WooCommerce crypto payment gateway for CXPay

Getting the WooCommerce plugin

Merchants receive the plugin through the CXPay contact form at /contact. There is no public download link on this site—submit a request describing your store so the team can provision access.

After installation, enter your cxpay_live_ or cxpay_test_ API key and point the plugin at https://api.cxpay.cash/api/v1 unless you use a staging base URL for tests.

Webhooks and order status

Configure a webhook endpoint for payment.succeeded (and related events you need) so WooCommerce orders move to paid when on-chain settlement completes.

Verify cxpay-signature headers on your server using the shared secret from the dashboard. Rotate secrets if credentials leak.

Settlement wallet prerequisites

Set your merchant payout wallet in CXPay before taking live orders. WooCommerce checkout uses the same non-custodial settlement model as links and invoices.

Merchant sign-up requires an email and password (or sign in with your existing CoinExchange account), a business name, and a payout wallet address. CXPay does not collect government ID, proof of address, business phone numbers, or KYB documents for onboarding. You are responsible for understanding obligations that may apply to your business in your jurisdiction.

Supported checkout assets

Supported networks and assets today: Ethereum (ETH, USDC, USDT, DAI); Base (ETH, USDC, DAI — USDT is not supported on Base); Arbitrum (ETH, USDC, USDT); Optimism (ETH, USDC, USDT, DAI); Polygon (MATIC, USDC, USDT, DAI); Tron (TRX, USDT TRC20); Solana (SOL, USDC, USDT); Bitcoin on-chain (BTC) and Bitcoin Lightning (BOLT11); and CXCASH (gas-free private payments via cxcash.app).

CXPay charges 1% on standard checkout, 0.5% when the payer selects the CXCASH rail (private, gas-free payments on Aztec via cxcash.app), and a $0.30 minimum fee per payment. There is no setup fee, monthly fee, or application fee in the product. Ethereum and Bitcoin network fees are shown to the payer at cost on those rails.

Support and contact

Use the contact form for plugin access and integration questions. Public pages do not list email addresses.

Configure webhook endpoints to receive signed POST requests when payment state changes. Parse the cxpay-signature header, reject stale timestamps outside the five-minute tolerance, and return quickly while processing asynchronously. Failed deliveries retry and may dead-letter; use dashboard delivery logs to diagnose URL typos, TLS issues, or application errors on your side.

The merchant dashboard and GET /reports/payments help you filter by status and time range. Download GET /exports/payments.csv when finance needs a spreadsheet-friendly view. Pair exports with webhook-driven order updates so internal systems stay aligned with on-chain settlement. Because CXPay does not hold balances, your wallet history and CXPay reports together form the reconciliation trail.

Operating WooCommerce with CXPay

Server integrations should create payment intents with Idempotency-Key headers, persist the returned intent ID on your order row, and only mark paid after payment.succeeded verifies on your webhook handler. Test keys let you exercise the full lifecycle without touching live balances. WooCommerce merchants request the official plugin through the contact form and configure API base URL plus webhook secrets before going live.

Merchants who educate payers about exact amounts and quote expiry see fewer support tickets. Publish your accepted assets and networks on your store policy page and link to CXPay asset guides. When customers pay with ETH or BTC, remind them that network fees appear separately from the CXPay merchant fee. For audiences comfortable with Aztec, highlight CXCASH as a gas-free alternative through cxcash.app.

Explore CXPay

• How CXPay works
• Pricing and fee examples
• API quickstart
• Frequently asked questions
• Create a merchant account
• REST API

Questions about this page