When would an account get frozen?
Explicitly: fraud / cash-out schemes / illegal business, bulk registration to evade risk limits, or abnormal transaction patterns. A frozen account can still log in, view data and file tickets. We never confiscate user assets, but we reserve the right to terminate service for abuse.
When it comes to freezing, what users really want to know isn't how long the list is, but this: as someone who simply subscribes to AI normally and honestly opens virtual cards and tops them up, could I get frozen out of the blue one day? Reframe it and the answer is clear — freezing targets behavior patterns, not your identity, and not any single failed payment. Not one of the triggers listed below is something normal use would ever run into; every one of them is a deliberate abuse of the card BIN range.
First, tell apart two different things that both go by 'freeze,' so you don't knock on the wrong door. This article is about account freezing — the restricted state an account enters after it trips risk control. If what you're looking for is temporarily disabling a single card, that's the one-click 'Freeze / Unfreeze card' on the card details page: you can freeze and unfreeze it yourself at any time, all charges on the card are declined while it's frozen, and restoring it is entirely in your hands. It's a self-service feature and is a completely separate matter from account freezing.
The three kinds of behavior that trigger an account freeze all damage the reputation of the card BIN range
These red lines aren't a moral judgment — they're about negative externalities. A card BIN range is a resource shared by all users: it only takes one account using cards for cash-out schemes, money-muling, or as a payment channel for illegal business, and the merchant side may blacklist the entire BIN range, killing everyone's cards at once. So what risk control protects isn't the platform's face — it's the public asset that is the BIN range's reputation. This is the same logic behind the hard limit of at most 5 active cards at once and 10 cards cumulatively.
| Behavior type | What it looks like | Why it triggers a freeze |
|---|---|---|
| Fraud / cash-out / illegal business | Using cards for cash-out or money-muling, or providing a payment channel for illegal-business operations | Exposes the BIN range directly to high-risk merchants; the BIN's reputation collapses and drags down every user |
| Bulk registration to evade risk limits | Registering multiple accounts to get around the per-account limit of 5 active / 10 cumulative cards | What it evades is precisely the hard limit that protects the BIN, so risk concentrates and erupts within a single BIN range |
| Abnormal transaction patterns | Fund flows that clearly deviate from the normal purposes of subscriptions / opening cards / topping up cards | Deviating from the normal spending profile is usually a precursor to abuse |
Normal use almost never crosses these red lines
| Normal scenario | Why it doesn't trigger an account freeze |
|---|---|
| Frequently opening cards, closing them, and topping up repeatedly within the card limit | All of this is normal activity; as long as the purpose is genuine, it has nothing to do with freezing |
| Managing multiple cards under one account | The 5 active / 10 cumulative limit was designed for exactly this normal multi-card need |
| A few retries after a failed payment | This falls under payment failures; repeated failures on the same card push up the merchant-side risk score and may get the card temporarily blocked by the merchant — that's a merchant-side matter and is not the same thing as an account freeze |
Freezing, terminating service, and confiscation are three different things
Many platforms ban accounts at the slightest provocation and seize the money along with them, blurring these three things into one. We keep them separate — and that determines how much room you have left if you ever do get frozen.
| Concept | What it means | Does it actually happen |
|---|---|---|
| Account freeze | The account enters a restricted state but can still log in, view data, and file a support ticket to appeal | A protective measure when a red line is tripped; if a mistaken freeze is confirmed, it is lifted |
| Terminate service | For verified abuse, we reserve the right to stop providing service | Only for confirmed violations, never for normal users |
| Confiscate assets | Withholding user funds and keeping them as our own | We don't do this — no confiscation; after a mistaken freeze is reviewed and lifted, your balance can be used as usual to open cards and top up cards, or withdrawn back via the original USDT route through a support ticket |
Worried about a mistaken freeze? Run through this self-check first
- One person, one account: use a single account only; if you need multiple cards, open them within the same account's 5 active / 10 cumulative allowance, and don't register a second account to get around the limit.
- Use cards only for your own genuine spending (AI subscriptions / SaaS / ad spend, etc.); don't pay on behalf of others and don't route funds through your cards.
- When a payment fails, first check on the card details page whether the limit covers this charge including tax (subscriptions are usually estimated at $22, past-due back-charges at $25) and whether the balance credited by the platform is sufficient — don't fight merchant risk control with repeated retries.
- Keep your fund flow consistent with its purpose: deposit → open card → top up card → subscribe, with no fund shuffling unrelated to spending.