USDT on 11 networks, settled into one balance

Accept USDT without building eleven separate integrations

Paymos accepts USDT on 11 mainnet networks:

• Tron
• Ethereum
• BSC
• Polygon
• Arbitrum
• Optimism
• TON
• Avalanche
• Solana
• NEAR
• Plasma

A customer selects an enabled network at checkout and sends USDT from a compatible wallet. Paymos assigns a dedicated deterministic address to the invoice, monitors the selected network, applies the confirmation policy, and updates the payment status.

This page owns the product question: how Paymos accepts and settles USDT. For the asset itself, read what USDT is. For implementation choices, use the step-by-step guide to accepting USDT. To compare asset coverage and operating fit, see USDT vs USDC vs DAI.

One USDT balance across supported networks

Merchant balances are held per asset rather than per deposit network. USDT received on different supported networks contributes to the same USDT balance. When creating a withdrawal, the merchant chooses an available payout network for USDT.

Paymos settles in the same asset received from the payer:

• USDT remains USDT;
• there is no forced conversion to fiat, BTC, or ETH;
• there is no Paymos markup hidden in the rate;
• Paymos does not provide a bank-account off-ramp.

Withdrawals go to a merchant-controlled, whitelisted blockchain address. Availability, minimums, and network fees depend on the selected asset and payout network and are shown for that route.

Disclosed USDT processing costs

Plan	Processing fee
Standard	1.0% per settled invoice
Enterprise	0.3% on request

Nothing else is billed: no setup fee, no monthly platform fee, no monthly minimum, no reserve and no rolling reserve.

The payer's wallet pays the network fee required to send USDT. Paymos covers the network cost of accepting and consolidating the payment. Paymos takes no processing commission on withdrawal; a withdrawal can include a network fee paid in the withdrawal asset — quoted for that route before the withdrawal is confirmed, and subsidised, so the amount stays under what the chain itself charges to send it.

Network costs are variable. Paymos therefore does not promise one permanent gas amount for every USDT network or wallet. The gateway comparison framework explains how to separate a headline processing rate from the total effective cost of the complete payment path.

Integration options

Use the integration surface that fits the checkout you already operate:

• Hosted Checkout for a Paymos-hosted payment page.
• Embedded Checkout for an iframe inside your website.
• Payment Links for invoices shared without a custom checkout.
• Low-Code SDK for a browser integration with static, callback, DOM-source, or custom-button amounts.
• POS Terminal for browser-based in-person collection.
• Host-to-Host REST API for a server-controlled payment flow.
• Official CMS plugins for WooCommerce, WHMCS, OpenCart, PrestaShop, Magento 2, Shopware 6, CS-Cart, and Easy Digital Downloads.

Sandbox and Production use separate credentials with the same API surface. Merchant API authentication uses HMAC-SHA256; it is not Bearer-token authentication. Invoice creation uses the caller-supplied external_order_id, and reusing that identifier returns the existing invoice.

See the quick start for the complete request and signature flow.

USDT payment lifecycle

1. The merchant creates an invoice or opens a configured checkout flow.
2. The payer selects USDT and one of the networks enabled for the project.
3. Paymos allocates a dedicated invoice address and shows the final payment amount.
4. The payer sends USDT and pays the wallet's network fee.
5. Paymos detects the transfer and tracks confirmation.
6. After the applicable finality threshold, the invoice settles and the USDT balance is updated.
7. The merchant receives status changes through the API and authenticated webhooks.

Confirmation policy depends on both network and payment amount. Smaller payments can require fewer confirmations, while larger payments can require a stronger finality threshold. Timing also depends on current blockchain conditions, so there is no single fixed confirmation time for every USDT payment.

Webhooks designed for recovery

Webhook requests use the X-Webhook-Signature header with timestamped HMAC-SHA256 authentication. One delivery cycle has 11 total attempts: the initial attempt and ten retries. Delays increase from one minute to eight hours, producing a retry window of approximately 16 hours.

Failed events can be replayed manually. A merchant environment can configure up to ten webhook endpoints and subscribe each one to selected event categories. A single project list narrows the project-scoped categories — invoice and payment channel together, not one of them alone — while withdrawal events stay merchant-wide.

Read webhook authentication and verification before handling a paid event.

Withdrawal signing and destination controls

Outgoing Paymos transactions are signed on isolated infrastructure. Withdrawals can go only to destination addresses that were added to the merchant's whitelist.

USDT checkout experience

The payer does not create a Paymos account, provide an email, or complete KYC inside the checkout. The page is responsive and takes QR payment. On a phone the button opens Trust Wallet, MetaMask, Tonkeeper or Phantom with the payment already filled in — each of them only on the networks it can take — while the OKX button copies the address and opens the app. The checkout follows the customer's language, with English as the fallback.

Each project can configure its name and logo, one of four style presets, checkout colors, corner radius, success and failure return URLs, and an allowed browser origin.

Frequently asked questions

Which USDT networks does Paymos support?

Paymos accepts USDT on Tron, Ethereum, BSC, Polygon, Arbitrum, Optimism, TON, Avalanche, Solana, NEAR, and Plasma.

Does Paymos convert USDT before settlement?

No. USDT remains USDT in the merchant balance. Paymos does not force conversion to fiat, BTC, ETH, or another settlement asset.

How much does accepting USDT cost?

Standard processing is 1.0% per settled invoice. Enterprise processing is 0.3% on request. There is no setup fee, monthly platform fee, monthly minimum, reserve, or rolling reserve, and an invoice that goes unpaid, expires or is cancelled costs nothing. The payer's wallet pays its own send-network fee.

How long does a USDT payment take to confirm?

There is no universal fixed time. Confirmation policy depends on the network and payment amount, and observed timing depends on current blockchain conditions.

Can I start before submitting KYC or business documents?

A merchant can start without submitting KYC or business documents. The product has no KYC or KYB flow — no questionnaire, no document upload — and Production needs no manual activation.

Can a payer reverse a settled USDT payment?

A blockchain payment that has reached finality cannot be reversed through a card-scheme chargeback. A refund is a new outbound blockchain transaction initiated by the merchant, not a reversal of the original transfer.