Corexa crypto payment vs Paymento – Non-Custodial Crypto Payment Gateway for WooCommerce

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. Key Advantages Multi-Coin support – Accept BTC, ETH, USDT, SOL, XRP, BNB, PEPE, USDC, TRON, DOGE — and almost any other cryptocurrency your wallet supports. Smart checkout – Customers choose their favorite network easily. QR codes – Display wallet addresses and QR codes for quick scanning. Live updates – Automatic order status changes after cryptocurrency transactions are confirmed. Custom notes – Add friendly instructions for your buyers. Privacy first – We don’t store or handle your funds. Payments go directly from customer to merchant. Crypto payment gateway api – No API needed — the process is simple and beginner-friendly. How it works 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. External services 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: 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 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 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 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 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 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 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 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 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 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 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 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

Paymento – The Non-Custodial Crypto Payment Gateway for WooCommerce Paymento allows businesses and individuals to accept cryptocurrency payments directly into their own wallets, eliminating third-party risks, custody issues, and unnecessary fees. 🌟 Key Features: ✔ Direct Wallet Payments – No intermediaries, full control over your funds. ✔ Multi-Chain Support – Accept Bitcoin, Ethereum, USDT (ERC20 & TRC20), and more. ✔ Secure & Private – Non-custodial solution with no private key access required. ✔ Easy WooCommerce Integration – Install, configure, and start accepting crypto in minutes. ✔ WooCommerce Blocks Compatible – Works with both classic and modern block-based checkout. ✔ HPOS Compatible – Full support for High-Performance Order Storage. ✔ Low Transaction Fees – Save costs compared to traditional payment gateways. ✔ Developer-Friendly API – Expand functionality with simple API calls. Requirements WordPress 6.0 or higher WooCommerce 8.0 or higher PHP 8.0 or higher A Paymento merchant account Configuration Go to WooCommerce > Settings > Payments. Find “Paymento” in the list and click “Manage”. Enable the payment method by checking the “Enable/Disable” box. Fill in the following required fields: Title: The name of the payment method displayed to customers Description: A brief description of the payment method displayed to customer, you can mention the assets that you want to accept. API Key: Your Paymento API Key (available in your Paymento merchant dashboard) Secret Key: Your Paymento Secret Key (available in your Paymento merchant dashboard) Choose your preferred Confirmation Type: Redirect Immediately and Hold Invoice (Recommended) Wait for Payment Confirmation Optionally enable Debug Log for troubleshooting. Click “Save changes” to apply your settings. Usage Once configured, the Paymento payment option will appear on your WooCommerce checkout page. Customers can select this option to pay with cryptocurrency. Order Process Customer selects Paymento as the payment method and completes the order. They are redirected to the Paymento payment page to complete the transaction. After payment, the customer is redirected back to your store. The order status is updated based on the payment status and your chosen confirmation type. External Services This plugin connects to the Paymento API to process cryptocurrency payments. Paymento is a non-custodial payment gateway that enables WooCommerce stores to accept payments in Bitcoin, Ethereum, USDT, and other cryptocurrencies. 📌 Data Sent to Paymento API The plugin makes exactly four types of request to the Paymento API, each with a specific trigger. No request is made on ordinary page views. Submitting Payment Requests Endpoint: https://api.paymento.io/v1/payment/request Triggered when a customer places an order and chooses Paymento at checkout. Data sent: order total, currency, order ID, the return URL on your store, and your API Key. Paymento returns a payment token used to generate the invoice. Payment Verification Endpoint: https://api.paymento.io/v1/payment/verify Triggered only when Paymento notifies your store of a paid order via webhook (IPN). Data sent: the payment token for that order, and your API Key. Used to confirm the notification is genuine before the order is completed. Fetching Merchant Information Endpoint: https://api.paymento.io/v1/ping/merchant/ Triggered only when an administrator saves the gateway settings in WooCommerce. Data sent: your API Key. Returns your registered merchant name and account status, which are stored locally and shown on the settings screen. Setting Callback URLs Endpoint: https://api.paymento.io/v1/payment/settings/ Triggered only when an administrator saves the gateway settings, after the merchant check above succeeds. Data sent: your store’s webhook (IPN) URL and your API Key, so Paymento knows where to send payment notifications. 📌 Customer Redirect After an order is placed, the customer’s browser is redirected to https://app.paymento.io/gateway with the payment token for that order, where they complete the payment. No other customer data is included in the redirect. 📌 Data Received Paymento sends payment status notifications to /wp-json/paymento/result on your store. Every notification is verified with an HMAC SHA256 signature using your Secret Key before it is processed. 🔗 Third-Party Policies By using this plugin, your WooCommerce store communicates with Paymento API. You can review Paymento’s terms and policies here: Terms of Service: https://paymento.io/terms Privacy Policy: https://paymento.io/privacy This ensures users are fully aware of the data being sent and why. 🚀 Troubleshooting If you encounter any issues: Enable Debug Log in the plugin settings. Check the WooCommerce status report (WooCommerce > Status > Logs) for detailed error messages. Ensure your API Key and Secret Key are correct. Verify that your server can receive incoming webhooks from Paymento. Support For support, please open an issue on the GitHub repository or contact Paymento support for gateway-specific questions. Contributing Contributions to improve the plugin are welcome. Please fork the repository and submit a pull request with your changes. License This plugin is released under the GPLv2 or later license.