Plugin 0.4.1
Add Bitcoin, USDT, USDC, ETH and more to your WooCommerce checkout. BluPay handles the hosted payment flow and syncs confirmed payments back to your orders with signed webhooks.
Version 0.4.1 · Free plugin download. Payment processing and network fees apply.
Payment workflow
The enabled BluPay payment method starts hosted crypto checkout for the order.
Payment options follow the shop and invoice currency-network settings.
Signed webhooks update eligible orders through WooCommerce payment completion.
Test with your theme, checkout type, and extensions. Review unresolved payment updates before fulfilling an order.
Classic checkout plus WooCommerce Cart and Checkout blocks
Responsive admin settings in Persian and English
Exact Toman and Rial denomination mapping, including thousand-unit currencies
Read-only rate and fee previews for fiat currencies enabled in BluPay
Hosted crypto checkout keeps wallet complexity outside your store
Order updates through HMAC-signed webhooks with duplicate-event checks
Declares compatibility with WooCommerce High-Performance Order Storage (HPOS)
Sandbox keys let you simulate invoice and order updates without real funds
Download the BluPay ZIP, upload it in WordPress under Plugins → Add New Plugin, and activate it.
Save your sandbox shop API key and webhook secret in WooCommerce settings, then register the displayed webhook URL in that BluPay shop.
BluPay appears in classic and block checkout. Customers pay on a hosted page, and signed webhooks update each order after confirmation.
Upgrading from an older release needs one initial manual installation. Future updates appear in WordPress while BluPay is active; your saved settings and orders are retained.
BluPay requires WordPress 6.2 or newer, PHP 7.4 or newer, and WooCommerce 7.0 or newer. It declares compatibility with High-Performance Order Storage and WooCommerce Cart and Checkout blocks.
Version 0.4.1 was verified with WordPress 7.1.3, WooCommerce 11.2.1 and PHP 8.3. Test your theme, extensions and store currency in Sandbox before accepting live payments.
The customer selects “Pay with crypto,” then completes payment on BluPay’s hosted checkout using an enabled asset and network. Your store never needs to generate wallet addresses or watch blockchains directly.
BluPay sends signed invoice webhooks to your store. After successful payment completion, the plugin records the available invoice and payment details, such as transaction hash, crypto amount, asset and network.
Keep the original WooCommerce order amount and currency. The plugin maps Toman, Rial and their thousand-unit variants exactly; BluPay calculates the crypto equivalent when the customer selects an enabled asset and network.
Conversion covers IRT (Toman), IRR (Rial), USD, EUR, GBP, CAD, AUD, CHF and JPY when the corresponding invoice currencies and rate services are enabled in BluPay. Availability also depends on your shop’s payment methods and a current valid rate. Installing the plugin alone does not activate currency support in the service.
BluPay is a custodial gateway: confirmed funds are credited to your BluPay merchant balance. Toman and Rial invoice pricing does not provide Rial bank settlement.
The responsive Persian and English panel brings connection settings, currency checks, checkout preferences and diagnostics together. Test entered connection values, copy the webhook URL and show or hide your credentials.
Save your connection, then check currency support and preview a sample amount using a shop-enabled asset and network. Review the applied rate, providers, observation and expiry times, crypto equivalent, service fee, transfer fee and the payer for each fee.
These checks require compatible BluPay rate APIs. A preview creates no invoice, payment or wallet reservation and does not reserve the rate. Checkout calculates the final payment amount again; unavailable or expired rates produce no numerical preview.
The plugin is free to download. Payment processing and network costs follow BluPay’s current terms and your shop configuration. Review the service fee, transfer fee and payer settings for the selected asset and network.
From version 0.4.1, the active plugin checks signed BluPay release metadata through WordPress updates. Read the version details and changelog, then choose Update now. The package is checked before installation. Older versions need one initial manual upgrade to 0.4.1. PHP Sodium and normal WordPress update and filesystem permissions are required; an inactive plugin cannot run its update provider.
Your available assets follow the BluPay shop configuration. The supported-assets page lists the available integrations, including USDT, USDC, Bitcoin, Ethereum, and SOL. The checkout offers only currency-network pairs enabled for that shop and payment.
The BluPay plugin registers a payment method for classic checkout and WooCommerce Checkout blocks, and declares HPOS compatibility. Test it with your store’s theme and extensions before launch.
For an eligible Paid invoice, BluPay uses WooCommerce payment completion. WooCommerce normally selects Processing or Completed based on the order items; the Completed preference can mark a paid order complete. Unresolved completion needs review.
Yes. Use a BluPay sandbox shop API key to simulate invoice and order updates without sending real funds. The API key determines whether payments are sandbox or live; choosing Sandbox in the plugin settings does not change a live key into a sandbox key.
The original WooCommerce order amount and currency stay unchanged. IRT, TMN and TOMAN identify Toman; IRR, RLS and RIAL identify Rial. IRHT and IRHR amounts are multiplied by exactly 1,000 for the Toman or Rial invoice. For example, 250 IRHT becomes 250,000 IRT. Crypto conversion requires an enabled invoice currency and a current BluPay rate; fiat pricing does not provide Rial bank settlement.
No. The admin preview creates no invoice, payment or wallet reservation and does not change order amounts. It shows the current rate, its sources and validity, and the fee breakdown for your saved shop connection. Checkout calculates the actual amount again when the customer selects an asset and network. Unsupported currencies and unavailable or expired rates produce no numerical preview.
Choose Persian or English in your WordPress user profile. The plugin follows that language with right-to-left or left-to-right layout. The customer-facing payment title and description remain editable store settings; changing the admin language does not automatically translate those saved texts.
For a storefront without a BluPay plugin, use the REST API to create hosted checkout invoices and signed webhooks to update orders. Review the API contract and test your integration before launch.
Read developer documentationConfigure a shop and validate your payment flow in the sandbox.