BoltUtil Payments for WooCommerce

By BoltUtil

0+ active installationsVersion 0.6.3

Accept USDT and supported USDC payments through BoltUtil Hosted Checkout. Funds go directly to the merchant's configured wallet.

Description

BoltUtil is a USDT and USDC payment gateway for WooCommerce, connecting your WordPress store to the BoltUtil stablecoin payment service. Customers select a token and network, place an order, and continue to BoltUtil Hosted Checkout. They can use wallet payment or manual transfer. BoltUtil displays the receiving address and exact payable amount, monitors the network, and reports the confirmed result to WooCommerce. The plugin does not receive cryptocurrency or store wallet private keys or recovery phrases.

Stablecoin payments for WooCommerce

  • Use a unified BoltUtil card with a USDT/USDC switch in invoice payments, Classic Checkout and Checkout Blocks.
  • Accept USDT (Tether) and USDC payments on eligible merchant-enabled routes.
  • Offer connected-wallet checkout with the address and exact amount filled in, or manual transfer with a QR code and receiving address.
  • Support six networks: TRON (TRC20), Ethereum (ERC20), BNB Smart Chain (BEP20), Polygon PoS, Solana and Base. USDT has six routes and USDC five; available options depend on the merchant and service configuration.
  • Receive payments directly in your configured wallet. The plugin does not hold customer funds or wallet private keys.
  • Update WooCommerce orders after verified payment status and signed Webhooks; support merchant-scoped status rechecks.
  • Integrate with Classic Checkout, Cart and Checkout Blocks, and WooCommerce High-Performance Order Storage (HPOS).

Try the WooCommerce demo store | Setup guide | BoltUtil website | Current plans

The demo store has test-only digital sample products and uses real funds for submitted payments. Its interactive checkout preview is illustrative and cannot be used to transfer funds.

USDT supports TRON (TRC20), Ethereum (ERC20), BNB Smart Chain (BEP20), Polygon PoS, and Solana. Native USDC supports Ethereum, Polygon PoS, and Solana; Binance-Peg USDC supports BNB Smart Chain (BEP20). These routes require activation by BoltUtil. Checkout offers only routes enabled in the service and plugin, with an active merchant receiving wallet. Existing installations default to USDT only. Base supports native USDC and Bridged USDT; other assets and networks are not supported.

Only WooCommerce stores using USD are supported. The USD numeric order total is the stablecoin invoice basis; this release does not provide a live exchange-rate quote or lock. The exact stablecoin amount displayed on BoltUtil Hosted Checkout is the amount to pay. Network transaction fees are charged by the customer’s wallet or network, separately from the invoice amount.

BoltUtil is an external service required for this plugin. Merchants must register a BoltUtil account, create a LIVE API key, configure receiving wallets and an active Webhook, and enter the key and Webhook secret in the gateway settings. A free order allowance is available each day; subscription plans have no daily order limit. Current allowances, plan benefits and fees are described at https://boltutil.com/pricing . The service, rather than plugin code, enforces account limits.

When a customer checks out, the plugin sends the order amount, USD currency, selected USDT or USDC token, selected network, a store-specific external order ID, the store’s return URL, and a merchant reference to BoltUtil over HTTPS. It sends the merchant API key and a signed request; it does not send the customer’s wallet private key. The plugin receives signed payment events and queries BoltUtil to verify status before completing a WooCommerce order. See https://boltutil.com/privacy and https://boltutil.com/terms for BoltUtil service policies. The merchant remains responsible for their store’s own privacy notice and payment disclosures.

Installation

  1. Install and activate WooCommerce, then install this plugin.
  2. Set the WooCommerce store currency to USD.
  3. In BoltUtil, create a LIVE API key, enable a receiving wallet for each desired network, and create an active Webhook using the URL shown in WooCommerce > Settings > Payments > BoltUtil Payments.
  4. Enter the LIVE API key and the matching Webhook secret in the gateway settings. Select stablecoins and networks backed by active receiving wallets, enable the gateway, and save.
  5. Place an unpaid order to check the network choice, BoltUtil redirect, amount, address, and return link. Returning to the store does not mark the order paid.

FAQ

Can customers connect a wallet instead of entering the amount manually?

BoltUtil Hosted Checkout offers connected-wallet payment on supported devices and networks. The receiving address and exact amount are filled in; the customer reviews and confirms in the wallet. Manual transfer remains available. Availability depends on the selected token, network, device and wallet, and is handled by the BoltUtil service rather than a wallet SDK bundled in this plugin.

Does the plugin store my wallet private key?

No. Receiving wallets are configured in BoltUtil. The plugin stores the merchant’s API key and Webhook secret encrypted using the WordPress site’s authentication salts. Keep the WordPress installation and its salts secure.

Why do the credential fields show masked text after saving?

The masked preview shows only the credential type and last four characters; the actual input value remains empty. Leaving the input blank during a later save keeps the existing credential.

When is a WooCommerce order marked paid?

Only after BoltUtil confirms payment and the plugin verifies the signed Webhook and payment status, or after a merchant-scoped status reconciliation. A browser redirect back to the store is not proof of payment.

Can customers pay with USDC or on Base?

Native USDC on Ethereum, Polygon PoS and Solana, and Binance-Peg USDC on BNB Smart Chain (BEP20), are available only when the service activates the route and the merchant enables USDC in plugin settings. Base supports native USDC and Bridged USDT when the backend, receiving wallet and plugin settings enable the route. Base uses L2 confirmation by default and confirms an order after the configured requirements are met. Strict mode waits for L1 finality. Timing depends on network and service conditions; no fixed confirmation time is guaranteed. Planned or inactive routes are never offered.

Which languages are available?

English is the fallback. The GitHub installation ZIP includes English source text and eleven bundled translations. The WordPress.org edition uses WordPress language packs; available translations depend on published packs and the selected WordPress locale. Merchant-written checkout labels are not translated automatically.

What happens when a payment needs investigation?

The WooCommerce order displays the BoltUtil payment ID, stablecoin, network, invoice amount, and payable amount. An administrator can use the Recheck BoltUtil payment order action. Payment exceptions should also be reviewed in the BoltUtil merchant dashboard.

What happens if a payment expires or fails?

When BoltUtil verifies an EXPIRED, FAILED, or CANCELLED payment, the plugin marks the unpaid WooCommerce order Failed and records the BoltUtil status in its order notes. A buyer must place a new WooCommerce order to make a new payment attempt. Any unexpected late transfer or amount discrepancy needs merchant review in BoltUtil; the plugin never marks an underpaid order paid automatically.

Where can merchants get support?

Use https://github.com/boltutil/boltutil-payments-for-woocommerce/issues for plugin setup questions. The plugin support forum is available at https://wordpress.org/support/plugin/boltutil-payments-for-woocommerce/ . For BoltUtil account, API, wallet, or payment issues, email support@boltutil.com. Do not include API keys, Webhook secrets, private keys, or recovery phrases in a support request.

Screenshots

Changelog

0.6.3

  • Unify invoice payment, Classic Checkout and Checkout Blocks with the BoltUtil checkout card, typography, controls and original project image assets.
  • Add a native order-payment layout when BoltUtil is the only available gateway, preserving order permissions, terms, nonce and submit hooks.
  • Require an explicit network choice after changing assets, while retaining valid same-asset choices through classic checkout refreshes.
  • Load checkout styles on pages containing Checkout Blocks, including non-default checkout URLs.
  • Update all eleven bundled translations, GitHub documentation and actual local WooCommerce screenshots.

0.6.2

  • Align checkout brand, stablecoin and network badges in Classic Checkout and Checkout Blocks, including narrow screens and RTL layouts.
  • Replace the generic Base illustration with a locally rendered blue-square identifier and keep asset provenance documented.
  • Order payment networks by BoltUtil network ID, with the original catalog order as a fallback for older services.
  • Refresh checkout styles and network artwork by content hash to avoid stale cached assets after reinstalling.
  • Preserve merchant settings, existing orders, payment amounts, signatures and verified payment-completion rules.

0.6.1

  • Describe daily free allowances and unlimited daily subscription orders without hardcoding a quota; link to the current BoltUtil plans.
  • Use documented CC0 network artwork and an original GPL Base network illustration for directory distribution.
  • Reject malformed Webhook event IDs without a PHP type error.
  • Align the WordPress minimum with the required WooCommerce 11.1 release.

0.6.0

  • Let buyers choose USDT or USDC first, then show only eligible payment networks.
  • Preserve the selected network when switching coins where that combination is available.
  • Keep coin and network choices through classic checkout refreshes; validate routes server-side.
  • Restore the Solana black circular mark and gradient bars.

0.5.3

  • Replace Polygon, BNB Chain and Base illustrations with unchanged SVGs from their official brand resources.
  • Preserve logo proportions and improve contrast and clear space in classic and block checkout.
  • Version network icon URLs so upgrades do not display cached legacy artwork.
  • Record official asset sources and distinguish their usage terms from CC0 artwork.

0.5.2

  • Add service-enabled Base native USDC and Bridged USDT routes with explicit labels.
  • Add an original GPL generic network illustration for Base.

0.5.1

  • Add service-enabled Binance-Peg USDC on BNB Smart Chain (BEP20) and explicit representation labels in classic and block checkout.
  • Preserve API symbols and USDT-only upgrade defaults.

0.5.0

  • Add merchant-controlled stablecoin selection and server-authoritative network/asset routes.
  • Support native USDC on service-enabled Ethereum, Polygon PoS and Solana routes.
  • Preserve old USDT orders and settings; verify stored asset identity in Webhooks and reconciliation.
  • Add the CC0 USDC icon and update multilingual configuration guidance.

0.4.21

  • Log a safe WooCommerce warning when a payment status check cannot be verified, so merchants can investigate orders that remain On hold.

0.4.20

  • Continue scheduled status checks for unpaid orders until BoltUtil reports a verified final status. The previous check mistakenly treated its own running Action Scheduler task as a pending follow-up.

0.4.19

  • Declare tested WooCommerce 11.1 compatibility for HPOS and Cart and Checkout Blocks.
  • Prepare the WordPress.org listing and release checks. Payment creation, monitoring, and Webhook behavior are unchanged.

0.4.18

  • Publish source documentation and the GPL license, with comments explaining API signing, retries, decimal comparison, and Webhook verification. Payment behavior is unchanged.

0.4.17

  • Package the CC0 icon license as a text file recognized by WordPress Plugin Check.

0.4.16

  • Replace the network and USDT images with CC0 artwork distributed with a source and license notice.
  • Send LIVE payment API requests only to the official BoltUtil API origin, including on upgraded stores.
  • Clean release packages of editor backup files and keep credentials out of distributable ZIPs.

0.4.15

  • Remove the square WooCommerce Blocks side rails around the BoltUtil payment option and use light network cards with a clear selected state.
  • Add pricing, documentation, terms, and support links to the BoltUtil settings menu and installed-plugin row.

0.4.14

  • Match the BoltUtil checkout network choices with chain and USDT image badges in Classic Checkout and Checkout Blocks.
  • Keep the network names visible so the payment options remain identifiable when images cannot load, and show a masked credential hint without submitting it as a new key.

0.4.13

  • Register WooCommerce gateway hooks once so status reconciliation does not duplicate the BoltUtil details panel or manual order actions.

0.4.12

  • Mark an unpaid WooCommerce order Failed after a merchant-scoped BoltUtil status read verifies EXPIRED, FAILED, or CANCELLED, while retaining the status in an order note.
  • Keep amount discrepancies for merchant review and preserve the existing completion verification path.

0.4.11

  • Added bundled translations for Spanish, Brazilian Portuguese, Russian, Vietnamese, Turkish, Japanese, Korean, Arabic, French, and Hindi, alongside English source text and Simplified Chinese.
  • Interface language follows the WordPress locale; English remains the fallback when a translation is unavailable.

0.4.10

  • Added a complete Simplified Chinese PO/MO language pack and a bundled translation path for ZIP installations.
  • Let WordPress translations control the display language, including Traditional Chinese and future community translations.

0.4.9

  • Clarified a translated payment-status placeholder and removed obsolete manual text-domain loading.
  • Hardened secret-field input handling and escaped the Webhook event table identifier in SQL.

0.4.8

  • Prepared WordPress.org release metadata and documented the current USDT scope and external service requirements.
  • Kept the existing WooCommerce gateway ID and payment behavior unchanged.
  • Replaced bundled chain and token artwork with text badges for clear distribution rights.
  • Made English interface strings available to standard WordPress translation tools.