SouthPay

SouthPay Crypto Payment Gateway lets your WooCommerce store accept cryptocurrency payments through SouthPay’s secure hosted checkout. Connect in one click via OAuth, and the plugin handles webhook setup, token refresh, and on-chain confirmation automatically — no key copy-pasting and no manual webhook configuration.
Customers are redirected to a secure SouthPay-hosted checkout where they can pay using supported cryptocurrencies. The order status updates automatically via webhook once payment is confirmed on-chain.
<h3>Features</h3>
<ul>
<li>One-click “Connect with SouthPay” — OAuth 2.0 with PKCE, no key copy-pasting</li>
<li>Automatic background token refresh — the connection stays live without merchant action</li>
<li>Accept cryptocurrency payments via a hosted checkout</li>
<li>Automatic order status updates via secure webhooks</li>
<li>Automatic webhook endpoint registration after first connection</li>
<li>HMAC-SHA256 webhook signature verification</li>
<li>Configurable invoice prefix</li>
<li>Minimum order amount filter</li>
<li>Debug logging via WooCommerce → Status → Logs</li>
<li>Customisable checkout title and description</li>
<li>Block checkout (Gutenberg) support</li>
</ul>
<h3>Requirements</h3>
<ul>
<li>WordPress 5.8 or higher</li>
<li>WooCommerce 6.0 or higher</li>
<li>PHP 7.4 or higher (cURL and OpenSSL extensions enabled)</li>
<li>HTTPS on your store domain — required for OAuth redirect and webhook delivery</li>
<li>A publicly reachable site URL so SouthPay can POST webhook events</li>
<li>A SouthPay merchant account at https://southpay.io/</li>
</ul>
<h3>Configuration</h3>
All settings live at WooCommerce → Settings → Payments → SouthPay.
Your SouthPay Account
<ul>
<li>Status — shows the current connection state (Connected, Disconnected, or Reconnect Required) and the connected store name.</li>
<li>Connect / Disconnect — manages the OAuth connection. Disconnecting revokes the refresh-token family on SouthPay’s side, not just the local copy.</li>
<li>API Key — only used as a manual fallback when OAuth isn’t possible (see Authentication below). Leave blank in the normal OAuth flow.</li>
</ul>
Checkout Appearance
<ul>
<li>Payment Method Name — what customers see at checkout (default: SouthPay). Customise this to something like “Pay with Crypto”.</li>
<li>Payment Method Description — short text shown below the name at checkout.</li>
</ul>
Advanced
<ul>
<li>Minimum Order Amount — hides SouthPay at checkout when the cart total is below this value. Set to <code>0</code> to always show it. Default: <code>1</code>.</li>
<li>Order Reference Prefix — prepended to the order number sent to SouthPay (default: <code>WC-</code>), so orders are easy to identify in the SouthPay dashboard.</li>
<li>Debug Logging — writes detailed request/response logs to WooCommerce → Status → Logs under the <code>southpay</code> source. Enable only when troubleshooting; the logs can contain order metadata.</li>
</ul>
<h3>Authentication</h3>
The plugin uses OAuth 2.0 with PKCE and the <code>offline_access</code> scope, so the connection survives access-token expiry without merchant intervention:
<ul>
<li>Access tokens are short-lived (one hour) and refreshed automatically before each API call.</li>
<li>Refresh tokens rotate on every use, and the previous refresh token is invalidated server-side.</li>
<li>If the refresh-token family is ever revoked (for example, an admin clicks Disconnect in the SouthPay dashboard), the plugin surfaces a Reconnect your account admin notice in WooCommerce and the gateway is hidden at checkout until reconnected.</li>
<li>Disconnecting from the WooCommerce side calls SouthPay’s revoke endpoint to invalidate the entire token family — not just the locally cached access token.</li>
</ul>
Manual API Key fallback. For environments without browser access (air-gapped boxes, whitelabel deployments, automated provisioning), paste a long-lived API key from SouthPay Dashboard → Developers → API Keys into the API Key field. This mode bypasses OAuth and does not auto-refresh; you are responsible for rotating the key yourself. The webhook still needs to be created manually in this mode.
<h3>Webhook Setup</h3>
In the standard OAuth flow there is nothing to configure — the plugin registers a webhook endpoint pointing at your site automatically the first time you connect, and stores the signing secret locally.
<ul>
<li>The active endpoint URL is shown in the Webhook URL row on the settings page (it is the WooCommerce REST route <code>/wc-api/southpay_webhook</code>).</li>
<li>Every inbound delivery is signed with HMAC-SHA256 over the raw request body plus a timestamp. The plugin rejects requests with a missing, malformed, or stale signature before any order state is touched.</li>
<li>If you ever need to rotate the signing secret (for example, after a security incident or when migrating environments), click Reconnect webhook on the settings page. The plugin will deregister the old endpoint and create a new one with a fresh secret in one step.</li>
</ul>
<h3>How It Works</h3>
<ol>
<li>The customer selects SouthPay at checkout and clicks Place order.</li>
<li>WooCommerce creates the order with status Pending payment.</li>
<li>The plugin calls <code>POST https://api.southpay.io/api/v2/payments</code> with the order total, currency, order reference, and return URLs to create a hosted-checkout session.</li>
<li>The customer is redirected to SouthPay’s hosted checkout, where they choose a cryptocurrency, see the quoted amount and exchange rate, and send the funds from their wallet.</li>
<li>Once the transaction is confirmed on-chain, SouthPay POSTs a signed webhook to your store.</li>
<li>The plugin verifies the HMAC-SHA256 signature, matches the event to the WooCommerce order, and transitions the order:
<ul>
<li>paid → order moves to Processing (or Completed for virtual orders), and a payment note is added.</li>
<li>expired → order moves to Cancelled.</li>
<li>failed → order moves to Failed; the customer can retry from the order-pay page.</li>
</ul>
</li>
<li>The customer is redirected back to your store’s order-received page.</li>
</ol>
All state transitions are driven by webhooks — the customer’s browser returning is not required to mark the order as paid.
<h3>External Services</h3>
This plugin connects to the SouthPay API to create cryptocurrency payment sessions and receive order status updates via webhook. Connection to this service is required for the gateway to function.
When a customer places an order using SouthPay as the payment method, the plugin sends the order total, currency, and return URLs to https://api.southpay.io/api/v2/payments to generate a hosted checkout session. No data is sent at any other time during normal store operation.
This service is provided by SouthPay: https://southpay.io/ 
Terms of service: https://southpay.io/terms 
Privacy policy: https://southpay.io/privacy

SouthPay Crypto Payment Gateway

Accept cryptocurrency payments in WooCommerce via SouthPay's hosted checkout, with one-click OAuth connect and automatic webhook registration.

nazebinan

Accept crypto payments directly to your own wallets – no third parties getting in the way.
If you’ve been looking for a crypto payment gateway WordPress solution that puts you in control, you’ve found it. Corexa lets you accept cryptocurrency payments in WooCommerce using your own personal crypto wallet addresses.
No middlemen, No extra fees, No KYC and No annoying sign-up forms.
Just add your wallet addresses and start receiving payments from customers all over the world.
Whether you’re selling products, services, or memberships, this plugin turns your WooCommerce store into a powerful crypto payment system in minutes.
<h3>Key Advantages</h3>
<ul>
<li>Multi-Coin support – Accept BTC, ETH, USDT, SOL, XRP, BNB, PEPE, USDC, TRON, DOGE — and almost any other cryptocurrency your wallet supports.</li>
<li>Smart checkout – Customers choose their favorite network easily.</li>
<li>QR codes – Display wallet addresses and QR codes for quick scanning.</li>
<li>Live updates – Automatic order status changes after cryptocurrency transactions are confirmed.</li>
<li>Custom notes – Add friendly instructions for your buyers.</li>
<li>Privacy first – We don’t store or handle your funds. Payments go directly from customer to merchant.</li>
<li>Crypto payment gateway api – No API needed — the process is simple and beginner-friendly.</li>
</ul>
<h3>How it works</h3>
Setting up Woocommerce crypto payments has never been this simple. You don’t need to be a tech expert to get started.
1.Connect your wallet: Add your cryptocurrency wallet addresses in the settings. (Already know how to open crypto wallet accounts? Just copy and paste your address!) 
2.Customer checkout: Shoppers select crypto payments with their preferred coin at checkout. 
3.Send crypto: Your customer sends crypto from their end. 
4.Auto-Confirm: Corexa checks the blockchain automatically. Once confirmed, the order status updates instantly.
<h3>External services</h3>
These services are only used to query public blockchain data required to verify incoming payments.
This plugin connects to external blockchain APIs and public RPC/explorer services to verify incoming cryptocurrency payments and update WooCommerce orders automatically after payment confirmation.
The plugin does not transmit personal customer data. Only blockchain addresses and transaction lookup requests required for payment verification may be sent to these services. Depending on the selected cryptocurrency/network, the plugin may send the configured wallet address, transaction lookup parameters, and related blockchain query data required to check whether a payment was received and confirmed.
The plugin may connect to the following services:
<ol>
<li>
Etherscan 
Used for Ethereum blockchain transaction verification. 
Data sent: wallet address and transaction lookup requests required to detect incoming transactions. 
When sent: during automatic payment verification for ERC20 / Ethereum payments. 
Terms: https://etherscan.io/terms 
Privacy: https://etherscan.io/privacyPolicy
</li>
<li>
BscScan 
Used for Binance Smart Chain transaction verification. 
Data sent: wallet address and transaction lookup requests required to detect incoming transactions. 
When sent: during automatic payment verification for BEP20 payments. 
Terms: https://bscscan.com/terms 
Privacy: https://bscscan.com/privacyPolicy
</li>
<li>
PolygonScan 
Used for Polygon blockchain transaction verification. 
Data sent: wallet address and transaction lookup requests required to detect incoming transactions. 
When sent: during automatic payment verification for Polygon payments. 
Terms: https://polygonscan.com/terms 
Privacy: https://polygonscan.com/privacyPolicy
</li>
<li>
BaseScan 
Used for Base network transaction verification. 
Data sent: wallet address and transaction lookup requests required to detect incoming transactions. 
When sent: during automatic payment verification for Base network payments. 
Terms: https://basescan.org/terms 
Privacy: https://basescan.org/privacyPolicy
</li>
<li>
TronGrid 
Used for TRON blockchain transaction verification. 
Data sent: wallet address and transaction lookup requests required to detect incoming TRC20 transactions. 
When sent: during automatic payment verification for TRON payments. 
Terms: https://developers.tron.network/page/terms-of-use 
Privacy: https://developers.tron.network/page/privacy-policy
</li>
<li>
Stellar Horizon 
Used for Stellar blockchain transaction verification. 
Data sent: wallet address, transaction lookup requests, and memo checks required for payment verification. 
When sent: during automatic payment verification for Stellar payments. 
Terms: https://stellar.org/terms-of-service 
Privacy: https://stellar.org/privacy-policy
</li>
<li>
XRPSCAN 
Used to verify XRP payments. 
Data sent: wallet address and transaction lookup requests required to detect incoming XRP payments. 
When sent: during automatic payment verification for XRP payments. 
Terms: https://docs.xrpscan.com/help/terms-of-service 
Privacy: https://docs.xrpscan.com/help/privacy-policy
</li>
<li>
Solana public RPC endpoint 
Used to query the Solana blockchain for payment verification. 
Data sent: wallet address and transaction lookup requests via JSON-RPC. 
When sent: during automatic payment verification for Solana payments. 
Terms: https://solana.com/tos 
Privacy: https://solana.com/privacy-policy
</li>
<li>
Blockfrost 
Used to verify Cardano payments via the Cardano blockchain API. 
Data sent: wallet address and transaction lookup requests required to detect incoming payments. 
When sent: during automatic payment verification for Cardano payments. 
Terms: https://blockfrost.io/terms 
Privacy: https://blockfrost.io/privacy
</li>
<li>
NOWNodes 
Used for Verge (XVG) Blockbook blockchain queries. 
Data sent: wallet address and transaction lookup requests required for blockchain verification. 
When sent: during automatic payment verification for Verge payments. 
Terms: https://nownodes.io/assets/data/service-agreement.pdf 
Privacy: https://nownodes.io/assets/data/privacy-pol.pdf
</li>
<li>
Tatum 
Used for UTXO blockchain transaction verification for supported coins such as BTC, LTC, BCH, DOGE, and DASH. 
Data sent: wallet address and transaction lookup requests required to detect incoming transactions and confirmations. 
When sent: during automatic payment verification for supported UTXO coins. 
Terms: https://tatum.io/terms-of-use 
Privacy: https://tatum.io/privacy-policy
</li>
<li>
CoinGecko 
Used for cryptocurrency exchange rate lookup in USD so the plugin can calculate the expected payment amount for supported coins. 
Data sent: the list of supported coin identifiers required to request current USD exchange rates. 
When sent: when the plugin fetches cryptocurrency rates for checkout/payment verification. 
Terms: https://www.coingecko.com/en/terms 
Privacy: https://www.coingecko.com/en/privacy
</li>
</ol>

Corexa crypto payment

Accept cryptocurrency payments in WooCommerce using your own wallet addresses, with automatic payment verification.

SouthPay Crypto Payment Gateway vs Corexa crypto payment