Accept Stablecoin Payments: Setup Guide for SMBs (Shopify, Woo, Custom)
Most SMBs accept stablecoin payments through one of three paths: a Shopify or WooCommerce plugin that wraps a third-party processor, a hosted checkout from Bridge or Stripe, or a direct wallet integration. Pick by settlement preference: fiat at the bank, stablecoin in a wallet, or both. Setup runs from one hour to two weeks.
The market got crowded fast in 2025-2026. Stripe added native stablecoin checkout. Bridge.xyz (now part of Stripe) shipped orchestration APIs. Coinbase Commerce, BitPay, NOWPayments, and CoinGate kept their plugin ecosystems alive. WooCommerce now lists USDC, Solana, Bitcoin, and Ethereum on its official cryptocurrency page. Shopify accepts crypto through merchant apps and, on enterprise plans, through Shop Pay extensions.
This guide walks through the three integration paths, the fee math, and a decision flow for choosing settlement currency.
Path one: Shopify
Shopify does not run stablecoin checkout natively in the same way it runs card checkout. You add a payment provider from the Shopify App Store, configure the chains and assets you accept, and the provider handles the onchain side. The most common picks in 2026 are Coinbase Commerce, BitPay, CoinGate, and NOWPayments.
Setup is roughly:
Install the app from the Shopify App Store.
Connect a merchant account at the provider (KYB takes one to five business days for fiat settlement).
Choose chains and assets. Default picks are USDC on Ethereum, Base, Solana, and Polygon. USDT coverage varies by provider, and USDT-on-Tron support in particular differs app to app, so check the current docs before committing.
Pick settlement: keep stablecoin in your wallet, or auto-convert to fiat at payout.
Enable the gateway in Shopify Settings and run a test order.
Time to first live payment: half a day if KYB is fast, three to five business days otherwise.
Path two: WooCommerce
WooCommerce has a broader plugin ecosystem because WordPress is open and self-hosted. The official cryptocurrency page at woocommerce.com lists USDC, Solana, Bitcoin, and Ethereum, and recent audits from Crocoblock and Cloudways flag CoinGate, NOWPayments, CryptoPay, BitPay, and Triple-A as the active plugins in 2026. Most plugins now ship automatic fiat conversion at settlement, so a merchant never has to hold the volatile leg.
Setup is:
Install the plugin from the WordPress plugin directory or the vendor site.
Create the merchant account, complete KYB.
Configure chains and assets in the plugin settings.
Set fiat-conversion or hold-as-stablecoin under payout rules.
Run a test order against your sandbox keys, then flip live.
The catch: not every plugin maintains parity across chains. Confirm USDC-on-Base and USDC-on-Solana support before you commit, especially if your customer base skews mobile-wallet.
Path three: custom checkout
Custom is the route for teams that already have a checkout funnel and want stablecoin as one button next to Stripe and PayPal. Three options in 2026:
Stripe stablecoin subscriptions (docs.stripe.com/billing/subscriptions/stablecoins). Lives inside the Stripe Billing flow. Setup Intent, then recurring withdraw. USDC on Ethereum, Solana, Polygon, and Base.
Bridge orchestration API (apidocs.bridge.xyz). Single API to accept, hold, convert, and pay out. Used by marketplaces and platforms.
Daimo Pay (docs.daimo.com). Accept deposits from any wallet, any chain, any token; funds arrive as the stablecoin you want. Intent-based.
Setup runs one to ten engineer-days depending on whether you already have a payments service in your stack.
How do stablecoin fees compare to card processing?
Card fees in the US run 2.5% to 3.5% all-in for SMBs, plus chargeback risk that quietly costs another 0.5% to 1.5% in disputed volume and labor. International cards push higher.
Stablecoin processing in 2026 settles around 0.5% to 1.5% for plugin-based flows that include fiat conversion, and 0.1% to 0.5% if you accept stablecoin and hold it. Onchain gas adds cents on Base, Polygon, Arbitrum, Solana, and Tron. Ethereum mainnet still runs higher; most processors default merchants to L2s or Solana to keep that cost negligible.
The fee comparison that actually matters:
Path | Processing fee | Chargeback risk | Settlement | Time to live |
Card (Stripe / Shopify Payments) | 2.5% to 3.5% | Yes | T+2 | 1 day |
Plugin with fiat conversion (CoinGate, BitPay, NOWPayments) | 0.5% to 1.5% | No | T+1 to T+2 | 3 to 5 days |
Plugin stablecoin-only (hold as USDC) | 0.1% to 0.5% | No | Instant onchain | 3 to 5 days |
Stripe stablecoin (native) | 1.5% | No | Per Stripe payout schedule | 1 to 2 days |
Custom (Bridge or Daimo Pay) | 0.1% to 1.0% | No | Programmable | 1 to 10 eng-days |
Fee tiers above are directional. Provider pricing pages move quarterly, so confirm current rates before locking in a stack.
Settlement choice flow
The single biggest setup decision is settlement: where do the dollars land?
Do you have any onchain treasury operation? If no, route to fiat conversion at the gateway. Keep your operating account exactly where it is. The card-replacement use case stops here.
If yes, do you pay vendors or contractors in stablecoin? Hold the stablecoin in your wallet. Skip the on-ramp out, skip the off-ramp back in. This is the cleanest unit economics: no FX, no fiat conversion fee, no banking delay.
Mixed? Use a split rule at the gateway. Most processors let you keep N% in stablecoin and convert the rest. Bridge and BVNK both expose this through their orchestration APIs; plugin processors generally do not.
That single choice cascades into chain selection, wallet custody, accounting integration, and tax treatment. Make it deliberately, not by accident.
Chain selection rule of thumb
Customer side: optimize for what the customer already holds. US and Western Europe skew Base, Ethereum, and Solana. LATAM and Southeast Asia skew Tron USDT and Polygon. Africa skews Stellar (MoneyGram corridor) and Tron.
Merchant side: optimize for cheap, fast finality. Base, Polygon, Arbitrum, Solana, and Stellar all settle for cents and confirm within seconds. The merchant rarely needs Ethereum mainnet on the receive side.
The processors handle the cross-chain piece. If your customer pays in USDC on Solana and you want USDC on Base, Bridge or Eco Routes routes it. The merchant should not be doing this manually.
What does KYB look like in 2026?
KYB (know-your-business) is the gating step for fiat settlement. Plugin processors collect company registration, beneficial ownership over 25%, address verification, EIN or equivalent, and a bank account for fiat payouts. Turnaround is one to five business days for clean files; longer for high-risk verticals.
If you only want to accept and hold stablecoin without fiat conversion, KYB is sometimes lighter or unnecessary, because no fiat rail is being touched on the merchant side. Confirm with the provider; this varies.
Common SMB setup mistakes
Defaulting to Ethereum mainnet on the customer side. Gas friction kills conversion.
Skipping the test order. Plugin misconfigs are common; test small first.
Ignoring tax handling. Every stablecoin receipt is a taxable event in many jurisdictions if you hold; conversion at receipt simplifies.
Treating "stablecoin payments" as a single product. It is three: customer payment, settlement, and treasury.
Sources
WooCommerce official cryptocurrency page, woocommerce.com/cryptocurrency
Stripe stablecoin billing docs, docs.stripe.com/billing/subscriptions/stablecoins
Bridge API docs, apidocs.bridge.xyz
Daimo Pay docs, docs.daimo.com
Crocoblock and Cloudways 2026 plugin audits
Related reading
PLACEHOLDER-stablecoin-settlement-marketplaces-splits-holds-refunds
PLACEHOLDER-stablecoin-subscriptions-recurring-onchain-billing-patterns
PLACEHOLDER-stablecoin-off-ramp-providers-business-bridge-bvnk-moneygram-conduit