spectrocointest/magento2merchanttest

SpectroCoin cryptocurrency payment gateway for Magento2

Maintainers

Details

github.com/SteinCode/Magento-2-Bitcoin-Payment-Gateway-Extension

Homepage

Source

Installs: 13

Dependents: 0

Suggesters: 0

Security: 0

Stars: 0

Watchers: 0

Forks: 3

Type:magento2-module

dev-master 2025-02-24 08:58 UTC

Requires

GPL-3.0+ 7a19beb8c2b7e8eafa73a069b880a5650ed13304

  • SpectroCoin <merchant.woop@spectrocoin.com>

paymentgatewaymerchantbitcoinbtcdashaltcoinmagento2xemspectrocoin

This package is not auto-updated.

Last update: 2025-06-13 10:30:05 UTC

README

Integrate cryptocurrency payments seamlessly into your Magento store with the SpectroCoin Crypto Payment Module. This extension facilitates the acceptance of a variety of cryptocurrencies, enhancing payment options for your customers. Easily configure and implement secure transactions for a streamlined payment process on your Wordpress website.

Installation

  1. Access your server terminal.
  2. Navigate to the magento web-root.
  3. Enter following command:
composer require 'spectrocoin/magento2merchant'
  1. To enable plugin run:
php bin/magento module:enable Spectrocoin_Merchant --clear-static-content
  1. To register the module run:
php bin/magento setup:upgrade
  1. To compile dependency injenction run:
bin/magento setup:di:compile

Setting up

  1. Sign up for a SpectroCoin Account.
  2. Log in to your SpectroCoin account.
  3. On the dashboard, locate the Business tab and click on it.
  4. Click on New project.
  5. Fill in the project details and select desired settings (settings can be changed).
  6. Click "Submit".
  7. Copy and paste the "Project id".
  8. Click on the user icon in the top right and navigate to Settings. Then click on API and choose Create New API.
  9. Add "API name", in scope groups select "View merchant preorders", "Create merchant preorders", "View merchant orders", "Create merchant orders", "Cancel merchant orders" and click "Create API".
  10. Copy and store "Client id" and "Client secret". Save the settings.

Note: Keep in mind that if you want to use the business services of SpectroCoin, your account has to be verified.

Testing Callbacks

Order callbacks in the SpectroCoin plugin allow your WordPress site to automatically process order status changes sent from SpectroCoin. These callbacks notify your server when an order’s status transitions to PAID, EXPIRED, or FAILED. Understanding and testing this functionality ensures your store handles payments accurately and updates order statuses accordingly.

  1. Go to your SpectroCoin project settings and enable Test Mode.
  2. From the Test mode select a payment status (PAID or EXPIRED), which will be sent with a callback.
  3. Ensure your callbackUrl is publicly accessible (local servers like localhost will not work).
  4. Check the Order History in SpectroCoin for callback details. If a callback fails, use the Retry button to resend it.
  5. Verify that:
    • The order status in WordPress has been updated accordingly.
    • The callback status in the SpectroCoin dashboard is 200 OK.

Contact

This client has been developed by SpectroCoin.com If you need any further support regarding our services you can contact us via:

E-mail: merchant@spectrocoin.com
Skype: spectrocoin_merchant
Web
X (formerly Twitter)
Facebook

Changelog

2.0.0 MAJOR ():

This major update introduces several improvements, including enhanced security, updated coding standards, and a streamlined integration process. Important: Users must generate new API credentials (Client ID and Client Secret) in their SpectroCoin account settings to continue using the plugin. The previous private key and merchant ID functionality have been deprecated.

Updated SCMerchantClient was reworked to adhere to better coding standards.

Updated Order creation API endpoint has been updated for enhanced performance and security.

Removed Private key functionality and merchant ID requirement have been removed to streamline integration.

Added OAuth functionality introduced for authentication, requiring Client ID and Client Secret for secure API access.

Updated Class and some method names have been updated based on PSR-12 standards.

Updated Composer class autoloading has been implemented.

Added Config.php file has been added to store plugin configuration.

Added Utils.php file has been added to store utility functions.

Added GenericError.php file has been added to handle generic errors.

Added Strict types have been added to all classes.

Migrated to GuzzleHttp since HTTPful is no longer maintained. In this case /vendor directory was added which contains GuzzleHttp dependencies.

Added To enhance module security added data sanitization and validation.

Optimised the The whole $_POST stack processing. Now only needed callback keys is being processed.