

VERIFIED gateways in WooCommerce payment settings.
VERIFIED Crypto Checkout is WooCommerce-native card-to-crypto routing and settlement infrastructure. It connects WooCommerce orders to independent provider-hosted checkout pages and is designed to deliver settlement to a merchant-controlled wallet, with USDC on Polygon as the intended settlement route.
WooCommerce remains the system of record for the order. The hosted provider controls customer verification, payment-method availability, risk checks, transaction approval, conversion, and settlement execution. VERIFIED creates and tracks the checkout session, coordinates the order status, and provides reconciliation tools. VERIFIED does not process card data or custody merchant funds.
This model can provide a checkout continuity layer when traditional merchant-account underwriting is unavailable or unreliable. It is not a bypass, a guarantee of approval, or a way to avoid provider rules. Customer and transaction eligibility remain subject to each provider’s terms, KYC/AML controls, regional support, and applicable law.
Read the canonical product overview or visit the documentation hub.
Learn more about the hosted checkout architecture.
Auto-Routing selects from available provider options based on the upstream route. Merchants can also expose individual gateways. The codebase includes integrations for providers and payment methods such as Coinbase, Ramp Network, Transak, Revolut, Stripe, Banxa, Simplex, Robinhood, Binance, PayPal, Crypto.com, Klarna, iDEAL, Blockchain.com, Particle, Interac, UPI, Cash App, Venmo, Apple Pay, and Google Pay.
Provider availability is dynamic. Supported countries, payment methods, minimums, KYC requirements, fees, limits, and approval decisions vary by provider and may change. The plugin identifies discontinued or impaired routes in wp-admin; merchants should keep at least one active route enabled and review provider notices before accepting live orders.
Use existing orders to send expiring Pay Now links or display in-person QR codes. Use WooCommerce > Request Payment for standalone links and branded invoices. Automated Recovery follows up on eligible first-time abandoned sessions with merchant-controlled timing, incentives, backup providers, and reporting. Supported subscription plugins use scheduled, customer-authorized renewal links instead of silent stored-card rebilling.
Read about payment links, QR payments, Smart Recovery, and subscription workflows.
The intended settlement route is USDC on Polygon to the merchant’s configured wallet. The provider chooses the actual settlement at purchase time and may instead settle USDT, another stablecoin, or a native coin (ETH, POL or BNB) on Polygon, Ethereum or BNB Chain. The configured wallet address receives on all three networks, so it must be a self-custodial EVM wallet – not an exchange deposit address, which may not credit an unexpected asset or network. The plugin’s settlement verifier evaluates the actual on-chain result on whichever of these networks the payment landed and either completes the order when adequately proven or holds it for merchant review. Merchants must verify wallet compatibility and protect their private keys.
VERIFIED charges a 4% infrastructure fee on successfully confirmed transactions. The merchant can absorb it or add it as a customer-paid WooCommerce fee. Hosted providers charge separate provider-side conversion, payment, and possible network fees. Fees, net settlement, and timing vary by route; VERIFIED does not control provider pricing or guarantee settlement time. See the fees transparency guide and risk disclosure.
On-chain settlement does not create a traditional card-acquiring chargeback process against a WooCommerce merchant account. It does not eliminate customer disputes, fraud, provider action before settlement, blockchain risk, stablecoin risk, wallet risk, or legal obligations.
VERIFIED may fit merchants that want WooCommerce order control, hosted card-to-crypto execution, wallet settlement, multiple provider routes, or a continuity option when conventional acquiring is unavailable. It may not fit businesses that require fiat bank settlement, embedded card fields, silent stored-card rebilling, guaranteed approval, fixed provider availability, or freedom from customer identity verification.
Want to accept Zelle, Cash App or Venmo on your WooCommerce store? The plugin includes three optional manual payment methods for these services, free to use alongside the card-to-crypto checkout. They are off by default and USD only. Customers pay you directly; you confirm each payment yourself.
How it works:
Features:
Account eligibility: the plugin does not ask for or assume an account type. Please ensure your payment account is eligible for its intended use and complies with your payment provider’s applicable terms.
VERIFIED provides checkout software only. It does not process, receive, hold, transmit or verify these payments, and it does not connect to Zelle, Cash App or Venmo. Zelle and the Zelle related marks are owned by Early Warning Services, LLC; Cash App is a trademark of Block, Inc.; Venmo is a trademark of PayPal, Inc. They are used here only to identify the payment method. VERIFIED is not affiliated with, endorsed or sponsored by them.
Prefer card payments that confirm automatically? The same plugin includes VERIFIED card-to-crypto checkout (see above), and these manual methods keep working alongside it.
This plugin depends on external services. These services are contacted when a merchant configures the plugin, creates a checkout or payment request, generates a QR code, checks settlement, or synchronizes transaction records.
The plugin uses https://pay.verifiedcryptocheckout.com to create and route hosted checkout sessions and the VERIFIED service endpoint to synchronize limited financial and reconciliation metadata. Depending on the feature and privacy setting, transmitted data can include merchant site URL, order amount and currency, customer billing email, merchant wallet address, callback/status URLs, gateway/provider choice, fee values, transaction hash, and technical reconciliation identifiers. For orders placed with version 1.56.54 or later, Missed Payment Protection may also send the order’s payment status token to the same service to ask whether the order was paid; the answer is checked on-chain before it is reported. Optional Full Receipt mode also makes the selected order and billing details available to the hosted thank-you page.
Service: https://pay.verifiedcryptocheckout.com
Terms: https://verifiedcryptocheckout.com/terms/
Privacy: https://verifiedcryptocheckout.com/privacy/
Fees: https://verifiedcryptocheckout.com/fees/
Risk: https://verifiedcryptocheckout.com/risk/
Payment Request and In-Person QR features use QuickChart to render the QR image. The tokenized payment-link URL is sent to QuickChart only when the QR code is generated.
Service: https://quickchart.io
Privacy: https://quickchart.io/privacy/
Settlement Guard, Missed Payment Protection and the settlement-network lookup query public JSON-RPC endpoints of the supported networks (Polygon, Ethereum and BNB Chain) to verify public on-chain records. Requests can include public wallet addresses, transaction hashes, token-contract addresses, block ranges, and JSON-RPC method data; no WooCommerce customer record is sent. Endpoints used by the current code are operated by PublicNode (https://www.publicnode.com), dRPC (https://drpc.org) and BNB Chain (bsc-dataseed.bnbchain.org, bsc-dataseed.binance.org). An optional Etherscan API key enables faster lookups through the Etherscan API (https://etherscan.io) on the networks its plan covers. CoinGecko is queried for the public market price of supported native and wrapped coins when a non-stablecoin settlement must be valued.
Policies: PublicNode (https://www.publicnode.com/privacy), dRPC (https://drpc.org/privacy-policy), BNB Chain (https://www.bnbchain.org/en/privacy-policy), Etherscan (https://etherscan.io/privacyPolicy), and CoinGecko (https://www.coingecko.com/en/privacy). Transaction and address links open the block explorer of the network the payment settled on (Polygonscan, Etherscan or BscScan), or Blockscan (https://blockscan.com, privacy: https://blockscan.com/privacyPolicy) when the network is not yet known – only when an administrator or customer follows the displayed link.
The optional manual payment methods (Zelle, Cash App and Venmo) do not contact any external service. Customer-entered payer details stay in your WooCommerce order. The “Open Cash App” and “Open Venmo” buttons are ordinary links to cash.app and venmo.com that open only when a customer taps them, and they carry your receiving account, the order amount and, for Venmo, the payment memo. Each service’s own terms and privacy policy apply to payments made in its app.
The selected or routed provider receives the information entered on its hosted page and may collect payment credentials, identity documents, biometric/liveness data, contact information, device data, and other compliance information under its own terms. Provider identity is shown during the hosted flow. Providers are independent; references do not imply affiliation or endorsement. Availability and the provider roster change over time.
Provider privacy resources include Coinbase (https://www.coinbase.com/legal/privacy), Stix – used for Cash App, Apple Pay and Google Pay (https://stixramp.com/legal/privacy.php), Cash App (https://cash.app/legal/us/en-us/privacy), Venmo (https://venmo.com/legal/us-privacy-policy/), Apple Pay (https://www.apple.com/legal/privacy/), Google Pay (https://policies.google.com/privacy), Crypto.com (https://crypto.com/privacy/en), Stripe (https://stripe.com/privacy), PayPal (https://www.paypal.com/us/legalhub/paypal/privacy-full), Revolut (https://www.revolut.com/legal/privacy/), Transak (https://transak.com/privacy-policy), Ramp Network (https://rampnetwork.com/privacy-policy), Banxa (https://banxa.com/privacy-policy), Simplex (https://www.simplex.com/privacy-policy), Binance (https://www.binance.com/en/privacy), Robinhood (https://robinhood.com/us/en/about/legal/), Sardine (https://www.sardine.ai/legal/privacy-policy), Topper (https://topperpay.com/privacy), TransFi (https://www.transfi.com/privacy-policy), Unlimit (https://www.unlimit.com/privacy-policy/), Klarna (https://www.klarna.com/us/privacy/), iDEAL (https://www.ideal.nl/en/security-privacy/privacy-statement/), Blockchain.com (https://www.blockchain.com/legal/privacy), Guardarian (https://guardarian.com/privacy-policy), Particle (https://particle.network/privacy), Interac (https://www.interac.ca/en/privacy-policy/), and UPI/NPCI (https://www.npci.org.in/privacy-policy/). Review the provider named on the hosted page before submitting data.
The plugin does not store card numbers or CVV values in WordPress. WooCommerce continues to store the order and customer information required by the merchant’s normal ecommerce workflow. VERIFIED stores local order metadata, tokens, gateway settings, recovery history, and ledger/reconciliation records needed for enabled features. For Zelle, Cash App and Venmo orders it stores the payer name, sender account, payment memo and any confirmation number the customer provides; these are included in WooCommerce personal-data exports and removed by WooCommerce’s order data eraser. Merchants are responsible for their site privacy notice, data-retention choices, wallet security, and applicable law.