Stablecoin Payments for Merchants: USDT vs USDC, Networks, Fees and Operations

Quick answer: Accept USDT and USDC on one or two low-fee networks your customers already use (commonly TRON, Solana or an Ethereum layer 2), price invoices in dollars, sweep funds to wallets you control, and keep per-payment records. The main risks aren't price swings. They're wrong-network deposits, issuer freezes and rare de-pegs, and each can be managed with policy.

Disclosure: Zitto publishes this guide and offers a crypto checkout. Competitor and issuer details link to primary sources and need checking on the date shown above.

Why stablecoins are the practical default

Bitcoin's volatility is a real problem for merchants: an invoice paid at $100 can be worth $95 by settlement. Stablecoins aim to hold a 1:1 value with the dollar, so a merchant can price, receive and account in dollar terms while keeping crypto's advantages: global reach, no chargebacks, and settlement in seconds or minutes.

Stablecoins are now one of the most used crypto assets for payments and transfers. For a merchant, that means many crypto-paying customers already hold them.

USDT vs USDC: what actually differs

Decision rule: if your customers are mostly in emerging markets or use exchange wallets on TRON, prioritise USDT on TRON. If they're US- or EU-based crypto users, add USDC on Solana or a layer 2. Check your analytics, or simply ask customers which they prefer.

Choosing networks

Each network a stablecoin runs on is effectively a separate payment rail. Supporting more networks reaches more customers but adds more ways for people to send on the wrong one.

Practical default: two networks. One "mass market" rail (often TRON for USDT) and one "low-fee modern" rail (Solana or a layer 2 for USDC). Add more only when customers ask for them.

Designing the invoice

Most stablecoin support tickets come from the invoice screen. A good one shows:

1. Token and network in large type: "USDT on TRON (TRC-20)", never just "USDT".
2. The exact amount, with a copy button, and a QR code that includes the amount where the wallet supports it.
3. A one-time deposit address per invoice, so payments match invoices automatically.
4. A validity window, e.g. 30 minutes. Prices are stable, but address monitoring should still expire.
5. Underpayment rule: e.g. accept within $0.50 or 0.5%, ask for a top-up beyond that.
6. A warning: "Sending on a different network may result in permanent loss."
7. Confirmation status that updates live.

The risks, and how to manage each

1. Wrong-network deposits

Customers send USDT on Ethereum to a TRON address, or the other way round. Sometimes funds can be recovered if you control the private keys on both chains, and sometimes they can't. Mitigation: network selection before showing the address, clear labelling, and a written recovery policy (with any fee).

2. Issuer freezes

Issuers can freeze tokens at addresses linked to sanctions or legal orders. Mitigation: screen incoming addresses against public sanctions lists where your obligations require it, sweep funds regularly, and spread holdings across issuers if your treasury is large.

3. De-peg events

Stablecoins have briefly traded below $1 during stress events. USDC fell well below its peg in March 2023 during the Silicon Valley Bank crisis before recovering. Mitigation: don't hold large balances in one stablecoin. Convert to your operating currency on a schedule, and define how to price invoices if a peg breaks (e.g. pause that token).

4. Counterparty and custody

If your gateway holds your balance, its solvency and freeze policies become your risk. Mitigation: prefer direct-to-wallet or automatic forwarding, and read the gateway's terms on holds.

5. Operational errors

Wrong payout address, lost keys, unclear refunds. Mitigation: multisig or hardware wallets for treasury, two-person approval for large transfers, written procedures.

Refunds in stablecoins

Crypto refunds can't happen automatically through a payment processor the way card refunds do. Set a policy:

• Refund the dollar amount, in the same token, on the same network, to an address the customer gives in writing
• Decide who pays the network fee (often the merchant for its own errors, the customer for change-of-mind refunds)
• Record the refund transaction hash against the original invoice
• Never refund to the address the payment came from without confirming it. Exchange deposit addresses may not accept incoming transfers back

Accounting and treasury

Stablecoin revenue still needs proper books:

Treasury pattern (illustrative): keep 1–2 weeks of operating expenses in stablecoins, convert the excess weekly through a regulated off-ramp if you need fiat, and keep a record of each conversion. Off-ramping to a bank usually involves identity verification at the off-ramp provider. That's separate from accepting payments.

Gateway comparison

Each competitor cell must cite the provider's own page with a capture date. Don't fill cells from memory.

Where stablecoin payments fit best

Recurring billing without "pull" payments

Card subscriptions charge customers automatically. Stablecoin wallets generally don't allow merchants to pull funds. Workable patterns:

1. Invoice + reminder: email a fresh invoice each cycle, with reminders at 3 days and on the due date.
2. Prepaid credit: customers top up a balance and you deduct usage, which suits usage-based products.
3. Annual plans: fewer payment events, and a discount gives customers a reason to pay up front.

Show the renewal date and the exact token and network on every invoice email.

Helping customers pay successfully

A short "How to pay with stablecoins" help page reduces support tickets. Include:

• Which tokens and networks you accept, with wallet and exchange examples
• How to withdraw from an exchange to the right network (screenshots help)
• What happens if they underpay or use the wrong network
• How long confirmation takes
• How to request a refund

Implementation checklist

• Choose 1–2 tokens and 1–2 networks from customer data
• Write underpayment, overpayment, wrong-network and refund policies
• Set up the gateway; turn on signed webhooks; fulfil only on confirmation
• Test each token and network with $1 invoices
• Set up sanctions screening if your obligations require it
• Set up treasury: hardware or multisig wallet, sweep schedule
• Set up accounting exports
• Publish a "Paying with stablecoins" help article
• Review fees and networks every quarter

Who this is not for

• Merchants who need card-style buyer protection for their customers
• Businesses whose regulators restrict crypto acceptance in their country or sector, so check first
• Anyone hoping stablecoins will hide revenue. Blockchain records are permanent and public

Bottom line

Stablecoins give merchants most of crypto's benefits without the price swings. Keep it simple: two tokens, two networks, clear invoices, regular sweeps and clean records. Compare gateways only on sourced, dated facts. Zitto's case, once verified, is checkout without merchant KYC that connects to the rest of its crypto-paid services.

FAQ

USDT or USDC? Both if you can. Otherwise, follow what your customers hold. Cheapest network? It depends on congestion. TRON, Solana and layer 2s are usually low-fee. Can payments be frozen? Yes, issuers can freeze addresses. Sweep and screen. Taxable? Revenue generally is. Ask an adviser.