Customers pay in stablecoins while you keep books in your own currency. Here is how to accept crypto, clear the FX exposure immediately, and avoid the situation where money has arrived but there is nowhere to move it.
networks accepted: Ethereum and TRON
currencies to credit after conversion
exchange accounts on the operator's side
Accepting crypto looks simple right up to the moment the first payment has to become money in the company account.
Time passes between payment and conversion, and all that time the rate is your loss or your gain. For a payments business that is someone else's risk with nothing to cover it.
Its own verification, its own limits, its own grounds for freezing funds. An operator whose settlement depends on an exchange account also depends on that exchange's decisions.
A blockchain payment arrives with no history. Without an address check you learn about the problem when your bank finds it — that is, too late.
Acceptance, conversion and address screening are three separate mechanisms, each with its own settings.
USDT, USDC and the networks' native coins. A payment is tracked by confirmation count, and it is credited by the operator's rules rather than the mere appearance of a transaction.
Incoming crypto is exchanged into your bookkeeping currency at the moment of payment, so the FX exposure closes at once. The swap terminal is configured like any terminal: provider, limits, fee.
The risk profile checks the sender address against sanctions and risk lists. You choose what happens on a hit: reject, hold for review, or accept with a flag.
The first question is where you hold the position. "Accept crypto and keep it" turns a payments business into a currency business: earnings depend on the rate rather than on volume. "Accept and convert immediately" leaves you the fee and removes the FX exposure — for an operator that is nearly always the right model. Everything else in the setup follows from that choice.
The second question is the network. TRON is cheaper in network fees and therefore convenient for frequent small payments; Ethereum costs more but is more familiar to corporate counterparties and better supported by wallets. You can enable both and let the payer choose — but then decide in advance who pays the network fee, or it will quietly come out of your margin.
The third question is regulatory. Accepting stablecoins does not exempt you from identification and monitoring duties: MiCA applies in the European Union, and the bank holding your settlement account will ask about the source of funds regardless of it. Address screening and a decision log for every payment are not over-caution — they are what you produce on the first request.
Three setup wizards. The operator goes through them alone — no development needed.
Networks and tokens, wallets, confirmation count for crediting, and how the payment is shown to the customer.
Exchange provider, currency pairs, deal limits, fee, and the wallet that pays network fees.
Address lists, trigger thresholds, and the action on a match: reject, hold, or accept with a flag.
Set up the swap terminal before switching acceptance on: otherwise the first payments arrive in crypto and wait for a manual conversion — exactly the FX exposure the whole exercise is meant to remove.
Register and set up acceptance and conversion yourself — on a test network first, then on mainnet. The swap terminal is created before acceptance goes live.
Get started