Limits are easier to plan around than to argue with, and most people meet one at the worst possible moment: with a voucher already bought. The mechanics are not complicated and they are not arbitrary. Known in advance, a ceiling turns a refusal into a scheduling decision.
What a limit is actually holding back
Three different pressures produce ceilings, and they pull in the same direction for unrelated reasons.
The rules attach to amounts. Anti-money-laundering law is threshold-driven. Above certain sums a business must do more: fuller due diligence, documented evidence of where the money came from, in some cases formal reporting to a financial intelligence unit. A business sets its own ceilings well inside the legal ones, so that ordinary transactions never approach a threshold and unusual ones get looked at before they cross one. See why prepaid vouchers attract anti-money-laundering rules.
Loss is one-directional. A voucher exchange pays out in instruments that do not come back. Crypto sent on-chain cannot be recalled. A bank transfer is difficult to unwind once credited. Meanwhile the thing received — a voucher code — can turn out to be worth nothing well after it verified cleanly, because a voucher bought with a stolen card is liable to be blocked by the issuer long afterwards, when the cardholder notices the charge. The ceiling is the size of the mistake the business is prepared to make in a single transaction.
Manual work has a capacity. Settlement here is not automated. A person contacts the issuer for each voucher, and issuers' support lines have opening hours and queues. A ceiling is partly an honest statement about how much can be handled properly in a day.
The shapes a limit takes
Any given transaction is measured against several ceilings at once, and the lowest one applies.
- Per transaction. A maximum, and also a minimum.
- Per day. Blunt, and mostly there to slow down an account behaving unusually.
- Per rolling period. The total across a window of days or months. This is the ceiling that matters most and the one people misunderstand.
- Cumulative, pending review. A total after which nothing more proceeds until documents are supplied, regardless of how long it took to get there.
- Per voucher brand. Issuers impose their own caps on what a single voucher can hold, and vouchers are sold in fixed denominations. A large amount necessarily arrives as several tickets, which is normal and is not itself splitting.
- Per settlement method. Rails differ. On-chain transfers carry a network fee that makes small payouts uneconomic; bank transfers have their own minimums and cut-off times; PayPal has its own rules.
No KYC documents are required at any amount. A full name and a country of residence is all we ask for, and the declared name is screened against sanctions and politically-exposed-persons lists, because screening has no lower bound. See why no KYC is required here.
Cumulative measurement
A per-transaction ceiling on its own would be theatre. Anyone who wanted to exceed it would submit two transactions. So limits are not measured against transactions. They are measured against a person, across a window of time, and every transaction that person has made in that window counts towards the total.
The difference between window types is worth knowing. A calendar window resets everyone on the same date — the first of the month, the first of January. A rolling window never resets. Each transaction ages out of the total exactly one period after it happened, so headroom returns gradually rather than all at once. A rolling window is the harder of the two to work around, because it offers no predictable reset date to aim at.
The total also follows the person rather than the login. One human being can be recognised across several attempts by the document number on their identification, by name and date of birth, by address, by the bank account or wallet address receiving payment, and by the device and connection used. Holding more than one account is a breach of the terms in its own right, and where accounts are linked, the totals are added together rather than kept apart.
Structuring, and why it does not work
Breaking one amount into several to stay under a threshold has a name. It is called structuring, or smurfing, and in many jurisdictions it is an offence in itself, separate from whatever the underlying money was. The intent to avoid the threshold is the thing prohibited. Money that was entirely clean before it was split does not stay uncomplicated afterwards.
Set the law aside for a moment, because there is a more immediate problem. Several transactions a little below a ceiling, close together, from one person or from a group of people who resemble one another, is among the most recognisable patterns in transaction monitoring. It is what monitoring was built to find. Attempting it does not reduce scrutiny; it is the thing that summons scrutiny.
The uncomfortable part is that most splitting is not criminal at all. Someone with a genuinely large amount often breaks it up out of a vague sense that smaller is less trouble, or embarrassment about the size, or a wish not to be asked questions. The instinct is understandable and it makes everything worse.
If you hold more than the ceiling, say so before you start. The trouble with splitting is not that it might be noticed. It is that it is indistinguishable from the thing the rules exist to catch, and it cannot be undone once the pattern is on the file.
Declared up front, a large amount is one case, reviewed once, with documents requested once. Split quietly, it becomes several cases, each one more suspicious than the last.
Why there is a floor as well as a ceiling
Minimums surprise people more than maximums. They exist because most of the cost of a transaction does not scale with its size. Verifying a small voucher with its issuer takes a person the same telephone call as a large one. A blockchain transfer costs the same fee whether it carries a little or a lot. Below a certain face value, a 5% commission does not cover the work involved, and pretending otherwise would mean either doing the checks badly or charging everyone else for it. The published rates show where that floor sits.
How a ceiling moves
Limits are not negotiated at the counter and cannot be bought. They move on evidence.
Upwards, on documented source of funds — a receipt for the voucher purchase, a bank statement showing the cash withdrawal, a payslip, a contract — and on an ordinary settled history that makes the next transaction unremarkable.
Downwards, too. A sharp change in pattern, a screening alert, a voucher that fails verification, or a payout destination that does not match the account holder will all reduce headroom while the file is looked at.
When you reach one
A limit stops a transaction before settlement, not after. Nothing is confiscated and nothing is held hostage; the transaction does not proceed. That is different from a hold, where a transaction already in progress is paused for review, and different again from a report, which by law cannot always be discussed with the customer.
If you are stopped, the useful responses are to wait for the window to roll, or to supply the documents that raise the ceiling. The unhelpful response is to try again in a different shape.
One habit avoids nearly all of this. Before buying or accepting a voucher larger than anything you have exchanged before, ask support what the ceiling is and how the window is measured. A limit discovered in advance is a calendar problem. A limit discovered with a code already in your hand is a code you are holding until the window rolls.