Ir al contenido
guide7 de noviembre de 2026 · 13 min read

Stablecoin payment gateway for PSPs: settlement, fees, compliance and build vs buy

How a PSP adds USDT and USDC acceptance for merchants: payment flows, confirmations, stablecoin settlement, fee stack, KYT, Travel Rule, build vs buy.

BitPolaris Engineering

English original

A stablecoin payment gateway lets a payment service provider, acquirer or EMI offer USDT and USDC acceptance to its merchants next to cards. The merchant creates an invoice, the buyer pays from a wallet or an exchange account, and the merchant balance is credited once the chain confirms. Behind that invoice, the PSP matches each payment to an order without a card number, collects it into a wallet it controls, screens it, settles it in stablecoin or fiat and reconciles it against the chain, on every network it accepts. Nothing reverses: there are no chargebacks, and no authorisation step stops a bad payment before it arrives.

This guide takes the PSP’s side of crypto payment processing for merchants, from flows and confirmations to fees, compliance and build versus buy. We build gateway software that runs in production for the reference exchange’s payments gateway; measured figures without another source come from that work. The engineering of a single payment is in how to build a USDT payment gateway.

What changes when a PSP adds stablecoins?

Card acquiring Stablecoin acceptance
Who moves the money The merchant pulls funds after an authorisation The buyer pushes tokens to an address
Reversal Chargebacks under scheme rules None; a refund is a new outgoing transfer
Settlement Scheme and bank cycles Minutes, at any hour, in tokens
Main cost Interchange and scheme fees, mostly a percentage Network fees, a fixed amount per transfer
Risk check Card, issuer, 3-D Secure The paying address and its history
What you hold A receivable from the scheme Tokens on several chains in wallets you control

Two rows decide the project: cost is charged per transfer, not per dollar, so small tickets are expensive on some chains; and risk moves from chargebacks to tainted funds and issuer freezes.

On 7 November 2026 DefiLlama counted $176.8 billion of USDT, 52.1% on TRON and 38.2% on Ethereum, and $70.6 billion of USDC, 60.6% on Ethereum and 10.0% on Solana. USDT on TRON and Ethereum plus USDC on Ethereum covers most of the supply, so a USDT payment gateway for PSPs usually starts there; add chains when merchants ask.

How does the gateway tell payments apart?

A token transfer carries a sender, a recipient, a token and an amount. On TRON and Ethereum there is no memo that wallets fill in, so the gateway has to identify the payment another way:

Method How a payment is matched Cost and risk for the PSP
Address per invoice A fresh address for every invoice Cleanest matching; every address must be swept, and on TRON activated first
Address per customer Each buyer keeps one address Fewer activations; only one open invoice per address at a time
Shared address plus tag A destination tag per payment Only where the chain has tags, such as the XRP Ledger; set the account to require one
Shared address plus unique amount 100.0137 USDT instead of 100.00 No sweeps; breaks when an exchange deducts its withdrawal fee from the amount

For a PSP this is mostly a cost decision, quantified below: per-invoice addresses multiply collection transfers; unique amounts avoid them but send short payments to manual review. Either way, one address never serves two open invoices, and expired addresses stay watched, because exchange withdrawals arrive late.

How many confirmations per chain?

Send the merchant a payment.detected event as soon as the transfer appears, so the checkout can say “received, confirming”, and credit the balance only on payment.confirmed.

Chain Finality rule Practice
TRON A block is solidified once at least 70% of the 27 super representatives, 19 of them, have confirmed it We credit after 30 blocks, about 90 seconds
Ethereum Finality takes about 15 minutes and can stall A configured depth for small amounts, the finalized block for large ones
BNB Chain Fast finality; 0.45-second blocks since the Fermi hard fork of 14 January 2026 Use the chain’s finality signal; BNB Chain asks teams to review fixed timing assumptions
Solana “Finalized” means at least 31 further confirmed blocks, about 13 seconds in Helius’s measurement Credit on finalized; “confirmed” still carries a small rollback risk

Crediting below finality is only safe if your ledger can reverse a merchant credit after a reorganisation. Make the depth a per-network setting, not a constant in code.

Settlement: stablecoin, conversion or fiat

A PSP can offer merchants three settlement options:

Settlement How it works Who carries what
Keep stablecoin The merchant balance is credited in USDT or USDC and paid out to an approved address Merchant: wallet and accounting. PSP: payout fees and a float on each payout chain
Auto-convert TRX, ETH or BTC payments are converted to a stablecoin on arrival at a quoted rate PSP: venue fee and spread; the regular-tier spot fee at Binance is 0.1%
Fiat The PSP sells stablecoins through an OTC desk, an exchange or the issuer and pays merchants by bank transfer PSP: spread, bank fees, a banking or EMI partner and the timing gap

Fiat is the hard part. One workable pattern is to pay merchants from your own fiat float on a schedule and convert stablecoins in batches. Issuer routes have thresholds: Tether’s direct redemption has a $100,000 minimum and a fee of the greater of $1,000 or 0.1%, plus a USD 150 verification fee; Circle Mint redeems USDC 1:1 for vetted institutional customers and lists no fees on its public page. Below that, OTC desks and exchanges quote a spread you negotiate.

Chains add a second question: a merchant paid on TRON who wants payouts on Ethereum needs USDT you already hold on Ethereum. Keep a float per chain and price the rebalancing into your fees.

The fee stack, with numbers

The PSP’s cost per payment has five lines: collection, payout, conversion, screening and infrastructure. The first two are fixed amounts per transfer, so ticket size matters more than any percentage.

Line Figure Source
TRON, collect the first payment on a new address 7.53 TRX (6.43 transfer plus 1.1 activation), about $2.41 Our measurements, 16 October 2026; TRX at $0.3199 on 7 November 2026
TRON, collect a later payment on the same address 6.43 TRX, about $2.06 Same
TRON, pay out to an address holding no USDT 13.03 TRX, about $4.17 Same
TRON, rented energy, new address 3.0–4.1 TRX (1.9–3 rented plus 1.1 activation), about $0.96–1.31 Quotes we collected in October 2026, not receipts
Ethereum, gas top-up plus sweep (about 86,000 gas) Under one cent at about 0.04 gwei; about $3.83 at 20 gwei eth_gasPrice from a public node and ETH at $2,224, 7 November 2026
Conversion on an exchange 0.1% spot fee at the regular tier, plus the spread Binance fee page, read 7 November 2026
USDT redemption at the issuer Greater of $1,000 or 0.1%, $100,000 minimum Tether fee page, read 7 November 2026
Address screening Priced on request by the large analytics vendors Ask for quotes early

TronGrid still showed 100 sun per energy unit on 7 November 2026, the rate behind our measurements. The collection line alone, as a share of the payment (assumption: one collection transfer per payment, 7 November prices):

Average payment TRON, energy burned, new address TRON, rented energy Ethereum at 0.04 gwei Ethereum at 20 gwei
$20 12.0% 4.8–6.6% 0.04% 19.2%
$100 2.4% 1.0–1.3% under 0.01% 3.8%
$500 0.48% 0.19–0.26% under 0.01% 0.77%
$2,000 0.12% 0.05–0.07% under 0.01% 0.19%

The levers are a fixed component in the merchant fee (BitPay publishes 25¢ on top of its percentage), a minimum payment per network, routing small tickets to cheaper networks, and on TRON rented energy plus a 1 USDT reserve in the receiving hot wallet; receipts are in how to cut TRON energy costs.

Compliance: KYB, KYT, the Travel Rule and which tokens

This section is a technical reading of the rules, not legal advice; counsel should confirm.

Merchants (KYB). Add the crypto questions to merchant onboarding: prohibited categories, expected volume per network, settlement preference, and payout addresses verified before first use.

Payers (KYT). Screen the sending address and transaction before you credit or sweep. OFAC says its crypto address listings are “not likely to be exhaustive”, so add a blockchain analytics provider. A hit stays on its deposit address, unswept and uncredited, and compliance decides any refund.

Travel Rule. Regulation (EU) 2023/1113 has applied since 30 December 2024 wherever either provider is in the EU, with no minimum amount. As the beneficiary’s provider, a PSP needs procedures to detect missing originator and beneficiary information (Article 16(1)) and to execute, reject, return or suspend such transfers on a risk basis (Article 17). For a payment from a self-hosted wallet, Article 16(2) requires you to obtain and hold that information and, above EUR 1,000, to assess whether the beneficiary owns or controls the address. In a merchant payment the wallet is the buyer’s. That is not automatically prohibited, but your risk policy must say what happens next and your checkout must collect the payer data it requires. Payments from exchanges should arrive with Travel Rule data, so be reachable and handle counterparties that are not (when the counterparty cannot receive the message). Outside the EU, FATF’s standards allow a USD/EUR 1,000 threshold.

Licences and tokens in the EU. Holding or transferring stablecoins for merchants generally falls under MiCA. In June 2025 the EBA also advised supervisors to require PSD2 authorisation for the custody and transfer of e-money tokens such as USDC, after a transition that ended on 2 March 2026. ESMA told providers to restrict services in stablecoins that are not MiCA-compliant by the end of March 2025. It named no token; in January 2025 Cointelegraph quoted a MiCA Crypto Alliance member saying Tether had no MiCA licence, so check USDT’s current status with counsel.

Frozen tokens: a risk card acquirers do not have

Tether’s terms, last updated on 26 February 2026, allow it to freeze tokens and blacklist addresses that hold USDT; Circle’s USDC terms, last updated on 15 October 2026, reserve the right to block USDC addresses. According to BlockSec, Tether blacklisted 4,163 addresses holding $1.26 billion in 2025, 3,506 of them on TRON, and removed only 150 of them within the year. A blacklisted address can no longer send USDT, so everything at that address stops moving, not only the tainted amount.

Receiving tainted funds does not blacklist your wallet automatically, but it brings a law-enforcement request closer to the hot wallet that pays every merchant. Controls:

  • Screen before you sweep, and keep flagged deposits on their own address.
  • Keep the hot wallet small, and split collection wallets by risk tier or merchant group so one freeze does not stop every payout.
  • Book frozen balances to their own ledger account, and write into merchant terms who bears a freeze.
  • Accept more than one issuer’s token, so a single issuer action does not stop the rail.

One gateway, many merchants

Each merchant needs balances per asset in a double-entry ledger, with your fees and network costs on your own accounts and “credited” and “swept” as separate states. Then the wallet layout:

Pooled hot wallet, ledger per merchant Wallets per merchant
Sweep and payout cost Lowest One float and fee reserve per merchant
Freeze blast radius Every merchant in the pool One merchant
Reconciliation The ledger must prove each merchant’s share every day The wallet balance is the merchant’s share
Fits Many small merchants Large merchants, or rules that require segregation

Add fee tiers, limits and a settlement preference per merchant, scoped API keys, team roles, and payouts only to pre-approved addresses with two-factor confirmation. If merchants are marketplaces themselves, decide early whether their sellers become accounts in your ledger, and scope it with any vendor, us included.

Reconciliation runs in four layers. The frequencies are our recommendation:

Layer Compares How often
Chain to wallets On-chain balances of every deposit, hot and treasury address against your wallet records Continuously, with a daily sign-off
Wallets to ledger Holdings against merchant balances, fee income, pending transfers, fee reserves and frozen funds Daily
Ledger to merchants Invoices, fees and payouts per merchant against statements Each statement
Fiat to bank OTC or exchange fills and bank statements against fiat payouts Each settlement run

Merchant reports need one line per payment: invoice and order ID, price currency and amount, rate, network, amount received, transaction hash, confirmation time, fee, net credited and payout reference. The hash lets the merchant’s auditor check the chain directly.

Uptime: scanners, RPC providers and the fee wallet

A card outage shows up as declines; a crypto outage shows up as payments that arrived and that nobody credited. Three failures from our own production:

  • Scanners stop quietly. A restart bug once stopped our TRON detection for 17.5 hours. Alert per chain on the scan position against the chain tip, and backfill after every outage.
  • RPC providers can be wrong. One of ours answered “rate limited” inside an HTTP 200, so failover never triggered. Run two providers per chain and check large payments against a second source (blockchain RPC failover).
  • The fee wallet runs dry. Payments are then credited but never collected; the alert thresholds are in why USDT deposits get stuck.

Retry merchant webhooks with backoff (we retry for 24 hours) and show per-network delays on a status page.

Refunds, underpayments and overpayments

Set the policy per merchant and let the gateway enforce it:

Case Usual cause What the gateway should do
Underpayment The buyer’s exchange deducted its withdrawal fee Send the buyer a top-up link and the merchant a partial-payment event, or accept within a set tolerance
Overpayment The buyer rounded up or paid twice Credit in full and flag; refund on request
Late payment Exchange withdrawal queues Credit stablecoin-priced invoices; re-quote fiat-priced ones
Wrong token or network USDC sent to a USDT invoice, BEP-20 sent to an ERC-20 address Watch both contracts; publish a recovery fee
Refund The merchant’s decision A new payout to a screened address the buyer provides, with the same approvals as any payout

Never refund to the sending address: for a payment from an exchange, that is the exchange’s hot wallet.

Build, license or resell a hosted processor?

Build in-house License gateway software Hosted processor
Upfront 30–50 engineer-months, our estimate BitPolaris Payments: €2,100 setup on our cloud, €7,700 self-hosted, €20,300 source Usually none
Ongoing Team, hosting, RPC, chain fees €410 a month on cloud, or 20% of the licence a year self-hosted; plus chain fees, RPC and screening A percentage per payment, sometimes plus network fees
Merchant pricing Yours Yours The processor’s fee plus your margin
Funds and licence Yours Yours Depends on the processor’s model; confirm whose licence covers your merchants
Time to first payment Months Weeks Days

Published processor fees, read on 7 November 2026:

  • BitPay: 2% plus 25¢ below $500,000 a month, 1.5% plus 25¢ up to $999,999, 1% plus 25¢ from $1 million; higher for high-risk industries; daily fiat settlement advertised.
  • NOWPayments: its help centre lists 1% for payments without exchange and 1.5% for multi-currency, fixed-rate and “fee paid by user” payments; network fees are separate.
  • CoinGate: 1% per payment; crypto payouts €0.50 plus 0.5%, or €0.50 plus 1.5% with conversion; refunds €0.25 plus 0.1%; weekly settlement on the standard plan. Its PSP page describes a branded checkout on the PSP’s own domain and virtual ledgers for sub-accounts.
  • Coinbase Payment Acceptance: for PSPs, marketplaces and large platforms; USDC or USDT on Ethereum, Base, Arbitrum, Optimism and Polygon; settlement by Fedwire, SWIFT or USDC; about a month of enhanced due diligence; no fees published.
  • CoinsPaid: we found no published fee schedule on its website.

At $1 million a month in 10,000 payments, a 1% processor costs $10,000 a month and BitPay’s top tier $12,500. A typical PSP configuration at our list prices (Payments on cloud with KYB and risk, auto-convert, shop plugins and two extra chains) is about €6,160 one-time and €640 a month. Chain costs apply under every model: at a $100 average on TRON, collection alone is roughly $9,600 to $24,100 a month, so ask each processor how it charges network fees. Our view: without the permissions to hold stablecoins for merchants, or below a few hundred thousand dollars a month, resell a processor; if payments are your product and you will hold the licence anyway, own the gateway.

BitPolaris Payments fills the software-licence column: hosted checkout, a REST API with HMAC-signed webhooks, SDKs, a merchant panel with payouts only to pre-approved addresses, and an operator console for fee tiers, chain watchers and reconciliation. USDT on TRON and Ethereum, USDC on Ethereum, TRX and ETH are included; extra chains are €980 each, and KYB and risk with address screening is €130 a month on cloud or €2,500 self-hosted. You run it under your own licence and set merchant fees; see the payment companies page for a typical configuration.

Stablecoin payment gateway FAQ

What is a stablecoin payment gateway for PSPs?

Software that lets a PSP accept USDT and USDC for its merchants: checkout, deposit addresses, chain scanning, confirmations, a merchant ledger, signed webhooks, settlement, payouts and reconciliation. The PSP sets merchant fees and runs compliance; merchants integrate once.

How does stablecoin settlement work for merchants?

The merchant balance is credited in USDT or USDC at the confirmation depth you set, about 90 seconds on TRON at 30 blocks. The merchant withdraws the stablecoin to an approved address, or takes fiat, which the PSP funds through an OTC desk, an exchange or the issuer.

What does crypto payment processing for merchants cost a PSP?

Network fees, conversion spreads, screening, hosting and RPC, plus the software or processor fee. Collecting one TRON payment cost 6.43 to 7.53 TRX in our measurements, about $2.06 to $2.41 on 7 November 2026, against under one cent on Ethereum. Hosted processors published 1% to 2% plus 25¢.

Does the Travel Rule apply to merchant stablecoin payments?

In the EU, yes, where the PSP is the beneficiary’s crypto-asset service provider: Regulation (EU) 2023/1113 sets no minimum amount, and payments above EUR 1,000 from self-hosted wallets need an assessment of who owns or controls the address. Elsewhere local law decides, often from a USD/EUR 1,000 threshold. This is a technical reading, not legal advice; counsel should confirm.

Can Tether or Circle freeze a PSP’s stablecoins?

Yes. Both issuers’ terms allow them to block addresses, and a blacklisted USDT address can no longer send the token. Screen before sweeping, keep the hot wallet small and split collection wallets.

BitPolaris Payments is gateway software for PSPs: hosted checkout, signed webhooks, a merchant panel and an operator console with fee tiers, chain watchers and reconciliation, on our cloud, on your servers or as source code. Prices are public.

See Payments · Build an estimate

Sources

  1. DefiLlama, stablecoins: USDT and USDC supply by chain from the stablecoins API, read 7 November 2026
  2. TRON, DPoS and block solidification; TronGrid, chain parameters (energy fee 100 sun), read 7 November 2026
  3. ethereum.org, time to finality
  4. BNB Chain, Fermi hard fork accelerates BSC to 0.45-second block times
  5. Helius, Solana commitment levels
  6. XRP Ledger, source and destination tags
  7. CoinGecko, TRX and ETH prices, read 7 November 2026
  8. Binance, spot trading fees, read 7 November 2026
  9. Tether, fees and terms of service (last updated 26 February 2026), read 7 November 2026
  10. Circle, Circle Mint and USDC terms (last updated 15 October 2026), read 7 November 2026
  11. BlockSec, USDT blacklisting on Ethereum and TRON in 2025
  12. OFAC, FAQ 562
  13. Regulation (EU) 2023/1113, Articles 16 and 17
  14. FATF, The FATF Recommendations, Interpretive Note to Recommendation 15
  15. EBA, no-action letter on the interplay between PSD2 and MiCA (10 June 2025)
  16. ESMA, guidance on non-MiCA-compliant ARTs and EMTs (17 January 2025) and Cointelegraph on the statement (20 January 2025)
  17. Processor pricing, read 7 November 2026: BitPay, NOWPayments fees, CoinGate pricing and CoinGate for PSPs, Coinbase Payment Acceptance
  18. BitPolaris, pricing and Payments, list prices as of 7 November 2026; How to cut TRON energy costs (measurements of 16 October 2026)

BitPay, NOWPayments, CoinGate, Coinbase, CoinsPaid, Tether and Circle are trademarks of their owners; this article describes their public documentation and pricing and implies no affiliation.

Reserve una llamada de alcance de 30 min

Crypto exchange, payments, wallet, custody and token launch software, already running in production. Run it on your own servers, license the source code, or let us host it under your brand.