USDT on Tron and BNB Smart Chain
Get paid in USDT. No bank, no chargebacks.
Send your customer a payment link. They pay from any crypto wallet, the payment is irreversible the moment it confirms, and it settles to a wallet only you control. No card fees, and no developer needed.
- A flat 2%
- The same rate at every size.
- Final in minutes
- No chargebacks, ever.
- Your own wallet
- The contract pays nowhere else.
- No ID to start
- Only over 1,999 USDT a payment.
How it works
Try it — one payment, start to finish
You do not need a website, a developer, or any understanding of crypto. Press through it and see exactly what you would be doing — and how little of it there is.
Payments
Nothing outstanding. Create one for what you are owed.
You
Create a payment
In the dashboard, or from your own site with one API call. Type what you are owed and what it is for.
Got a developer? They can create payments automatically from your own site instead — skip to the technical part.
Why switch
Why businesses take stablecoin
USDT is pegged to the US dollar, so this is not a bet on a currency going up. It is a cheaper, faster way to be paid the same amount.
Nobody can claw it back.
A blockchain transfer cannot be reversed by the sender, their bank or a card network. No chargebacks, no chargeback fees, no disputes six weeks after you shipped.
You keep more of each sale.
Cards typically cost around 2.9% plus a fixed fee, before conversion margins and monthly charges. Here it is 2% and nothing else.
The payment is final in minutes.
No weekend delay and no rolling reserve held back against future disputes. It confirms, it cannot be reversed, and it reaches your wallet when the refund window you chose closes — immediately, if you chose none.
Your customers can be anywhere.
No merchant account, no correspondent bank, and no country quietly declined by a card processor. If they have a wallet, they can pay you.
Who it's for
Who this is for
Any business whose customers already hold stablecoin, or whose card fees have stopped making sense.
Online sellers and digital goods
Downloads, templates, courses, licences — the products card processors treat as high-risk and charge accordingly.
Subscription and SaaS businesses
Bill the same customer every month against a limit they approved once, with trials, usage-based charges and discount codes.
Freelancers and agencies
Send a client an invoice they can pay from anywhere, without either of you losing a percentage to an international transfer.
Cross-border and export
Where a wire takes days, costs a fixed fee at both ends, and the exchange rate is decided by someone else.
Getting started
Choose how you get paid. One of these needs nothing but a browser and somewhere to paste a link. The other two need a developer for an afternoon.
Not touching any code? Create a payment or a full invoice in the dashboard, copy the link, and send it however you already talk to your customer. Nothing to install.
Selling from your own site? Create the payment from your backend and redirect. You get a receiving address, an exact amount and a checkout URL back.
Billing the same customer monthly? They approve a spending limit once, on-chain. You charge up to it each period without asking again, and they can cancel without emailing you.
How it fits
Connect it to what you already run. You do not replace your invoicing, your storefront or your books — paygate sits beside them, takes the payment, and tells them it happened.
What you already run
The money never passes through an account of ours. It waits out your refund window on the escrow contract, then releases here — the only address it can go to.
Speed and settlement
Final in under a minute. A card payment is a promise for a week. This is a transfer that has already happened, into a wallet we could not reverse if we wanted to.
- 60s
- until the money cannot be taken back20 confirmations on Tron and 15 on BNB Smart Chain, at roughly three seconds each. Not authorised, not pending — final.
- 18
- attempts to tell your systems it landedSpread over just under two days, backing off as it goes. Anything still undelivered is parked in a queue you can replay rather than dropped.
- 0
- accounts of ours it passes throughThe payment rests in a contract whose only two exits are your payout address and a refund to your customer. Neither takes a destination, so there is no balance for us to hold, freeze or lose.
For your customer
They pay from whatever they already use
There is no account to create and nothing to download. If they hold USDT anywhere, they can pay you with it.
Any wallet, any exchange.
Trust Wallet, MetaMask, TronLink, Binance, OKX, an exchange withdrawal — they scan the QR or paste the address.
One click in a browser wallet.
If they have MetaMask or TronLink installed, the page fills the amount and the address for them. No copying anything.
Two networks.
USDT on Tron (TRC20) and BNB Smart Chain (BEP20) — the two with fees low enough that a small payment still makes sense.
Priced in your currency.
Show the amount in what your customer understands. They send the USDT equivalent at the current rate.
The page they land on, carrying your name and your support address.
Pricing
A flat 2%. No monthly fee, ever.
The same rate on every payment, whatever its size. There is no setup fee, no monthly charge and no minimum.
2%
per payment, at every size
$0
monthly, setup and minimum fees
0
held back in reserve, ever
Doing serious volume? Enterprise rates are negotiable.
Recurring
Bill the same customer every month
A blockchain has no direct debit, so recurring payments work differently here — and, once you see how, better.
Your customer approves a spending limit once. Each month you charge up to that limit and not a cent more. They can see the limit, and they can cancel it themselves without emailing you first.
Free trials, usage-based charges, discount codes, and automatic retries when a payment fails are all included. Prices are locked once created, so an existing subscriber is never quietly moved onto a new one.
FAQ
Questions merchants ask first
The short versions. There are more, with the long versions, on the FAQ page.
Do I need a developer to use paygate?
No. You can create a payment in the paygate dashboard, copy the checkout link, and send it to your customer by email, WhatsApp or any other channel — no code at all.
A developer is only needed if you want payments created automatically by your own website or app, which is what the API and webhooks are for.
How much does paygate cost?
Every payment is charged a flat 2%, the same rate at every size, with no monthly fee, setup fee or minimum.
Blockchain network fees are separate and are not ours — they go to the network and are typically a few cents. Merchants doing high volume can ask about Enterprise pricing.
Where does the money go? Do you hold my funds?
Your customer pays a deposit address belonging to that one payment. The money is swept into our escrow contract, held for your refund window, and then released to the payout wallet you registered. You choose that window — anything from none at all to 180 days.
It never reaches an account of ours, and that is a property of the contract rather than a policy we keep. There are exactly two ways out of it — release to your payout address, and refund to the payer who sent it — and neither takes a destination as a parameter. There is no address either function could be pointed at, by anyone, including us.
What the hold buys you is the refund window. Money already in your wallet can only be given back by you sending it; money on the contract can be returned to your customer from your dashboard while the window is open.
Can a customer charge back a USDT payment?
No. A blockchain transfer cannot be reversed by the sender, their bank, or a card network, so there is no chargeback process and no chargeback fees.
This is the main reason merchants selling digital goods, services or cross-border move to stablecoin payments — card chargeback rates and the fees attached to them disappear entirely.
It cuts both ways, and we would rather say so: if you want to refund a customer as a goodwill gesture, that is something you choose to do, not something a network forces on you.
How fast do I get paid?
The payment is confirmed and irreversible within minutes. When it reaches your own wallet is a separate moment, and it is the one you set. Those two are deliberately not the same thing.
The gap between them is your refund window: your customer's money sits in the escrow contract, where you can return it to them and nobody else can move it — not us, not them, not a bank. When it closes, the money is released to the wallet you registered, minus the fee.
You pick the length before your first live chain is enrolled. It can be nothing at all, in which case each payment is released to you in the same pass that collects it and nothing can be returned to a customer through the contract, or as much as 180 days.
There is no weekend delay and no rolling reserve held back against future disputes. A card payment also takes days to arrive, and then stays reversible for months afterwards; this one is final from the moment it confirms.
Is paygate live? Can I take real payments today?
Yes. You can open an account, take test payments while you build, and switch the same integration to live money when you are ready — the API and the checkout are identical in both modes.
What you should know before you build on us: we are new, we settle in USDT rather than your own currency, and we do not stand between you and your customer in a dispute. All of that is on this page rather than buried, because you would find it out anyway and it is better found now.
Straight answers
What we cannot do
Every payments company has a list like this. Most keep it in the terms. Ours is on the front page, because you will find out anyway and it is cheaper for both of us if that happens now.
You are paid in USDT, not in your own currency.
We can show prices in your currency, but what arrives is USDT. Converting it to cash is something you do at an exchange, not something we do for you.
We do not refund, on any setup.
You refund, from your dashboard, while the payment is still held — the contract accepts that instruction from the wallet you registered and not from ours. Once your refund window closes the money is in your own wallet and you send it back yourself. Either way the button is yours, and there is no version of this where we press it for you.
We do not settle disputes between you and your customer.
paygate is the mechanism, not the referee. If a payer says the goods never arrived, that is between the two of you — we hold no position, take no side, and have no power to move the money to either of you. What we give you is the window in which you can return it if you decide to.
A payment sent on the wrong network is usually gone.
True of every crypto processor, not just this one. The checkout page states the network clearly, which prevents nearly all of it, but nobody can recover the rest.
For developers
Reliable, unsurprising infrastructure. A REST API with the shape you already expect, and an OpenAPI document generated from the running deployment rather than written by hand beside it.
curl -X POST "$PAYGATE/v1/payments" \
-H "Authorization: Bearer sk_test_..." \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"amount_decimal":"25.00","reference":"order_1"}'- Idempotency on every write. A retry after a timeout cannot create a second payment.
- Signed webhooks, at least once. 18 attempts over just under two days, with a replayable dead-letter queue.
- A test mode that simulates a reorg. Rehearse the failures nobody can otherwise test.
- MCP for coding agents. Point Claude or Cursor at the deployment and it reads the real contract.
Take your first payment today
No card reader, no merchant account, no contract. Create a link and send it.