Ax402 For WooCommerce Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
Ax402 for WooCommerce adds a payment method that settles orders with Ax402 / x402. Shoppers pay from a wallet on the pay page. Agents can use the same payment URL via the Ax402 CLI or buyer SDKs.
Your catalog stays in USD. Settlement tokens come from your Ax402 platform config (for example USDC). Classic checkout and Cart / Checkout Blocks are supported. HPOS is supported.
You need an Ax402 merchant account and API key from https://ax402.io
External services
This plugin does not include analytics, advertising pixels, or other tracking. It contacts the services below only to accept Ax402 / x402 payments. Saving an Ax402 API key in WooCommerce settings is consent to use the Ax402 service. WalletConnect, Hedera Mirror Node, and public RPC calls run in the shopper’s browser when they choose to pay.
Ax402
Ax402 (operated by AxLabs) creates payment endpoints, syncs settlement tokens, confirms settlements, and serves the payment gateway the shopper or agent pays. The browser and the WordPress server may call your assigned gateway host (*.ax402.io) under the same operator.
- When: configuring the gateway, placing an Ax402 order, loading the pay page, refreshing tokens, verifying payment, and (server-side) proxying or reconciling a payment when needed.
- Data sent: API key, pay-to wallet, order totals / amounts, order keys, selected settlement token, store origin for CORS, and settlement references returned by Ax402. No card data or wallet private keys are sent.
- Service: https://ax402.io
- Terms: https://ax402.io/terms
- Privacy: https://ax402.io/privacy
- Disclaimer: https://ax402.io/disclaimer
Chain metadata (GitHub / ethereum-lists)
When a settlement token does not already include a chain name, public RPC, or explorer URL, the plugin may fetch one public Ethereum chain JSON file from the GitHub Contents API at https://api.github.com/repos/ethereum-lists/chains/contents/_data/chains/eip155-{id}.json, cached for 24 hours per chain. The dataset is https://github.com/ethereum-lists/chains (MIT).
- When: resolving a display name, public RPC, or explorer for an EVM settlement network that lacks those fields on the Ax402 token.
- Data sent: HTTP GET with Accept and GitHub API version headers only. The path includes the numeric chain id. No personal data, API keys, or order data are sent.
- Service: https://api.github.com
- Terms: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service
- Privacy: https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement
WalletConnect / Reown
On the pay page, when a shopper selects Hedera settlement and the merchant has configured a WalletConnect project ID, the browser uses WalletConnect / Reown to discover and connect a Hedera wallet (for example HashPack). This includes WalletConnect relay traffic such as https://rpc.walletconnect.com/.
- When: only after the shopper starts Hedera wallet connect on the pay page.
- Data sent: project ID, dapp metadata (store name and URL), session data, and the wallet account id used for signing. Private keys stay in the wallet.
- Terms: https://reown.com/terms-of-service and https://walletconnect.com/terms
- Privacy: https://reown.com/privacy-policy and https://walletconnect.com/privacy
- Docs: https://docs.reown.com/
Hedera Mirror Node
On the pay page, the shopper’s browser may query public Hedera Mirror Node REST endpoints (mainnet-public.mirrornode.hedera.com / testnet.mirrornode.hedera.com) to read token balances and network readiness.
- When: when a shopper pays with a Hedera settlement token.
- Data sent: Hedera account id and token id in public REST paths. No private keys are sent.
- Terms: https://hedera.com/terms
- Privacy: https://hedera.com/privacy
Public EVM RPC endpoints
The shopper’s browser may call public EVM JSON-RPC URLs taken from token metadata or ethereum-lists chain files (via the GitHub Contents API) for balance checks, chain switching, and payment signing with their wallet. No server-side private keys are sent. Exact RPC URLs vary by chain.
Wallet extensions (for example MetaMask) run locally in the shopper’s browser; private keys never leave the wallet.
UCP discovery JSON may include protocol spec and schema URLs (https://ucp.dev, https://x402.org/schemas/ucp-payment-handler.json, and https://github.com/AxLabs/ucp-x402-binding). Those are documentation identifiers. This plugin does not call them as APIs.
Source code and build
Minified frontend assets live in build/. Readable source, build tooling, and third-party license notes:
https://github.com/AxLabs/ax402-woocommerce-extension
See also assets/THIRD_PARTY_LICENSES.md in the plugin package.
`
npm –prefix plugin ci
npm –prefix plugin run build
Optional lean EVM-only bundle (stubs Hedera): AX402_EVM_ONLY=1 npm –prefix plugin run build
`
The default build includes Hedera WalletConnect support (~2MB pay-page bundle).
Screenshots
No screenshots provided
