Which Payment Status Should Mark a WooCommerce Order as Paid?

Start With the Status, Not the Coin List

When you add crypto to a WooCommerce store, the most useful question is not which coins to list. It is which payment status your store will treat as permission to fulfil the order. Decide this before you choose a provider, because plugins handle statuses differently.

Keep the Order as the Source of Truth

MiraclePay describes its ecommerce approach as keeping the order as the source of truth, connecting payment creation, wallet instructions, confirmation and settlement context around the order your systems already understand. Its WooCommerce page adds that the merchant keeps the existing order flow and receives a status the store can use for its own fulfillment policy. In practice, write down which status releases goods, who reviews exceptions, and what support tells a customer whose payment is still pending.

What Another Plugin Lets You Configure

Comparing providers helps here. CoinGate's WooCommerce setup guide says merchants can set order status mappings in the plugin settings, and explains that a "Do nothing" option leaves the WooCommerce order status unchanged when a callback arrives. That flexibility is useful, but a careless mapping could move orders along before you intend. Review every default instead of assuming it matches your policy.

Match the Setup Path to Your Timeline

The onboarding routes differ. MiraclePay's plugin starts with business approval and KYB, followed by an API key you enter in the plugin settings. It is aimed at eligible U.S. merchants, and New York State is not currently eligible. CoinGate's guide describes a verified business account, an API token and a sandbox with a Test Mode switch. Plan your launch date around whichever route you choose.

A Short Pre-Launch Checklist

Before going live, confirm four things: the assets and networks approved for your account, the single status that moves an order forward, the message shown to a shopper whose payment is incomplete, and who handles exceptions. Then place an internal test order and watch the status travel from cart to confirmation.

If those answers are written down, the plugin becomes a configuration task rather than a policy debate. If they are not, no plugin will settle them for you.