Crypto as a payment method
On the checkout a crypto payment looks like any other: the payer gets an address and an exact amount, sends from a wallet or an exchange, and the provider confirms when the network has enough confirmations. Payouts send assets to the recipient’s address the same way. The merchant creates the payment with the same request as a card payment and receives the same signed webhook; the only difference it sees is the action: show an address and an amount instead of a card form.
Through licensed or registered providers
Binance Pay, Coinbase Commerce, BitPay, NOWPayments, Cryptomus and others are adapters in the catalogue. Custody and conversion where the provider offers them, travel-rule checks and sanctions screening are theirs; Tranzify routes, cascades, journals and calls the webhook. The client signs with the provider, enters its account in the terminal settings and decides, by routing rules, where and for whom crypto appears. The platform never holds an asset and never generates an address of its own.
The flow
| Step | Pay-in | Payout |
|---|---|---|
| Create | The merchant creates a payment in fiat; the provider quotes the asset amount and an address | The merchant creates a payout with the recipient’s address and network |
| Pay | The payer sends the exact amount before the deadline | The provider sends from the client’s balance at the provider |
| Confirm | The provider waits for the network’s confirmations and reports | The provider reports the transaction hash and the status |
| Record | The journal keeps the quote, the address, the amount received and the hash; the ledger writes the fiat value | The journal keeps the request, the hash and the provider’s answer |
| Notify | A signed webhook to the merchant; the status on the payment | A signed webhook; the status on the payout |
Underpayments, overpayments and late transfers are reported by the provider with the amounts and handled by rules the client sets per provider; the operator sees every case with what arrived and when.
For whom
Exchanges and on/off-ramps that need local fiat methods in and stablecoins out, or the reverse; forex and iGaming businesses that settle with their payment partners in USDT; marketplaces paying sellers in regions where bank payouts are slow. In every case the licensed provider carries the regulatory obligations of the crypto side, and the client carries those of its own licence; the platform gives both one set of tools.
A typical setup
An exchange’s on-ramp takes local methods in and sends stablecoins out: PIX, UPI and bank transfers as pay-ins through the local providers of each country, USDT on TRC-20 as the payout through the licensed or registered crypto provider. Routing rules keep crypto off the checkout in the countries where the exchange’s licence does not cover it; a cascade sends a declined card to a bank transfer; limits per terminal keep the provider’s daily caps. The off-ramp is the reverse: USDT in through the provider’s address, a bank payout out, with the ledger holding the fiat value of every leg. Both directions share the journal, the trace and the reports the exchange’s accountants need.
What to check before enabling it
The client’s own licence and policy, the provider’s list of supported countries and assets, the merchants’ categories the provider accepts, and the accounting treatment of assets received: the ledger records fiat values at the provider’s quote, and the reports show the asset, the network and the hash for the client’s accountants.