Who got your money: the very different risks of on-site checkout, card-shop codes and on-chain top-ups
The question nobody asks
When choosing a relay site, people compare price, models and latency. Almost nobody asks: whose account does my money land in?
That question decides everything downstream, because the proof you can produce and the party you can complain to are both determined by the payment path.
Four common paths
| Path | Recipient | Proof you get | Reversible? |
|---|---|---|---|
| On-site checkout (Alipay, WeChat, Stripe) | the site’s own merchant account | order id plus platform statement | yes, the platform can intervene |
| Third-party card shop plus redeem code | the card platform, not the site | a code plus the shop’s order | almost never; the site says the code was sold |
| Manual transfer / corporate transfer | a personal or company account | bank statement | depends on the counterparty |
| On-chain USDT | a wallet address | transaction hash | irreversible |
On-site checkout: best case, but check the recipient
Checkout on the site’s own domain through a payment provider means the site holds merchant credentials, and the order id is traceable. If the amount looks wrong, you can escalate to the payment platform.
One thing to check: whether the recipient name matches the operator named in the terms. A different name is not automatically a problem (brands and operators often differ) but it needs an explanation.
Card shop plus redeem code: the transaction happens elsewhere
The most common and most overlooked pattern:
- The top-up button sends you to a different domain (the card platform)
- You pay there and receive a redeem code
- You return to the site, enter the code in the wallet page, and the balance appears
The legal relationship for that payment is between you and the card platform. The site only acknowledges what the code is worth.
Concrete consequences:
- Code not received, code invalid, balance not credited: the site says the shop sold it, the shop says it was delivered
- The site disappears: the card platform owes you nothing
- Terms usually state that sold codes are neither refundable nor exchangeable; that sentence exists for this path
We have seen sites with genuinely thorough terms that also state "we do not accept payment on this website" and "top-ups are non-refundable and non-withdrawable". Each sentence is defensible; read together, they tell you what you are buying.
Manual and corporate transfer
Suitable for business purchasing. Advantages: a bank record with a counterparty name. Disadvantages: manual, slow, and mismatches need human reconciliation.
Corporate transfer carries an implicit signal: having a corporate account implies a business licence, which is entity information in itself.
On-chain USDT
Advantages: cross-border, instant, no FX loss. Disadvantages:
- Irreversible: a wrong address is a loss
- No invoice, no statement, hard to book
- Volatility if a non-stablecoin is used
- For mainland teams, an extra compliance judgement
Five checks before paying
- Is the payment page on the site’s own domain? If it redirects elsewhere, check that domain’s registration first.
- What name does the recipient show? Does it match the operator in the terms?
- Is there an order or transaction number? Without one you cannot even prove you paid.
- What do the terms say about refunds? Three keywords: unused, window, fee.
- Can the balance be withdrawn? Most sites say no, and cannot be transferred. That is normal, but know it.
Three combinations, three risk levels
| Combination | Typical wording | Risk |
|---|---|---|
| On-site checkout + entity disclosed + 13-day refund | merchant account, company name, refund window | low |
| On-site checkout + no entity + explicitly non-refundable | personal recipient, "non-refundable once credited" | medium |
| Off-site card shop + no entity + codes non-refundable | redirect to a card shop, "codes are non-refundable" | high |
The second and third are not impossible to use, but keep the first top-up minimal and treat the money as spent rather than deposited.
One rule that covers most of it
Treat prepaid balance as money already gone.
- If you top up 100, assume it is spent and buy service with it
- Do not buy six months of usage to chase a bonus
- Top up monthly, enough for the month
This assumes the worst case, and the worst case does happen.
Takeaways
- The payment path determines what proof you hold when something breaks.
- With a card shop, your counterparty is the card platform, not the site.
- On-chain top-ups are irreversible and produce no invoice.
- Five checks: domain, recipient, order id, refund terms, withdrawability.
- Treat prepaid balance as spent; that alone avoids most losses.
Was this useful? If you have run into something the article does not cover, tell us and we will verify it and update the text.
Related articles
No contact channel is a risk: how far to verify a relay site before paying
Model retirement is not an accident: turning deprecation into a scheduled task
RPM, TPM and concurrency: the four real shapes of relay rate limiting, and how to find the true ceiling
Three traps in choosing a site from a leaderboard alone
Evening peak jitter: upstream, network path, or your own concurrency
Four ways to check a "direct official connection" or "pure resale" claim
Read on: a few of the services we list
This article does not point at a specific model family, so here are a few of the highest-scoring services we list, in case you want to read on. They are ordered by score and uptime and are not a recommendation.
See the full list in the directory, or browse by model family.