icpay

Why ICPay?
<ul>
<li>Instant settlement to your wallet with no intermediaries or withdrawal delays. Customers pay, you receive – that simple.</li>
<li>0.5% transaction fees. Free to use. Start earning crypto in minutes.</li>
<li>Multi-chain support including Base, X402, and Internet Computer means your customers can pay using their preferred network and token.</li>
</ul>
Key Features:
<ul>
<li>Seamless WooCommerce gateway integration (Checkout + Order Pay pages)</li>
<li>Support for 50+ cryptocurrencies and tokens</li>
<li>Optional X402 (Coinbase) payment support enabled</li>
<li>Real-time payment confirmations via webhooks</li>
<li>Developer-friendly with extensive documentation</li>
<li>Secure, non-custodial – funds go directly to your wallet</li>
<li>Compatible with HPOS (High-Performance Order Storage) and Cart/Checkout Blocks</li>
<li>Express Checkout button (optional) for Cart and Checkout</li>
</ul>
This plugin:
<ul>
<li>Adds an ICPay payment gateway for WooCommerce checkout</li>
<li>Renders a pay button at checkout / order-pay</li>
<li>Updates order status automatically when payment completes or fails (webhooks and verification)</li>
<li>Reuses the Publishable Key from the ICPay plugin (if installed) or set keys locally</li>
<li>Provides Settings for:
<ul>
<li>Filter allowed tokens (optional) using searchable multi-select by token shortcode</li>
<li>Metadata editor (key/value) merged into widget metadata (orderId is added automatically)</li>
</ul>
</li>
<li>Progress bar is always enabled for a smooth checkout experience</li>
</ul>
<h3>Source code and build</h3>
This plugin includes minified frontend bundles: 
– assets/js/icpay-embed.min.js (ICPay widget) 
– assets/js/wc/index.umd.js (optional WalletConnect adapter UMD for the widget)
Public source (maintained and human-readable): 
– Widget: https://github.com/icpay/icpay-widget (MIT) 
– SDK: https://github.com/icpay/icpay-sdk (MIT) 
– WalletConnect (optional adapter runtime): https://github.com/WalletConnect/walletconnect-monorepo
Exact mapping of distributed files to source: 
– assets/js/icpay-embed.min.js → Built from https://github.com/icpay/icpay-widget (package “@ic-pay/icpay-widget”). 
 – Primary sources live under /src in that repository. 
 – Build target is the IIFE embed bundle at /dist/index.embed.js, which is copied and renamed to icpay-embed.min.js for this plugin distribution. 
 – Example tagged release used: see icpay-widget releases matching this plugin version. Repository includes full TS sources and sourcemaps. 
– assets/js/wc/index.umd.js → Built from https://github.com/icpay/icpay-widget at /src/index.umd.js (WalletConnect adapter UMD) and copied to /dist/wc/index.umd.js by the build script.
Build instructions (reproducible): 
1) Clone https://github.com/icpay/icpay-widget 
2) Install dependencies (pnpm, yarn, or npm): 
 – pnpm install 
3) Build the library (produces ESM, IIFE embed, and UMD adapter): 
 – pnpm build:embed 
 – The script also copies the WalletConnect UMD adapter to dist/wc/index.umd.js 
4) Copy artifacts into this plugin: 
 – dist/index.embed.js → instant-crypto-payments-for-woocommerce/assets/js/icpay-embed.min.js 
 – dist/index.embed.js.map (optional, recommended) → instant-crypto-payments-for-woocommerce/assets/js/icpay-embed.min.js.map 
 – dist/wc/index.umd.js → instant-crypto-payments-for-woocommerce/assets/js/wc/index.umd.js
Notes: 
– The widget depends on “@ic-pay/icpay-sdk”, which is fully open source at https://github.com/icpay/icpay-sdk; the SDK sources are not vendored into this plugin but are bundled into the distributed widget file as part of the upstream open-source build. 
– If you prefer, you may vendor the unminified files from icpay-widget/dist instead; WordPress.org accepts either shipping unminified sources with the plugin or providing public, maintained source links (as above).
<h3>External services</h3>
This plugin connects to the ICPay service operated by ICPay, Ltd. to process payments. Details below list what is used, when, what data is sent, and links to each provider’s terms and privacy policies.
1) ICPay API (icpay.org, api.icpay.org) — operated by ICPay, Ltd. 
– What/why: Create and manage a payment and receive payment status updates. 
– When: When rendering the pay button (client-side widget load) and when receiving payment webhooks or running order payment verification. 
– Data sent: Order amount (in store currency; sent with optional fiat_currency when store is not USD), selected crypto asset, and order metadata (e.g., orderId). Webhook payloads contain payment status updates for the order. 
– Terms: https://icpay.org/terms 
– Privacy: https://icpay.org/privacy
<h3>Additional third-party services used by the widget (optional)</h3>
2) WalletConnect RPC (rpc.walletconnect.org) — provided by WalletConnect 
– What/why: Facilitate mobile wallet connections via WalletConnect. 
– When: Only if the WalletConnect adapter is enabled AND the shopper chooses WalletConnect. 
– Data sent: Wallet session metadata and JSON-RPC requests needed to complete a payment. 
– Terms: https://walletconnect.com/terms 
– Privacy: https://walletconnect.com/privacy
3) Wallet vendor websites and app deeplinks — shown only if the WalletConnect adapter is enabled and the shopper chooses a wallet. Navigation happens only on explicit user action; the plugin does not send data to these vendors automatically. 
– Phantom: https://phantom.app — Terms: https://phantom.app/terms — Privacy: https://phantom.app/privacy 
– Solflare: https://solflare.com — Terms: https://solflare.com/terms-of-use — Privacy: https://solflare.com/privacy-policy 
– Coinbase: https://go.cb-w.com (redirect), https://www.coinbase.com — Terms: https://www.coinbase.com/legal/user_agreement — Privacy: https://www.coinbase.com/legal/privacy 
– Binance: https://app.binance.com, https://www.binance.com — Terms: https://www.binance.com/en/terms — Privacy: https://www.binance.com/en/privacy
4) On-ramp provider (optional and disabled in this plugin build) 
– The bundled WalletConnect adapter contains an optional on-ramp link for “Meld” (domain: https://meldcrypto.com). In this plugin distribution, on-ramp is disabled by default; no requests are made to this provider. 
– When: Only if a developer explicitly enables on-ramp in the widget configuration and the shopper chooses to open it. 
– Data sent: None by default in this plugin. If enabled by a developer, the provider’s own site and terms will apply. 
– Vendor site: https://meldcrypto.com (please refer to the vendor site for terms and privacy)
<h3>Remote assets and CDN fallbacks</h3>
<ul>
<li>This plugin bundles all primary JS/CSS/images locally and does not offload required assets to remote CDNs.</li>
<li>The optional WalletConnect adapter may reference external vendor logos or pages provided by those vendors. We ship local icons where possible; any navigation to vendor sites occurs only when the shopper explicitly chooses that wallet. No plugin settings or secrets are transmitted by simply rendering the checkout page.</li>
</ul>

Instant Crypto Payments for WooCommerce

Accept crypto payments (ICP, Bitcoin, stablecoins) in WooCommerce via ICPay. Gateway for secure checkout and webhook order updates.

PayzCore

PayzCore is a blockchain monitoring service, not a payment processor. All payments are sent directly to your own wallet addresses. PayzCore never holds, transfers, or has access to your funds.
<ul>
<li>Your wallets, your funds — You provide your own wallet (HD xPub or static addresses). Customers pay directly to your addresses.</li>
<li>Read-only monitoring — PayzCore watches the blockchain for incoming transactions and sends webhook notifications. That’s it.</li>
<li>Protection Key security — Sensitive operations like wallet management, address changes, and API key regeneration require a Protection Key that only you set. PayzCore cannot perform these actions without your authorization.</li>
<li>Your responsibility — You are responsible for securing your own wallets and private keys. PayzCore provides monitoring and notification only.</li>
</ul>
How It Works
PayzCore is a non-custodial blockchain transaction monitoring service. When a customer checks out, the plugin creates a monitoring request via the PayzCore API. The customer is shown a unique wallet address and QR code. PayzCore watches the blockchain for incoming transfers and sends a webhook notification when the payment is detected, automatically updating your WooCommerce order status.
Key Features
<ul>
<li>Accept USDT and USDC stablecoins</li>
<li>Multi-network support: TRC20 (Tron), BEP20 (BNB Smart Chain), ERC20 (Ethereum), Polygon, and Arbitrum</li>
<li>Non-custodial: funds go directly to your wallet, PayzCore never touches them</li>
<li>Static wallet mode: use a fixed address for all payments with customer tx hash confirmation</li>
<li>Real-time payment status polling with automatic order updates</li>
<li>Dark-themed payment instructions page with QR code and countdown timer</li>
<li>HMAC-SHA256 webhook signature verification for security</li>
<li>Automatic order completion for virtual/downloadable products</li>
<li>Blockchain explorer links in order notes (Tronscan, BSCScan, Etherscan, Polygonscan, Arbiscan)</li>
<li>WooCommerce HPOS (High-Performance Order Storage) compatible</li>
<li>Translatable with full i18n support</li>
</ul>
Static Wallet Mode
By default, PayzCore derives a unique HD wallet address for each payment. If you prefer to use a single fixed address for all payments, you can enable Static Wallet Mode:
<ol>
<li>Go to WooCommerce > Settings > Payments > PayzCore (Stablecoin)</li>
<li>Enter your wallet address in the “Static Wallet Address” field</li>
<li>Save settings</li>
</ol>
When static wallet mode is active:
<ul>
<li>All payments use the same address you configured</li>
<li>The payment amount includes a micro-offset (e.g., $50.003 instead of $50.00) to distinguish transactions</li>
<li>Customers see a notice with the exact amount to send</li>
<li>After sending payment, customers are shown a form to paste their blockchain transaction hash (TxID)</li>
<li>The transaction hash is submitted to PayzCore for verification</li>
<li>Order status is updated automatically once PayzCore confirms the transaction</li>
</ul>
This mode is useful when you want to receive all payments to a single address without setting up HD wallet (xPub) derivation.
Requirements
<ul>
<li>A PayzCore account at <a href="https://payzcore.com" rel="nofollow ugc">payzcore.com</a></li>
<li>A project with an API key and webhook secret configured</li>
<li>WooCommerce 7.0 or higher</li>
<li>PHP 7.4 or higher</li>
<li>WordPress 5.8 or higher</li>
</ul>
Before Going Live
Always test your setup before accepting real payments:
<ol>
<li>Verify your wallet — In the PayzCore dashboard, verify that your wallet addresses are correct. For HD wallets, click “Verify Key” and compare address #0 with your wallet app.</li>
<li>Run a test order — Place a test order for a small amount ($1–5) and complete the payment. Verify the funds arrive in your wallet.</li>
<li>Test sweeping — Send the test funds back out to confirm you control the addresses with your private keys.</li>
</ol>
Warning: Wrong wallet configuration means payments go to addresses you don’t control. Funds sent to incorrect addresses are permanently lost. PayzCore is watch-only and cannot recover funds. Please test before going live.
Links
<ul>
<li><a href="https://docs.payzcore.com/getting-started" rel="nofollow ugc">Getting Started</a> — Account setup and first payment</li>
<li><a href="https://docs.payzcore.com/guides/webhooks" rel="nofollow ugc">Webhooks Guide</a> — Events, headers, and signature verification</li>
<li><a href="https://docs.payzcore.com/guides/networks" rel="nofollow ugc">Supported Networks</a> — Available networks and tokens</li>
<li><a href="https://docs.payzcore.com/guides/errors" rel="nofollow ugc">Error Reference</a> — HTTP status codes and troubleshooting</li>
<li><a href="https://docs.payzcore.com" rel="nofollow ugc">API Reference</a> — Interactive API documentation</li>
<li><a href="https://github.com/payzcore/woocommerce" rel="nofollow ugc">GitHub</a> — Source code</li>
</ul>
<h3>Third Party or External Service</h3>
This plugin connects to the <a href="https://api.payzcore.com" rel="nofollow ugc">PayzCore API</a> to create and monitor blockchain payment requests. The PayzCore API is required for this plugin to function.
When data is sent:
<ul>
<li>When a customer places an order and selects PayzCore as the payment method, a monitoring request is created via the API.</li>
<li>While the customer is on the payment instructions page, the plugin polls the API every 15 seconds to check payment status.</li>
<li>If using static wallet mode, the customer’s submitted transaction hash is sent to the API for verification.</li>
<li>When the admin clicks “Test Connection” in plugin settings, the plugin fetches project configuration from the API.</li>
</ul>
Data transmitted:
<ul>
<li>Order amount, selected blockchain network and token</li>
<li>Customer identifier (order ID or email, used as external reference)</li>
<li>Store webhook URL (for receiving payment status notifications)</li>
<li>Transaction hash (static wallet mode only)</li>
</ul>
No data is sent unless the plugin is enabled and configured with an API key. PayzCore does not hold, transmit, or custody any funds — it is a read-only monitoring service.
<ul>
<li><a href="https://payzcore.com" rel="nofollow ugc">PayzCore Website</a></li>
<li><a href="https://payzcore.com/terms" rel="nofollow ugc">PayzCore Terms of Service</a></li>
<li><a href="https://payzcore.com/privacy" rel="nofollow ugc">PayzCore Privacy Policy</a></li>
</ul>
This plugin also displays links to third-party blockchain explorers so users can verify their transactions on the blockchain. No data is sent to these services by the plugin — they are informational links only, opened in the user’s browser.
<ul>
<li><a href="https://tronscan.org" rel="nofollow ugc">Tronscan</a> — TRC20 transaction explorer (<a href="https://tronscan.org/#/about/terms" rel="nofollow ugc">Terms</a>, <a href="https://tronscan.org/#/about/privacyPolicy" rel="nofollow ugc">Privacy</a>)</li>
<li><a href="https://bscscan.com" rel="nofollow ugc">BscScan</a> — BEP20 transaction explorer (<a href="https://bscscan.com/terms" rel="nofollow ugc">Terms</a>, <a href="https://bscscan.com/privacyPolicy" rel="nofollow ugc">Privacy</a>)</li>
<li><a href="https://etherscan.io" rel="nofollow ugc">Etherscan</a> — ERC20 transaction explorer (<a href="https://etherscan.io/terms" rel="nofollow ugc">Terms</a>, <a href="https://etherscan.io/privacypolicy" rel="nofollow ugc">Privacy</a>)</li>
<li><a href="https://polygonscan.com" rel="nofollow ugc">PolygonScan</a> — Polygon transaction explorer (<a href="https://polygonscan.com/terms" rel="nofollow ugc">Terms</a>, <a href="https://polygonscan.com/privacyPolicy" rel="nofollow ugc">Privacy</a>)</li>
<li><a href="https://arbiscan.io" rel="nofollow ugc">Arbiscan</a> — Arbitrum transaction explorer (<a href="https://arbiscan.io/terms" rel="nofollow ugc">Terms</a>, <a href="https://arbiscan.io/privacyPolicy" rel="nofollow ugc">Privacy</a>)</li>
</ul>
<h3>Upgrade Notices</h3>
<h4>1.0.2</h4>
Security hardening and WordPress.org compliance improvements. No configuration changes needed.
<h4>1.0.1</h4>
QR code display fix. No configuration changes needed.
<h4>1.0.0</h4>
Initial release. Configure your API key and webhook secret in WooCommerce settings.

PayzCore for WooCommerce

Accept USDT and USDC stablecoin payments in your WooCommerce store via PayzCore blockchain transaction monitoring across multiple networks.

Instant Crypto Payments for WooCommerce vs PayzCore for WooCommerce