Ivno Payment Gateway with Instant Approval

Ivno supports traditional fiat payment methods such as major credit/debit cards, Apple Pay, and Google Pay. It also supports crypto checkout when enabled by the merchant.

Supported crypto options include:
* Bitcoin (BTC) — Bitcoin
* Ethereum (ETH) — Ethereum
* Solana (SOL) — Solana
* Litecoin (LTC) — Litecoin
* Monero (XMR) — Monero
* Polygon (Pol) — Polygon
* Ripple (XRP) — XRP Ledger
* Dogecoin (DOGE) — Dogecoin
* Cardano (ADA) — Cardano
* Tron (TRX) — Tron
* Tether (USDT) — Tron
* Tether (USDT) — Ethereum
* Tether (USDT) — Polygon
* Tether (USDT) — BNB Smart Chain
* USD Coin (USDC) — Polygon
* USD Coin (USDC) — Ethereum
* USD Coin (USDC) — BNB Smart Chain
* USD Coin (USDC) — Arbitrum
* USD Coin (USDC) — Optimism
* USD Coin (USDC) — Solana

Yes. The WooCommerce plugin can offer both traditional card methods and crypto inside the same Ivno payment method. Customers can choose whether they want to pay by Card / Apple Pay / Google Pay or by Crypto.

Yes. On fresh installation/configuration, both fiat/card payments and crypto payments are enabled by default. Merchants can manually disable crypto or fiat later from the WooCommerce Ivno gateway settings.

Yes. If both fiat and crypto are enabled and available, the checkout will preselect Crypto by default unless the customer changes it.

Yes. Version 2.1.1 adds a merchant setting that allows you to disable the Card / Fiat option from checkout while still keeping crypto enabled. This is useful if you want Ivno to operate as a crypto-only payment gateway on WooCommerce.

Yes. Version 2.0.0 adds a new Enabled Cryptocurrencies setting in the WooCommerce Ivno gateway configuration. This lets you show only the crypto asset/network combinations you want customers to see.

This is especially useful if:
* you have not yet configured a payout wallet for a specific crypto
* you want to temporarily stop accepting a particular asset or network
* you want a smaller, simpler crypto list at checkout

Yes. Version 2.2.2 ensures that a cryptocurrency/network method is automatically hidden from WooCommerce checkout if the merchant has not entered and saved a matching payout wallet for that crypto in the Ivno Crypto Merchant Dashboard.

This helps prevent customers from selecting a crypto payment method that is not actually ready to receive payouts.

Yes. Ivno provides API support and can be used beyond WooCommerce.

In addition to WooCommerce, Ivno supports or can be integrated with platforms such as:
* Shopify
* WHMCS
* PrestaShop
* OpenCart
* Magento
* BigCommerce
* Ecwid
* Spree Commerce
* Shopware
* Shift4Shop
* Commercetools
* Elastic Path
* Drupal Commerce
* Volusion
* Wix eCommerce
* Miva
* XenForo
* NamelessMC
* Paymenter

and more through custom API-based integration.

If your platform is not listed above, you can still contact Ivno for custom integration options using the Ivno API.

Each token is listed together with its specific network as a standalone selectable option.

Current supported options are:
* BTC — Bitcoin
* ETH — Ethereum
* SOL — Solana
* LTC — Litecoin
* XMR — Monero
* POL — Polygon
* XRP — XRP Ledger
* DOGE — Dogecoin
* ADA — Cardano
* TRX — Tron
* USDT — Tron
* USDT — Ethereum
* USDT — Polygon
* USDT — BNB Smart Chain
* USDC — Polygon
* USDC — Ethereum
* USDC — BNB Smart Chain
* USDC — Arbitrum
* USDC — Optimism
* USDC — Solana

Go to WooCommerce → Settings → Payments → Ivno Payment Gateway and enable the Crypto Option. Then paste your Crypto API Key, Crypto API Secret, and Crypto Webhook Secret from your Merchant Dashboard.

You can also use the Enabled Cryptocurrencies setting to limit checkout visibility to only the assets and networks you want customers to use.

As of the current version, the minimum order amount is merchant-configurable via the Minimum Order Amount setting in WooCommerce → Settings → Payments → Ivno Payment Gateway. It defaults to $20, matching prior plugin behavior, but can be raised, lowered, or set to 0 to disable the minimum entirely. This threshold is enforced identically whether your store uses the classic checkout or the block-based checkout.

This is almost always one of the following: the gateway’s Enable/Disable toggle is not actually saved as enabled, one of your API credential fields contains invisible/hidden characters from copy-pasting, or your test cart total is below the configured Minimum Order Amount. As an administrator, add ?ivno_debug=1 to your checkout page URL to see a full diagnostic panel that checks all of these automatically. This diagnostic panel works identically on both classic and block-based checkout as of version 2.4.4.

Ivno uses USDC payouts for fiat/card-based payments, with consolidated settlement to the merchant by T+21. For crypto checkout, merchants receive the original cryptocurrency paid by the customer instead of a USDC-converted payout.

For fiat settlement, configure your payout settings in the Merchant Dashboard. For crypto settlement, you need the appropriate wallet addresses configured for the crypto assets and networks you want to accept, such as BTC, ETH, SOL, LTC, XMR, POL, XRP, DOGE, ADA, TRX, USDT on supported networks, and USDC on supported networks.

Yes. Crypto uses a dedicated Crypto Webhook Secret from your Merchant Dashboard. This allows WooCommerce to securely verify crypto payment updates.

Customers can pay by:
1. Card / Apple Pay / Google Pay, or
2. Cryptocurrency.

For fiat, the usual Ivno fiat flow is used, and merchant payouts are settled in USDC by T+21.
For crypto, a crypto checkout session is created and the customer is redirected or shown a modal checkout, and the merchant receives the original cryptocurrency paid by the customer.

Only merchant-enabled payment modes and crypto asset/network combinations with configured wallets are shown to customers at checkout.

Ivno uses secure API authentication, webhook signature verification, wallet validation, encrypted payment flows, and server-side crypto selection validation for both fiat and crypto modes.

If a payment fails, WooCommerce will remain pending or be updated to failed depending on the payment status callback.