| 开发者 |
Ivno
loquisoft ivno |
|---|---|
| 更新时间 | 2026年8月4日 00:01 |
| PHP版本: | 5.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
?ivno_debug=1) works identically on both the classic shortcode checkout and the block-based checkout, making setup issues easy to self-diagnose./wp-content/plugins/ivno-payment-gateway/ directory, or install through the WordPress plugins screen.?ivno_debug=1 to your checkout page URL. This displays a diagnostic panel (on both classic and block-based checkout) showing whether the gateway is enabled, whether your credentials are configured and free of hidden characters, whether wallet-backed crypto assets were found, and whether your cart total meets the configured minimum order amount.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:
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:
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:
Each token is listed together with its specific network as a standalone selectable option. Current supported options are:
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 $10, 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.
To process payments, Ivno support USD, and EUR currencies. Please ensure your WooCommerce or store settings is set to any of these two currencies.
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, settlements are instant or by T+1. 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, 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:
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.
iv_live_ / iv_secret_, Test: iv_test_ / iv_test_secret_) for clearer environment identification.environment column to crypto wallets, crypto links, crypto subscriptions, and fiat subscriptions tables to fully separate Live and Sandbox data.?ivno_debug=1) previously only rendered on the classic shortcode checkout and never on block-based checkout, causing admins to see log entries with no corresponding on-page diagnostics. Both checkout types now share a single diagnostics source (get_debug_diagnostics()) and render an identical visual panel.trim() to strip BOM markers, zero-width characters, non-breaking spaces, and control characters that can be silently introduced via copy/paste and previously caused authentication to fail with no visible error. Existing stored credentials are automatically cleaned the next time settings are saved.ivno-blocks.js now includes defensive guard clauses that detect missing WooCommerce Blocks globals or missing localized settings and log clear, actionable console.error() messages instead of failing silently with no visible symptom.ivno-blocks.js from being served after plugin updates.