What do I need to accept stablecoin payments as a business?

At minimum: a wallet address (or a gateway that generates one for each transaction), a way to verify payment was received, and a plan for what happens to the stablecoin after receipt — hold it, convert to local currency, or use it in outbound payments. Most businesses use a payment gateway that handles address generation, payment detection, and settlement rather than managing a raw wallet.

Should I use a payment gateway or a direct wallet?

Gateways are the right choice for most merchants. They handle address generation per transaction (which prevents linking customer payments), payment detection, conversion to local currency if needed, and compliance screening. Direct wallet acceptance makes sense for B2B counterparties who already transact on-chain and where a persistent wallet address per customer relationship is acceptable.

How do I convert stablecoin revenue to local currency?

Through an off-ramp: an exchange (Kraken, OKX, Coinbase) or a specialist service (Bridge, Transak, Yellow Card) that converts stablecoin to fiat and sends it to your bank account. Settlement time ranges from minutes to one business day. Some gateways handle the off-ramp automatically, so funds land in your bank account in local currency as if you had processed a card payment.

How are stablecoin payments recorded in accounting?

Revenue is recognized at the USD fair market value of the stablecoin on the date received. For a 1:1 dollar-pegged stablecoin, this equals the token amount — no FX calculation needed. Under US GAAP (ASC 350-60), stablecoin holdings are measured at fair value with changes in net income. Holdings require disclosure. If you convert to fiat immediately, the accounting is identical to a dollar cash receipt.

Is there sales tax on stablecoin payments?

Sales tax applies to the taxable transaction (the sale of goods or services), not to the payment method. Accepting stablecoins does not change your sales tax obligations — you owe the same tax as if the customer paid by card or wire.

How to accept stablecoin payments as a business

Accepting stablecoin payments as a business is a four-part problem: receive the payment, verify it settled, decide what to do with the stablecoin, and record it correctly in the books. In 2026, each part has established tooling. The choice is whether to assemble the stack yourself or use a gateway that handles most of it in a single integration.

The two acceptance models

Gateway acceptance — a payment processor handles address generation, payment detection, and optionally off-ramp to fiat. The merchant experience resembles card acceptance: configure the integration, and payments land in your account with minimal blockchain exposure.

Direct wallet acceptance — the business publishes a wallet address (or generates one per invoice) and monitors it for incoming transactions. Works well for B2B relationships where the payer is already on-chain; less suitable for e-commerce or consumer-facing flows where address hygiene and UX matter.

Most businesses start with a gateway and graduate to direct treasury management as stablecoin volume grows.

Choosing a gateway

Gateway	Best fit	Key characteristics
Stripe	Businesses already on Stripe	Stablecoin settlement and treasury via Bridge acquisition; configuration change, no new integration; used by millions of businesses; Stripe co-incubated Tempo
BVNK	Enterprise B2B, $30B+ annual volume	Full stablecoin operations stack — on/off-ramp, treasury, compliance; listed in Mastercard's Crypto Partner Program
Coinbase Commerce	Smaller merchants, crypto-native customer base	Fast setup, broad chain support, converts to fiat automatically
Triple-A	E-commerce, Asia-Pacific reach	Checkout plugins for major platforms; automatic fiat settlement

Stripe is the natural path for any business already using Stripe for card processing. Its acquisition of Bridge in 2024 brought stablecoin issuance, orchestration, and treasury capabilities into the platform. Stripe is also a co-incubator and validator on Tempo, and uses Tempo as the rail for cross-border stablecoin settlement in 100+ countries. Adding stablecoin acceptance for a Stripe merchant is a configuration change, not a new vendor relationship.

BVNK targets larger operations that want to hold stablecoins on their balance sheet, manage on-chain treasury, and run compliance workflows directly. It serves the enterprise segment where Stripe's self-serve model has gaps.

Setting up a wallet for direct acceptance

For B2B flows where customers already transact on-chain, a business wallet is sufficient. Steps:

Choose a wallet type. For a business, a multisig smart account (Safe is standard) is appropriate — it requires multiple authorized signers for outbound transactions, providing an internal control that a single-key wallet cannot offer. Fireblocks and BitGo provide institutional custody if the balance warrants it.
Choose a network. Confirm which chain your counterparties use. If you need sub-cent fees and sub-second finality, Tempo is purpose-built for payment settlement. If you need to reach existing USDT liquidity, Tron and Ethereum are also options with their own cost profiles.
Generate the receiving address. For a persistent B2B relationship, a single wallet address per counterparty is acceptable. For e-commerce or invoice-by-invoice flows, generate a fresh address per payment to prevent customers from linking their payment history.
Monitor for incoming payments. Most wallets and block explorers provide webhooks or APIs for incoming transaction alerts. Goldsky, Alchemy, and QuickNode all provide Tempo event monitoring.

Off-ramps: converting stablecoin to local currency

Businesses that prefer to hold revenue in their bank account need an off-ramp. Options:

Exchange off-ramp: Send stablecoins to an exchange account (Kraken supports USDT0 and USDC.e natively on Tempo; OKX was Tempo's first international exchange partner). Sell for USD or local currency. Wire to bank account. Typical settlement: same day to next business day.

Specialist off-ramp service: Bridge (Stripe), Transak, Yellow Card (Africa focus), and Conduit Pay connect on-chain stablecoin balances to bank accounts in local currency. Most automate the sweep so the business never manually handles the stablecoin.

Hold on balance sheet: Businesses with high stablecoin payment volume increasingly hold a working stablecoin balance rather than converting each receipt. This eliminates round-trip conversion costs and positions idle balances to earn yield through lending protocols (Morpho is live on Tempo) or yield-bearing stablecoin products.

Compliance: what the business needs to handle

Accepting stablecoin payments does not make a business a money transmitter — you are receiving payment for goods or services. But two compliance obligations apply regardless:

Sanctions screening: Before accepting a payment from a new on-chain counterparty, screen their wallet address against OFAC, EU, and UN sanctions lists. Chainalysis Address Screening and Elliptic both cover Tempo with automatic TIP-20 token support. For gateways, this step is embedded.

AML transaction monitoring: Ongoing monitoring of inbound payment flows is best practice, and required in some jurisdictions for higher volumes. Again, gateways typically handle this; direct operators need to contract a monitoring service.

Accounting for stablecoin revenue

Revenue recognition follows the substance of the transaction. When a customer pays $500 USDC for a product:

Revenue: $500 (the fair market value of the stablecoin on the date received; for a 1:1-pegged stablecoin, this equals the token amount)
Asset: $500 increase in stablecoin holdings (measured at fair value under ASC 350-60)
Sales tax: Calculated on the $500 transaction value, same as a card payment

If you convert to fiat immediately, the stablecoin holding and the conversion cancel out, and the net entry is a cash receipt. If you hold the stablecoin, it sits on the balance sheet at $1.00 per token until converted or spent, with disclosure required under ASC 350-60.

For sales tax purposes, stablecoin payment is a payment method, not a different type of transaction. Your sales tax nexus analysis and rates do not change.

The settlement workflow end to end

A complete stablecoin acceptance workflow for an e-commerce merchant:

Customer selects "Pay with stablecoin" at checkout
Gateway generates a unique wallet address and QR code for the transaction amount in USDC/USDT
Customer sends payment from their wallet
Gateway detects confirmation (sub-second on Tempo; 15–30 seconds on Ethereum)
Order is marked paid; fulfillment is triggered
Gateway either holds the stablecoin in a merchant account, or auto-converts and sweeps to the bank account daily
Transaction record (hash, amount, timestamp, dollar value) is exported to the accounting system

The critical design decision is step 6. Businesses with predictable outbound stablecoin needs — paying suppliers, contractors, or cross-border partners — should hold rather than convert. Each conversion costs 0.1–0.5% in exchange spread; eliminating unnecessary round-trips compounds into material savings at volume.

The bottom line

Accepting stablecoin payments is a solvable problem today. For most merchants, Stripe is the path of least resistance. For high-volume B2B operations, BVNK is the enterprise-grade choice. For direct treasury management, a multisig wallet with Fireblocks or BitGo custody and Chainalysis monitoring is the standard institutional setup. The B2B guide covers the AR/AP automation layer; the Tempo field guide explains the payment rail that Stripe uses for cross-border settlement.