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.

uniple

uniple checkout for WooCommerce lets merchants accept JPYC, a Japanese yen stablecoin / electronic payment instrument (電子決済手段), through uniple’s hosted checkout.
Shoppers choose the uniple payment method in WooCommerce and are redirected to the uniple checkout page. uniple handles wallet connection and settlement, then returns the shopper to the WooCommerce order-received page. Payment confirmation is applied through a signed webhook, with a server-side session lookup fallback when the return page is reached before the webhook arrives.
Features:
<ul>
<li>Redirect-only WooCommerce payment gateway.</li>
<li>Classic checkout and Cart / Checkout Blocks support.</li>
<li>High-Performance Order Storage (HPOS) compatibility.</li>
<li>HMAC-SHA256 signed webhook verification.</li>
<li>Atomic webhook idempotency lock and event history.</li>
<li>Return URL order key verification and live lookup fallback.</li>
<li>Masked API key and webhook secret fields in the WooCommerce admin.</li>
</ul>
This plugin is built for WooCommerce stores. It is not developed by, affiliated with, or endorsed by WooCommerce or Automattic.
<h3>How to obtain an API key</h3>
uniple checkout requires a merchant account with uniple. Apply for an account at:
https://forms.gle/b8kwVZeynA1ffV8j6
After your application is approved, uniple will issue your API key and webhook secret, which you enter in the plugin settings (WooCommerce → Settings → Payments → uniple checkout (JPYC)).
<h3>External services</h3>
This plugin connects to the uniple hosted checkout API. The default service endpoint is <code>https://uniple.io</code>; the settings screen also permits <code>https://dev.uniple.io</code> for test use.
The plugin sends data to uniple only when it needs to create or verify a checkout session:
<ul>
<li>When a shopper places an order with the uniple payment method, the plugin sends <code>POST /api/merchant/checkout/sessions</code> to the configured uniple API base URL.</li>
<li>The session creation request includes the order total as <code>amountJpyc</code>, the WooCommerce order ID as <code>clientReferenceId</code>, the order description / order number, the configured merchant label, a one-line item summary, the success URL, the cancel URL, and the webhook URL.</li>
<li>The session creation request also includes the merchant API key in the <code>Authorization</code> header and a plugin <code>User-Agent</code> containing the plugin version, WordPress version, and WooCommerce version.</li>
<li>When the shopper returns from hosted checkout before the webhook has completed the order, the plugin may send <code>GET /api/merchant/checkout/sessions/{sessionId}</code> to verify the session status. This request includes the uniple session ID, the merchant API key, and the same plugin <code>User-Agent</code>.</li>
<li>uniple sends payment webhooks back to the store at <code>/wp-json/uniple/v1/webhook</code>. The plugin verifies the webhook signature locally with the configured webhook secret.</li>
</ul>
The plugin does not send full billing addresses, shipping addresses, customer account details, card details, wallet private keys, or browser cookies to uniple.
Service documentation and legal terms:
<ul>
<li>uniple: https://uniple.io/</li>
<li>Terms of Service: https://uniple.io/terms/</li>
<li>Privacy Policy: https://uniple.io/privacy/</li>
</ul>

uniple checkout for WooCommerce

JPYC hosted checkout for WooCommerce, powered by uniple.

PayzCore for WooCommerce vs uniple checkout for WooCommerce