Stablecoin Payments for Business: Setup, Costs and Rules

A business can accept stablecoin payments in 2026 by turning on a processor feature such as Stripe’s crypto payment method, by using a dedicated crypto payment gateway, or by building its own wallet integration. Whether you should depends mostly on where you operate: the US and the EU now have stablecoin laws with clear dates, while Turkey has banned paying with crypto since 2021.

This guide is for owners and managers weighing the option for a real business, for example a software company selling licences to customers abroad or an online shop with an international audience. It covers the money flow, the setup choices, the cost drivers, the rules and the failure modes.

What does accepting stablecoin payments involve?

Accepting a stablecoin payment means a customer sends a dollar or euro token from their wallet, the blockchain records the transfer, and a processor matches it to your order and pays you out. The parts are the same no matter which provider you pick.

The customer holds a wallet, such as a browser extension or a mobile wallet app, with a stablecoin like USDC on a specific network. At checkout they connect that wallet or scan an address, approve the amount and sign the transaction. The network confirms it, usually within seconds to a few minutes depending on the chain.

Your processor watches the chain, sees the payment arrive, and marks the order as paid. It then either keeps the stablecoin for you or converts it to fiat and adds it to your balance, which later goes to your bank account.

With Stripe, for example, you enable the “Crypto” payment method and it works through Payment Links, Checkout, Elements or the Payment Intents API. Customers are sent to crypto.stripe.com to connect their wallet, and the funds settle in your Stripe balance in USD, according to Stripe’s documentation. The same page lists the United States under regional considerations, so availability outside the US is limited.

Reconciliation happens in three places. The on-chain transaction hash, the order or invoice in your system, and the fiat payout in your bank all need to line up. If the processor handles conversion, most of that matching sits in its dashboard and reports. If you build your own setup, your team or your software has to do it.

Processor, crypto gateway or your own integration: which setup fits?

Most businesses should start with a processor they already use, move to a crypto gateway only if they need networks or regions the processor does not cover, and build their own integration only when payments are central to the product. The table compares the three.

	Payment processor (e.g. Stripe crypto method)	Crypto payment gateway	Your own integration
Setup effort	Low: enable a payment method in an existing account	Medium: new account, onboarding, plugin or API work	High: wallet infrastructure, chain monitoring, conversion, reporting
Fees	Published processor fee per payment	Gateway fee, sometimes plus conversion spread	Network fees, exchange fees, plus your engineering and operations cost
Custody	Processor converts; you receive fiat	Varies: fiat payout or stablecoin held by the gateway or sent to your wallet	You hold the keys and carry the security risk
Supported networks	Limited list chosen by the processor	Usually wider	Whatever you build and maintain
Refunds	Handled through processor tools, rules vary	Varies by gateway	You design the whole process
Who handles compliance	Processor does screening and licensing; you still check your own obligations	Gateway, if it is licensed where you sell	Mostly you, with legal advice

A processor fits a company that wants to offer one more checkout option without touching crypto on its balance sheet. A gateway fits a business whose customers use networks or tokens the processor does not support, or which operates where the processor is not available. In the EU, check that any gateway appears on ESMA’s MiCA register before you sign.

Your own integration makes sense for products where on-chain payments are the core feature, such as a marketplace that pays out sellers in stablecoins or a platform with programmable payment logic. This is the kind of system we build in our blockchain development work, and the honest advice is that most merchants do not need it.

What drives the cost of stablecoin payments?

The cost of stablecoin payments comes from five things: the processor fee, the network, the conversion to fiat, the accounting work and the compliance checks. The processor fee is the visible part, but the others often decide whether the option pays off.

The processor fee is the easiest to compare. Stripe’s developer blog describes a 1.5% fee for stablecoin payments, with settlement as fiat in the Stripe balance, in its post on using Stripe stablecoin payments without crypto knowledge. Processors update prices and network lists, so confirm the figure on the current pricing page before you build a business case.

The network matters because each transfer pays a network fee. In most checkout flows the customer pays that fee, but if you send refunds or move funds between wallets yourself, you pay it. Fees on Ethereum mainnet tend to be higher than on Base, Polygon or Solana, and they move with network activity.

Conversion to fiat can add a spread or exchange fee, especially with gateways that let you choose when to convert. If you hold stablecoins instead of converting, you take on issuer risk and an accounting question about how to value them.

Accounting and reconciliation work is the cost people underestimate. Someone has to match transaction hashes to invoices, record payouts, and handle the cases that do not match, such as an underpayment or a payment that arrives after the checkout expired. Much of this is a good candidate for automation; our article on which business processes to automate first explains how to judge that.

Compliance checks include sanctions screening of sending addresses and, in some cases, identity checks on customers. A licensed processor does most of this for you. With your own integration, the cost of screening tools and legal review sits with you.

Which stablecoin and which network should you support?

Support the stablecoin and network your customers already hold, which for most dollar-priced merchants means USDC on one or two low-fee networks. Adding every token and chain increases support work without adding many buyers.

USDC, issued by Circle, is the most widely supported dollar stablecoin among mainstream processors. EURC is Circle’s euro-denominated token and is relevant if you price in euros and sell in the EU. Stripe supports USDC on Ethereum, Solana, Polygon and Base, according to the developer blog linked above. Third-party guides say Stripe has since added more networks and tokens for US merchants, so check its current docs rather than relying on any list, including this one.

The networks differ in practice:

• Ethereum mainnet is the most established, with the highest fees for customers.
• Base and Polygon run on or alongside Ethereum, use Ethereum-style wallets and addresses, and cost less per transfer.
• Solana is fast and cheap but uses its own wallet ecosystem, so customers with only Ethereum-style wallets cannot pay there directly.

A simple way to decide is to ask your customers. If you sell to developers or crypto-native companies, a short survey or a look at past payment requests often shows which network they use. Supporting that one network well beats supporting four badly.

What rules apply in the US, the EU and Turkey?

The US and the EU now regulate stablecoin issuers and service providers directly, while Turkey bans the use of crypto assets in payments altogether. Merchants are rarely the regulated party in the US and EU, but the rules decide which tokens and providers you can safely use.

United States: the GENIUS Act

The GENIUS Act became law on 18 July 2025 as the first federal framework for payment stablecoins, covering licensing, reserves, disclosure and compliance for issuers. It takes effect 18 months after enactment or 120 days after the final implementing rules, whichever comes first, as Debevoise & Plimpton summarise. Issuers must hold full reserves, publish regular reserve reports and may not pay yield to holders.

Implementing rules were still being finalised in late 2026, so details for service providers can still change. For a merchant, the practical point is to accept tokens from issuers that are positioned to be licensed, because US service providers will later be barred from offering unlicensed payment stablecoins to US persons.

European Union: MiCA

MiCA’s rules for stablecoins, which it calls asset-referenced tokens and e-money tokens, have applied since 30 June 2024, and the rest of the framework since 30 December 2024. A token pegged to a single fiat currency, such as USDC or EURC, is an e-money token, and only an e-money institution or credit institution may issue one. Holders can redeem at par, and neither issuers nor service providers may pay interest.

The transitional period for crypto-asset service providers ended on 1 July 2026, and unauthorised providers must stop serving EU clients. If you sell in the EU, confirm that your processor or gateway is authorised and listed on ESMA’s register.

Turkey: payments with crypto are banned

The TCMB regulation on not using crypto assets in payments took effect on 30 April 2021. Crypto assets may not be used directly or indirectly in payments, nobody may offer a service for that purpose, and banks, payment institutions and e-money institutions may not build business models around them. A company in Turkey cannot legally take stablecoin payments from its customers.

Separately, Law No. 7518 requires crypto asset service providers to obtain permission from the Capital Markets Board (SPK), with IT systems meeting criteria set by TÜBİTAK, as the SPK announcement explains. MASAK has also added withdrawal limits, waiting periods and transfer description rules for stablecoins on platforms. Turkish groups with entities abroad should treat any foreign stablecoin setup as a legal question first and a technical one second.

What can go wrong?

The main risks are funds sent on the wrong network, refunds without a chargeback system, issuer or regulatory changes, payments from sanctioned addresses, and unclear tax treatment. Each one is manageable if you plan for it before launch.

Wrong-network payments happen when a customer sends USDC on one chain to an address your provider only watches on another. Depending on the setup, those funds may be recoverable with effort or lost. Clear checkout instructions and a processor that only shows supported networks reduce this.

There are no chargebacks. That protects you from fraud disputes, but it also means you need a written refund policy: who requests it, which address receives it, which network, and whether you refund the token amount or the fiat value at the time of purchase.

Issuer and regulatory risk is real even for large tokens. A stablecoin can lose its peg briefly, or a provider can stop supporting a token in a region where it lacks authorisation. Converting to fiat on receipt limits your exposure.

Sanctioned addresses appear on government lists such as the US OFAC list. A licensed processor screens them; with your own integration you need a screening service and a procedure for frozen or blocked funds.

Tax and accounting treatment varies by country. Receiving, holding and converting stablecoins can each have consequences, so agree on an accounting policy with your accountant before the first payment, not after the first audit.

What to prepare before you start

Before you add stablecoins to checkout, confirm that customers want it, that the law allows it where you sell, and that your accounting can handle it. A short preparation list:

1. Customer demand. Count requests from buyers, check which tokens and networks they mention, and estimate volume, for example a handful of international B2B invoices a month.
2. Jurisdiction check. Ask a lawyer to confirm the rules for each country where you sell and where your company is registered. In Turkey, the answer for domestic payments is already no.
3. Provider check. Confirm regional availability, current fees and supported networks, and in the EU, MiCA authorisation.
4. Accounting policy. Decide whether you convert immediately or hold, how you record each payment, and how refunds are booked.
5. Test plan. Run test payments on each network you support, including an underpayment, a late payment and a refund.

If a processor’s standard feature covers your case, start there. If you need a custom flow, such as stablecoin payouts, multi-network support or reconciliation tied into your own systems, contact us with your target markets, expected volume and current payment stack, and we will tell you which setup fits and what it takes to build.