Why USDT only?
For cross-border payments USDT is credited fastest and settles with the most predictable finality. Fiat channels (bank cards, e-wallets, etc.) carry a completely different regulatory profile, and we don't operate them.
"USDT only" sounds like a preference, but it's really an engineering constraint problem: the platform has to move your money across borders into a platform balance, then use that balance to open cards and top them up. Which channel to use comes down to whether it can do three things at once — credit fast, be irreversible once credited, and cross borders in a way that's regulatorily above board. Measure every option against this yardstick, and stablecoin settlement is the only one that scores on all three.
The key isn't actually speed — it's finality. RDVCC runs a prepaid model: once your top-up is credited, the platform records the balance under your name using standard double-entry accounting, and it becomes immediately available to open cards and top them up. If the top-up channel itself can be reversed after the fact, you get an exposure where the money has already turned into card limit but the original top-up gets clawed back. Fiat third-party payment and bank-card channels generally come with cancellation / clawback windows, whereas on-chain stablecoins are irreversible after block confirmation — credited is settled, leaving no room for the funds chain to unwind. That is exactly the property a prepaid balance needs.
In cross-border prepaid scenarios, USDT wins on speed, finality, and compliance all at once
| Dimension | USDT stablecoin settlement | Fiat channels (Alipay / WeChat / bank card) |
|---|---|---|
| Crediting speed | Paid to your personal deposit address: usually 1–5 minutes on TRC20, 1–30 minutes on other networks (pending block confirmation) | Subject to clearing banks and business hours; slower still across borders |
| Crediting finality | Irreversible after on-chain confirmation; credited is settled | Cancellation / clawback windows are common |
| Cross-border capability | Inherently borderless; settles directly | Domestic fiat channels, not designed for topping up cross-border virtual cards |
| Conversion step | The payment processor converts the USDT to US dollars before settlement; your account is kept in US dollars | Requires fiat↔USD conversion, adding a layer of loss and routing |
| Regulatory profile | Matches cross-border settlement scenarios | A completely different regulatory profile for domestic payments; we don't operate them |
Pay in USDT, keep the account in US dollars, with money in and out through one payment processor
Choosing USDT isn't just about the entry point — it keeps the entire funds chain on one basis: the USDT you pay is received by a third-party payment processor (currently Gate Pay) and converted to US dollars, RDVCC settles and credits your account in US dollars only and keeps your balance in US dollars, and it does not receive or custody any crypto assets; when you take funds back you use Prepayment Refund (no closure) or Account Closure (full clearance), and either way the money goes back through the original payment processor to a USDT address you control (a flat $2 fee per payout, payment processor fee included). With money in and out through one payment processor and the account kept only in US dollars, every inflow and outflow reconciles in the ledger — this is also the prerequisite that makes daily automated reconciliation against the upstream, with alerts on any discrepancy, possible. The moment a reversible fiat channel is mixed in, it's like drilling a hole in this closed loop that requires manual conversion and reconciliation, and both speed and stability take a hit.