| 开发者 | qbitflow |
|---|---|
| 更新时间 | 2026年7月31日 07:08 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
qbitflow-for-woocommerce folder to /wp-content/plugins/)Sign up at qbitflow.app and generate an API key from your dashboard.
ETH, SOL, USDC, USDT, and more. Check the QBitFlow dashboard for the full list.
No. QBitFlow is fully non-custodial. Payments go directly to your wallet via smart contracts.
Yes. The plugin supports both the classic shortcode checkout and the new WooCommerce block-based checkout.
Customers request a refund from their QBitFlow invoice page; you approve or refuse it in the QBitFlow dashboard. Once you approve a refund and the on-chain refund settles, a notice at the top of the order screen shows a Sync refund to WooCommerce button; clicking it marks the WooCommerce order Refunded and adds a note recording the refund transaction hash. The order's QBitFlow meta box shows the current refund status at all times. While a request is still pending, an admin notice keeps it on your radar with a one-click link to the QBitFlow refund queue. Only full refunds are supported (blockchain transactions are irreversible, so partial refunds aren't applicable).
Yes! Create a Test API Key from your QBitFlow dashboard and use it in the plugin settings. You can simulate the entire payment flow without spending any cryptocurrency. See the Test Mode Documentation for details.
Test API keys will not process real transactions. Make sure to replace your test key with a live key before launching your store.
edit_shop_orders) action that marks the order Refunded, records the refund tx hash, and adds an order noteRequires Plugins: woocommerce header so WordPress enforces the WooCommerce dependency before activation.wordpress-org, raw screenshots, dev docs); added a build.sh/.distignore build pipelineGET /customer/email/{email} first, POST /customer only when missing) so the QBitFlow checkout never re-prompts the buyer for details WooCommerce already has/transaction/session-checkout/new/payment; fixed customerUUID field casinguninstall.php cleans up plugin options, the email → UUID map, and the legacy customer-uuid user meta on deletionTested up to: 7.0 and WC tested up to: 9.7 (in sync with readme)languages/qbitflow-for-woocommerce.pot)permission_callback auth model with inline commentmeta_query; remaining structural warnings annotated with justified phpcs:ignore commentsqbitflow-for-woocommerce to comply with the WordPress.org trademark policy (settings option name and gateway ID unchanged, so existing installs preserve their API key and order history)