Accept USDT payments on your website

Suawave creates a USDT deposit address for your payout address and HTTPS callback URL. Your checkout shows the selected network, amount and address. Suawave forwards each eligible deposit and sends signed callbacks; your server verifies the confirmed payment before fulfilling the order. No registration, no account and no API key are needed.

Build the checkout

Choose a USDT payment network

Choose the network your buyer can send on and use a payout wallet that supports that same network. Keep the network beside the address throughout checkout. A token name alone is not enough to identify a payment route.

USDT minimums and per-deposit forwarding charges
API tickerMinimum depositFixed network chargeMinimum service fee
bep20/usdt1.00 USDT0.05 USDT0.05 USDT
trc20/usdt10.00 USDT1.00 USDT0.05 USDT

The service fee is calculated separately using the applicable percentage and minimum; the network charge is also deducted. Each eligible deposit is charged separately. Read the selected ticker’s info/create response before displaying payment instructions, and use the confirmed callback for the actual deducted and forwarded amounts.

Fees and minimums

The table lists USDT routes enabled in the public asset data. Check the ticker guide before offering another network or asset. Supported tickers and networks

Accept USDT TRC20 payments on TRON

For trc20/usdt, the QR payload contains the deposit address only. Even when a value is supplied, the buyer enters the amount in their wallet. Display the amount as text. Deposits must pass TRON solidification checks, then forwarding must confirm before the confirmed callback is sent. A block interval is not a checkout completion promise.

Accept USDT BEP20 payments on BNB Smart Chain

For bep20/usdt, a QR request with a value produces an EIP-681 token transfer request. Wallet support varies and the payer may change the amount. Match the selected token and network to the stored order. Suawave uses finalized chain evidence and confirms forwarding before sending the confirmed callback.

Connect the USDT payment API

  1. Create an address with your payout address and an encoded HTTPS callback containing an order reference and an unguessable nonce. Store address_in with the ticker and order. Repeating the same ticker and callback returns the existing deposit address.
  2. Show the buyer the selected network, deposit address, amount and minimum. Payments below the ticker minimum are not forwarded and produce no public callback or log entry.
  3. Verify x-ca-signature with the RSA public key from /pubkey/. For GET callbacks verify the exact full URL; for POST verify the raw body before parsing. Match the order reference, nonce, coin and deposit address.
  4. Record each event UUID durably. Fulfill only after pending is 0 and the confirmed amount meets your order policy. Acknowledge with HTTP 200 and *ok* after persisting the result. Repeated delivery must not fulfill the order twice.

Callback signature verification

Integration guides and payment details