EcomTrade24 Pay for WooCommerce

By ecomtrade24

0+ active installationsVersion 2.5.9

Accept cryptocurrency payments in WooCommerce with secure checkout, order updates and optional fiat-to-crypto onramp methods.

Description

Accept cryptocurrency payments in WooCommerce

EcomTrade24 Pay is a WooCommerce crypto payment gateway that connects your online store to cryptocurrency checkout, secure payment sessions and automatic order-status updates. Offer your customers a crypto payment option without building your own payment infrastructure.

Start with a free merchant account and Hosted Checkout. Eligible paid plans can enable Smart Routing and supported fiat-to-crypto onramp options for customers who prefer local payment methods.

Create a free merchant account | Setup documentation | Plans and fees

Why choose EcomTrade24 Pay?

  • Crypto payments for WooCommerce: Offer supported cryptocurrency assets and networks configured for your merchant account.
  • Fiat-to-crypto checkout options: Eligible paid plans may display card, Google Pay, Apple Pay, Venmo, Cash App, PayPal, Revolut, iDEAL, Klarna and other available payment routes when enabled and available through the gateway API. These are onramp methods, not direct fiat settlement.
  • One-click merchant connection: Securely authorize your shop to import its API key and per-shop webhook secret, register its callback automatically, and verify signed webhook delivery.
  • Automatic WooCommerce order updates: Synchronize payment-session status using authenticated, signed webhooks.
  • Classic Checkout and Checkout Blocks: Compatible checkout integrations for both WooCommerce checkout experiences.
  • Dynamic payment method sync: Classic and Blocks checkouts read payment methods and order directly from the gateway API. Only methods enabled, configured and available for the buyer are presented; new gateway methods and their payment logos need no plugin code change as long as the gateway API returns a supported, trusted HTTPS logo URL.
  • Free Hosted Checkout: Get started without a monthly plan subscription; payment processing fees still apply.

Connect your shop in three steps

  1. Save your receiving USDC Polygon wallet in the EcomTrade24 merchant dashboard, then install and activate the plugin in WordPress. Open WooCommerce > EcomTrade24 Pay.
  2. Click 1. Authorize / reconnect shop. Sign in to EcomTrade24 Pay and approve the connection for the correct merchant and shop.
  3. After approval, EcomTrade24 Pay automatically registers the WooCommerce webhook URL and returns you to the store. The plugin saves the credentials and requests a signed, order-free test webhook. Connected – Webhooks Active appears only after the test receives a valid HTTP 200 acknowledgement. If verification fails, review the WAF/Cloudflare settings and use Retry signed webhook test (within 15 minutes) or reconnect.

A valid USDC Polygon payout wallet is required before you can connect your shop or create new payment sessions. Existing connections must use Connect / Reconnect Shop after upgrading when prompted. Before connecting, configure your payout wallet in the EcomTrade24 merchant dashboard. When you click Connect, the webhook callback is registered per shop automatically: no manual URL or secret entry is needed. Select checkout options allowed by your plan and complete a test order. Successful webhook verification is not a substitute for testing signed session creation and a real payment.

How fiat-to-crypto payments work

A customer can choose a method available in their country and for their transaction. Where an eligible fiat onramp method is shown, an independent provider handles the payment and conversion into cryptocurrency; EcomTrade24 Pay does not turn your WordPress site into a card processor. Providers can require additional verification and apply their own terms, limits and fees.

Payment methods depend on merchant settings, plan eligibility, buyer location, currency, order amount and provider availability. No specific card, wallet or local payment method is guaranteed for every order.

Secure checkout and merchant configuration

Checkout-session requests are signed with HMAC-SHA256. Payment notifications are verified using webhook signatures. Keep API credentials private and connect the correct merchant account to avoid rejected session requests.

Your merchant account and API key are required to use this hosted payment service. The plugin is free to download; service fees and plan options are listed on the pricing page.

External services

This plugin connects to the EcomTrade24 Pay service at https://pay.ecomtrade24.com to create and track payment sessions, retrieve merchant capabilities, authorize the merchant/shop connection, register the shop-specific webhook URL and test signed webhook delivery, and process payment notifications. Data sent as needed for transactions can include order identifiers, amounts, currency, store domain, customer email and the customer IP address captured by WooCommerce. The gateway uses this address for payment-session security, fraud prevention and applicable routing checks. It also records the connecting shop-server IP separately. Canonical payment logos may be downloaded from https://pay.ecomtrade24.com/assets/logos/ using the WordPress HTTP API and cached locally when available. API-supplied checkout logo URLs from that same first-party HTTPS directory can also be displayed directly in the store checkout (SVG, PNG or WebP); visitors requesting such logos may transmit standard HTTP request data, including their IP address and user-agent, to the EcomTrade24 Pay service. Optional telemetry is disabled by default and only enabled when the merchant explicitly opts in under gateway settings. If enabled, it sends store URL/domain, WordPress/WooCommerce/PHP/plugin versions, enabled payment options, currency and checkout configuration approximately every 15 minutes and while checkout pages are visited. Merchants may disable this at any time without disabling payment processing. A manually requested heartbeat sends the same diagnostic information once. These requests authenticate the configured merchant and report connection / integration context. Gateway connection tests also transmit merchant configuration and diagnostic information. API credentials are used to authenticate merchant requests. Depending on the checkout route, customers may be redirected to independent payment or on-ramp providers, which apply their own terms and privacy policies.

Service: EcomTrade24 Pay (https://pay.ecomtrade24.com/). Terms of Service: https://pay.ecomtrade24.com/terms . Privacy Policy: https://pay.ecomtrade24.com/privacy . Documentation: https://pay.ecomtrade24.com/docs/ . The merchant is responsible for informing customers about payment-related data transfers.

Installation

Quick installation

  1. Install and activate WooCommerce on your WordPress store.
  2. Create an EcomTrade24 Pay merchant account and save a valid USDC payout wallet address on Polygon in Merchant Settings. This is mandatory before connecting or receiving payments.
  3. In WordPress go to Plugins > Add New Plugin, search for EcomTrade24 Pay for WooCommerce, install and activate the plugin. For manual installation, upload the complete plugin ZIP.
  4. Open WooCommerce > EcomTrade24 Pay (or WooCommerce > Settings > Payments > EcomTrade24 Pay > Manage).
  5. Click Connect / Reconnect Shop. Use it even if a previous plugin installation has been connected before.
  6. Approve the correct merchant and shop domain on EcomTrade24 Pay. Return automatically to WordPress or choose the Return to Shop & Complete Connection button if the redirect is blocked.
  7. The WooCommerce callback URL and matching per-shop signing secret are registered during connection. Connected – Webhooks Active means the shop acknowledged a signed test webhook over HTTPS. If verification fails, try Retry signed webhook test or reconnect after checking firewall settings.
  8. Set the checkout options allowed by your plan: Free merchants use Hosted Checkout; eligible paid plans can enable Smart Routing. Direct Crypto settings appear in the second payment tab.
  9. Place a test order to verify signed session creation, provider redirect, webhook delivery and order updates. An API key or webhook test alone does not prove successful payment processing.

Already have an EcomTrade24 merchant account?

Use Connect / reconnect shop and approve your shop on EcomTrade24 Pay; you will then return to WordPress automatically. This registers the webhook URL for that shop and imports its matching signing secret. A signed no-order webhook test must pass before a green success message is shown. Manual completion remains a fallback. If you change credentials manually, reconnect to keep webhook delivery working.

Checkout troubleshooting

  • API connection test passes but checkout fails: The test only verifies API-key access. Reconnect the shop and run a test order to verify the session-signing secret.
  • invalid_request_signature or HTTP 401: The API key and signing secret may not match. Use Connect / reconnect shop, approve the correct merchant and wait for the automatic return to WordPress (or use the manual fallback). Never disable signature verification to work around the error.
  • No fiat payment option is shown: Check plan eligibility and gateway settings. Smart Routing only displays methods the API confirms as active and available for the current country, amount and currency.
  • Order remains pending after payment: Check that Signed webhook delivery is verified; an HTTP 403 may come from Cloudflare/WAF. The test is separate from a real payment. Reconnect if you changed the webhook secret.
  • Need diagnostics: Go to WooCommerce > Status > Logs and select the EcomTrade24 Pay log. Do not share API keys, signing secrets or personal customer information.

FAQ

How do I accept cryptocurrency payments with WooCommerce?

Install EcomTrade24 Pay, connect your merchant account under WooCommerce > EcomTrade24 Pay, configure your shop and wallet in the gateway, enable the supported checkout options and complete a test purchase.

Is the WooCommerce crypto payment plugin free?

The plugin is free to install. A free merchant plan with Hosted Checkout is available. Transaction fees apply; optional paid plans provide additional gateway capabilities. See the current pricing.

Can my customers pay with a card, PayPal, Revolut, iDEAL or Klarna?

Eligible paid plans can show supported fiat-to-crypto onramp routes. Availability depends on the active gateway API configuration and each transaction. These are independent provider payment methods, not a guarantee of direct PayPal or card processing by your store.

What is the difference between Hosted Checkout and Smart Routing?

Free merchants use Hosted Checkout. Eligible paid merchants can enable Smart Routing, allowing currently available fiat-to-crypto methods to appear at checkout. The gateway determines provider availability for each checkout context.

How do I connect or reconnect my WooCommerce store?

Open WooCommerce > EcomTrade24 Pay, select Connect / reconnect shop, and approve the merchant connection. You will return automatically to WooCommerce, or use the Return to Shop & Complete Connection button on the gateway approval page. A green status confirms that both credentials were saved and a real signed test webhook was acknowledged. If redirected back manually, use Complete manually (fallback). This imports the correct API key and matching signing secret.

Why does the API test work but payment creation fail with invalid_request_signature?

The API test verifies the API key but not checkout-session signatures. Reconnect the shop to import the matching signing secret. Leave HMAC-SHA256 verification enabled, then place a test order.

Does the plugin support WooCommerce Checkout Blocks?

Yes. It supports WooCommerce Checkout Blocks as well as the classic checkout.

Will unavailable payment methods be hidden?

Yes. Smart Routing only presents methods the gateway reports as enabled, configured and available for the buyer’s current checkout context. Options can change with country, currency, amount and provider status.

Does this plugin handle card details or customer identity verification?

No. Where fiat-to-crypto onramp methods are available, third-party providers handle their own payment collection and may require customer identity verification. Your WordPress website does not process payment card details through this plugin.

How are WooCommerce orders updated after a payment?

EcomTrade24 Pay uses signed webhook notifications and session synchronization to update payment status. Configure the callback URL and matching secret shown in your plugin settings, then test a complete payment flow.

Where do I configure the payout wallet?

In your EcomTrade24 Pay merchant account. Supported settlement details, currencies and networks are governed by your merchant configuration and the service terms.

Does this plugin require a merchant account?

Yes. A merchant account and API key are required to access EcomTrade24 Pay payment services. Create an account.

Where can I find setup instructions and support?

Read the integration documentation or use the support contact page. For checkout issues, check WooCommerce > Status > Logs without sharing private credentials.

Changelog

2.5.9

  • Include the validated WooCommerce order customer IP in signed Fiat and Crypto payment-session requests.
  • Keep customer and shop-server addresses separate in compatible EcomTrade24 Pay gateways.
  • Distribute plugin updates through the official WordPress.org repository.
  • Preserve merchant connection, payment methods, signed webhooks and existing order settings.

2.5.8

  • Make Hosted Checkout a compact, mobile-friendly WooCommerce payment row without repeated title, instruction panels, badges or a logo wall.
  • Show the same streamlined Hosted Checkout for Free merchants and paid merchants using hosted/legacy mode in Classic Checkout and Checkout Blocks.
  • Keep API-driven Pro Smart Routing, crypto gateway, signed sessions, Connect/Reconnect and signed webhooks unchanged.

2.5.7

  • Use the merchant gateway API logo_url field for dynamic checkout payment-method logos in Classic Checkout and Checkout Blocks, including WeChat and Rewarble Gift Cards Pay.
  • Accept only trusted HTTPS payment logos hosted under https://pay.ecomtrade24.com/assets/logos/, and keep a local-icon fallback for older gateway responses.
  • Keep API-provided method names and customer-facing descriptions; provider names and minimum amounts are not exposed by the plugin itself.
  • Preserve signed checkout requests, verified webhooks, merchant pairing and existing payment logic.
  • After installing, use Connect / Reconnect Shop if connection settings need to be refreshed. A USDC Polygon payout wallet is required before accepting new payments.

2.5.6

  • Build the nested WordPress pairing callback with RFC3986 encoding to preserve the nonce when crossing domains.
  • Gateway R9 accepts valid legacy callback encodings and provides a visible Return to Shop button if automatic redirection is unavailable.
  • Automatic completion remains nonce-protected; missing/invalid callbacks require the existing manual fallback.
  • Existing checkout routes, dynamic methods, webhooks and signing checks are unchanged.

2.5.5

  • Fix the Connect / reconnect shop redirect by encoding the WordPress callback nonce correctly, avoiding the HTML-escaped & query parameter in redirects.
  • Keep the signed pairing challenge, existing per-shop webhook secret, Webhook Active verification and all payment logic unchanged.
  • Requires the gateway WAF R8 correction when gateway security incorrectly treats a nested WordPress return URL as a scanner request.

2.5.4

  • One-click connection now registers the correct per-shop WooCommerce webhook callback and matching signing secret on the gateway.
  • After storing credentials, verify real HTTPS delivery with a signed, side-effect-free test callback; no test order is created or changed.
  • Display Connected – Webhooks Active only after a confirmed signed test, with clear errors and a retry button for failed delivery.
  • Respect merchant shop limits and separate webhook configuration for multiple shops under one merchant.
  • Preserve Classic Checkout, Checkout Blocks, dynamic methods and existing signed payment logic.

2.5.3

  • Automatically return to WooCommerce settings after the merchant approves a shop connection on EcomTrade24 Pay (with matching gateway update).
  • Show a clear green success notice only after the WordPress callback has securely claimed and saved the merchant API key and matching signing secret.
  • Preserve an explicit manual-completion fallback for older gateway installations, blocked redirects or interrupted browser sessions; display clear error guidance when pairing fails.
  • Keep the existing dynamic payment method sync, signed session requests and webhooks unchanged.

2.5.2

  • Dynamic payment method discovery using the live EcomTrade24 merchant capabilities API: no hardcoded checkout method allowlist in the WooCommerce integration.
  • Display gateway-enabled Google Pay, Apple Pay, Venmo, Cash App and future payment methods in Classic Checkout and Checkout Blocks when eligible; refresh Blocks methods when billing country or cart total changes.
  • Display names and order are controlled by EcomTrade24 Pay; no third-party provider IDs or URLs are sent by the shop.
  • Recheck actual order country, currency and total against merchant capabilities at payment submission; fail closed when a method is unavailable.
  • Keep Free merchants on Hosted Checkout and preserve existing signed webhook, session and connection security.

2.5.1

  • Corrected merchant pairing and settings handling to prevent mismatched API keys and signing secrets after credential changes.
  • Added actionable admin notices and safe WooCommerce logs for gateway checkout-signature rejections.
  • Keep signed Fiat and Crypto sessions, active-method filtering, and payment-method branding.
  • Use WordPress.org for automatic updates in the WordPress.org repository edition.

2.5.0

  • Fixed Checkout Blocks Store API payment method selection, including local Fiat on-ramp method values.
  • Enforced the gateway minimum signing-secret length and retained HMAC-SHA256 request signing for Fiat and Crypto sessions.
  • Added safely redacted diagnostics for rejected session creation and checkout exceptions.

2.4.9

  • Restore reliable admin settings via WooCommerce > EcomTrade24 Pay, with fixed high-contrast light UI.
  • Protect saved API credentials on blank-field saves and retain signed checkout.

2.4.8

  • Added dedicated WooCommerce settings for Fiat and Crypto with improved contrast and secure credential persistence.

2.4.7

  • Corrected official PayPal logo filename to paypal-original.png (download and local cache).
  • Classic and Blocks now show only Smart Routing methods explicitly enabled, configured and available in /gateway/me.php for the customer checkout context.
  • Removed disabled/greyed-out rows and all invented Card defaults; unavailable API results fail closed.
  • Added UPI/IMPS and Interac where confirmed active by the API, preserving the gateway’s method order.
  • Capability cache reduced to 30 seconds with versioned cache keys; no cross-context stale fallback.
  • Gateway branding in the fiat option no longer suggests Card is enabled when it is not.

2.4.5

  • Correct HTML-encoded gateway titles in both Classic and Blocks checkouts, including older saved settings.
  • Use the six official gateway payment PNG assets (Card, Crypto, iDEAL, Klarna, PayPal and Revolut), with WordPress HTTP downloads, local caching and secure refresh in merchant settings.
  • Replace incorrect fixed provider labels with truthful fiat-to-crypto on-ramp method labels.
  • Align Checkout Blocks with saved Smart Routing preference and merchant eligibility, and fix checkout mode persistence after saving.
  • Hide payment methods until a merchant API key is configured; disable debug logging by default for new installs and protect Apache log files.
  • Make checkout layout options and optional branding behave as configured for Classic and Blocks.
  • Remove obsolete provider-specific payment eligibility rules in favor of the gateway API response.

2.4.4

  • Restore signed checkout handoff for WooCommerce Card/local methods and signed chooser links.
  • Reuse existing order sessions using the stored secure checkout link; no duplicate payment session.
  • Keep signed checkout links out of WooCommerce debug logs.

2.4.3

  • Checkout session creation HTTP wait increased to 75 seconds to allow V3 wallet and Alchemy webhook preparation to finish.
  • Extend the PHP execution budget where permitted and the WooCommerce per-order lock lifetime to avoid parallel session creation during slow provider responses.
  • Record request durations in existing gateway debug logs.

2.4.2

  • Merchant-account pairing also imports the matching webhook signing secret used by server-side notifications.
  • Fail closed when the merchant has no signing secret configured.

2.4.1

  • WordPress.org review hardening: require signed webhooks, optional telemetry consent, opt-in checkout branding and more restrictive request sanitization.

2.4.0

  • Added secure WooCommerce merchant-account pairing with a short-lived approval flow.
  • No changes to payment processing, routing or settlement behavior.

2.3.13

  • Updated WooCommerce checkout styling and settings presentation.
  • Added merchant sign-up links and WordPress.org listing documentation.
  • Prepared distribution through WordPress.org’s update mechanism.
  • Removed alternative plugin updater and external checkout image dependencies.
  • Disabled optional public attribution links by default for new installs.
  • Avoided API credentials in crypto fallback request URLs.