Crypto payment gateways for online stores 2026
Compare crypto payment gateways by what customers pay and merchants receive, including confirmation, conversion, refunds and the records an order needs.
- Published
- Last updated
A crypto payment gateway turns a store’s payment request into a cryptocurrency payment, reports its status and manages the agreed merchant settlement. The customer’s chosen coin and network can differ from the currency your store ultimately receives.
For Australian retailers, merchant eligibility comes before integration. CoinGate lists Australia among supported countries. BitPay has paused new Australian merchant onboarding, and Stripe’s stablecoin payment method does not list Australian businesses as eligible. Those differences can rule out an otherwise suitable payment flow.
What a crypto payment gateway does
A crypto payment gateway connects the retail order to a payment record, but the gateway is only one part of the transaction. Identify each part before deciding what customers can use.
| Part | Meaning | Example |
|---|---|---|
| Gateway or processor | Creates the payment request and tracks its outcome | A hosted invoice connected to your order |
| Asset | What the customer transfers | Bitcoin (BTC), Ether (ETH), USDC or USDT |
| Network | Where the transfer happens | Bitcoin, Ethereum or Solana |
| Wallet | Software or hardware used to authorise a transfer | The customer’s wallet signing a payment |
| Settlement currency | What the merchant receives under the provider agreement | Fiat money in a bank account or crypto in a supported balance |
USDC and USDT are different stablecoins. Each aims to track the US dollar, and each has its own issuer and supported networks. A USDT payment requires support for that exact token on that exact network. A gateway accepting Bitcoin does not automatically accept every stablecoin.
Provider-managed acceptance delegates invoice tracking and conversion to a service. Your store still owns order fulfilment and customer support. A direct wallet route gives your store responsibility for matching incoming transfers to orders and setting confirmation rules. Your store also controls wallet access and sends refunds itself.
A plain wallet address cannot identify which of several similar orders a transfer belongs to. A direct implementation therefore needs a payment-reference strategy, transaction monitoring and a record of who can move the funds. It also needs a separate conversion route if the merchant wants bank settlement.
CoinGate documents a hosted checkout, storefront plugins and an application programming interface (API) for custom integration. Its checkout service lets merchants convert receipts or keep supported crypto balances. BitPay likewise requires a merchant account and configured settlement preferences. An API is the connection your software uses, not a separate currency or payment method.
Compare confirmation and settlement
Payment submission, permission to fulfil the order and merchant settlement are separate events. A customer’s wallet screenshot proves none of those events in your store’s own records.
Consider a fictional order through an existing, eligible BitPay merchant account. This illustrates BitPay’s documented states, including the distinction between its fulfilment signal and the merchant’s balance. It does not imply new Australian accounts can onboard.
- The store creates an invoice in its chosen pricing currency. The customer receives a cryptocurrency amount due, with a 15-minute payment window.
- The customer sends the requested Bitcoin amount before expiry. Under the medium-speed setting, the invoice moves from
newtopaidwhile network validation continues. - The invoice reaches
confirmedunder that setting. BitPay identifies this as the fulfilment signal. Staff match the invoice identifier to the retail order. - The invoice reaches
complete. BitPay credits the merchant account in the configured settlement currency. The later bank deposit is another record.
BitPay’s invoice-state documentation makes the confirmation behaviour dependent on transaction-speed settings. Other settings can change or skip a state. Avoid applying one provider’s state names to another provider’s checkout.
A payment notification also needs verification. BitPay says its notifications are unsigned and instructs merchants to retrieve the invoice to verify its status. Use its webhook verification procedure before a custom integration changes the order state.
For any provider, retain the original order amount and currency beside the requested asset amount. Record the network and invoice expiry as well. Reconcile the payment identifier to the provider balance, then reconcile that balance to the eventual payout. A received notification alone does not prove the bank received funds.
Plan refunds and customer support
A crypto refund is a new transfer authorised through the merchant’s refund process. Its amount and destination depend on the provider’s rules, so staff need the original payment record before promising an outcome.
BitPay lets merchants refund all or part of a fully paid invoice. Its refund rules use the original fiat invoice value, converted to cryptocurrency at the rate when the customer claims the refund. The customer can therefore receive a different crypto quantity from the quantity originally sent.
BitPay requires a sufficient merchant balance to fund the refund. Its customer process includes a refund claim and a final notification when the transfer executes. Save the refund record with the original invoice, rather than treating a sent refund email as completion.
CoinGate’s merchant refund process lets staff select an amount and supported currency from the original order. The customer supplies the wallet address and network, and CoinGate requests confirmation where needed. Staff can track refund status through the dashboard or API. A different refund currency can require conversion and a conversion fee.
The customer-support response must reflect the provider record:
| Situation | What staff can say | Record needed before changing the order |
|---|---|---|
| Underpayment | The payment has not covered the invoice. We’re checking the payment exception and refund route. | Invoice amount due and received amount |
| Delayed confirmation | Your transfer is recorded, and confirmation is still pending. We’ll update the order when the provider confirms its status. | Retrieved provider status and transaction reference |
| Screenshot without a matching payment | We’re checking the invoice and transaction reference against our payment records. | Matching invoice and verified payment status |
| Refund requested | Your refund request is recorded. We’ll confirm when the transfer completes. | Refund identifier and completed status |
Use those responses only when their stated facts are present. If a connection fails, staff must establish the provider status before promising dispatch or another payment attempt. Asking the customer to pay again too early can create a duplicate payment.
Check the operating requirements
Choose a provider only after its merchant eligibility, settlement route and support process fit your business. For a new Australian merchant, CoinGate’s country listing makes it a candidate for onboarding assessment. BitPay’s pause and Stripe’s business-location restriction exclude them as immediate new-account options under their published rules.
Provider operating models
| Provider | Assets and networks | Custody and confirmation | Merchant settlement | Australian merchant eligibility |
|---|---|---|---|---|
| CoinGate | Bitcoin on-chain or Lightning, plus USDC on supported networks including Ethereum and Solana | Provider-managed account balances and order status | Supported crypto or fiat, including EUR, GBP and USD | Australia appears on its supported-country list, subject to account approval |
| BitPay | Bitcoin on-chain or Lightning, Ether and supported tokens, with network and location restrictions | Provider account credited at complete; fulfilment follows configured invoice states | Supported crypto, bank settlement or a mix | New Australian merchant onboarding is paused |
| Stripe stablecoin payments | USDC on supported networks including Ethereum, Solana, Polygon and Base | Customer authorises a wallet payment; completed funds enter the Stripe balance | Local-currency Stripe balance for eligible businesses | Australia is absent from its supported business locations |
CoinGate’s supported-country list establishes country coverage, not approval for every business activity. Its currency matrix separates accepted assets from settlement and withdrawal support. Its published fiat options do not establish an Australian-dollar payout route.
BitPay’s country policy explicitly records the Australian onboarding pause. Its accepted-currency list also makes payment availability dependent on location. Existing merchants need their approved account settings to determine their available route.
Stripe’s stablecoin payment documentation supports full and partial refunds to the customer’s original wallet in stablecoins. It lists US business availability and private-preview regions, with Australia absent. A customer’s ability to pay from Australia does not establish Australian merchant eligibility.
Integration, refunds and fees
| Provider | Storefront connection | Refund basis | Fee categories to budget |
|---|---|---|---|
| CoinGate | Official plugins include WooCommerce and Wix, with hosted checkout and API routes | Merchant-selected amount and supported currency, linked to the original order | Processing, manual conversion, withdrawals and refunds, with network costs where applicable |
| BitPay | Documented WooCommerce plugin or custom API connection | Original fiat invoice value paid back in crypto, with full or partial refunds | Processing and applicable application, settlement or network charges under the agreement |
| Stripe stablecoin payments | Stripe Checkout or Elements for eligible businesses | Full or partial refund returned in stablecoins to the original wallet | Applicable payment-method pricing and account conversion or payout charges |
CoinGate’s pricing page distinguishes processing from manual conversion and withdrawal costs. Its refund conversion fee applies when the currencies differ. BitPay’s pricing information and merchant agreement define its applicable processing terms. Compare those categories against your expected order size and refund workload without assuming crypto costs less than cards.
A white-label crypto gateway is infrastructure sold under another business’s branding. It does not establish a supported asset, Australian eligibility or a native storefront plugin. Identify the contracting provider and who holds funds, then confirm which documented product the proposed integration uses. Keep trading, custody and merchant checkout products separate even when one vendor sells all of them.
Australian records and controlled acceptance
Australian tax and regulatory duties depend on the transaction and services involved. The Australian Taxation Office explains that crypto assets used in business can affect income tax and goods and services tax (GST). Its digital-currency payment guidance requires GST reporting in dollars for taxable supplies. Preserve the conversion evidence needed for the tax invoice and accounting records.
AUSTRAC’s virtual asset designated-services guidance covers exchange, safekeeping and transfers on behalf of customers, with geographical and transitional conditions. Compare your actual services and the provider’s role against that guidance. Offering a retail payment button alone does not establish which designated services either business provides.
Give staff separate authority for order support, refunds and settlement changes. Restrict API credentials to the actions the integration needs. Export payment and refund records for reconciliation, including provider fees and the final payout reference.
Before enabling the payment method, use the selected provider’s isolated test environment:
- Create one test order and save its invoice identifier, amount, network and expiry.
- Follow the documented successful-payment path and confirm that the saved order changes only after verified provider status.
- Exercise an expired or underpaid invoice. Confirm that the order remains unfulfilled and the support queue records the exception.
- Submit a supported refund and retain its completed record. Reconcile the test payment, fee and refund records without relying on a customer-facing success screen.
BitPay documents test accounts and testnet payments for integration checks. A successful test establishes the tested flow, while production activation still depends on merchant approval. Enable the chosen method only when your staff can trace an order through payment confirmation, settlement and a completed refund using the records they will have in daily work.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.