The money that must go back the way it came
A withdrawal is not a payment out of a balance. It is the reversal of the deposits that built it, rail by rail. This desk explains the rule that pairs every withdrawal to the deposits behind it - the four things it decides, the cap each rail carries, the arithmetic of splitting one request across several rails, and the routes left open when a rail has gone.
- The rule
- a rail may return only what it paid in
- The name
- the destination must carry the account holder
- The split
- one request, one payment per rail
- The dead rail
- re-route, or the cap is unreachable
Four decisions, one rule
The whole arrangement comes down to four questions, asked in this order every time a withdrawal is requested. Each one can stop a payment on its own, and each one is answered by the operator’s own withdrawal policy rather than by a rule a reader can appeal to a licence for.
Whose name is on the destination
The account that receives the money must carry the same name as the gambling account. A rail paid by somebody else cannot return the money - not because the payment failed, but because the name does not match.
Which rail the money must travel
A rail may only carry a withdrawal once it has carried a completed deposit. The test is a settled deposit, not a saved card: a rail with no completed deposit behind it has a cap of zero however long it has been on the account.
How much each rail may return
Each rail carries a cap - what it paid in, less what it has already paid back. Once a rail has returned its cap it cannot carry another withdrawal, so a large request is met by the next rail rather than by the first one alone.
What happens when the rail is gone
A closed bank account, an expired card and a dead wallet all leave a cap that exists on paper and cannot be paid. The money is not lost; it is unreachable until the operator re-routes it, and re-routing is where the delays and the fees sit.
Where every number on this desk comes from
No operator’s policy is quoted anywhere on this site. Six invented samples carry the arithmetic, and every other figure is derived from them. They are small enough to re-derive by hand, which is the point: a reader can check the mechanism without trusting a number.
S1 - the two-rail account
200.00 arrived by card and 240.00 by bank transfer, so 440.00 of cap exists. The balance is 500.00 after a 60.00 win, and the whole 500.00 is requested back.
S2 - the partial withdrawal
30.00 by card and 70.00 by e-wallet, with 40.00 requested back and 60.00 left in the account - the case that separates a waterfall rule from a proportional one.
S3 - the verification deposit
A 10.00 deposit from a rail never used before, then a 400.00 request - the case that shows what a test deposit actually unlocks.
S4 - the dead rail
200.00 arrived by a card that expired fourteen months ago, and 200.00 is requested back - the case where the cap exists and the rail does not.
S5 - the third-party payer
150.00 arrived on a card in somebody else’s name, and the withdrawal stops at the name check - the case where the money has a working rail and the name rule still closes it.
S6 - the desk’s book
12,000 withdrawal requests against a mixed-rail book, of which 8,160 used one rail, 2,880 used two and 960 used three or more - the sample behind the split rates on this desk.
That is the whole mechanism in four lines. The 500.00 did not leave the account as one payment because it never entered as one: it entered as a 200.00 payment on one rail and a 240.00 payment on another, and the loop returns each part to where it came from. The 60.00 above the caps is the only part that behaves like a fresh payment, and on the sample terms it travels on the operator’s default rail for released funds.
Why a reversal reads as a refusal
The mechanism is an accounting reversal, and it lands as a rejection. That gap is worth naming, because a reader who understands it stops arguing about the wrong thing - the person in the queue cannot release a cap that has no rail behind it, however sympathetic they are.
One pot in the reader’s head
A balance screen shows a single number, so the money in it is treated as one pool - the mental account most people keep. The rule keeps several pools, one per rail, and the two do not agree. The reader is told they have 500.00 and cannot move 60.00 of it; both statements are true, which is what makes the exchange feel like a trick.
A rule that reverses a receipt
A withdrawal that returns to the card it came from is a refund of a payment, not a payment out of a balance. Reframed that way it is unremarkable - nobody expects a refund to arrive somewhere the purchase never came from. Framed as a withdrawal it reads as the operator redirecting money, and the delay that follows reads as withholding rather than as the card rail’s own settlement clock.
Neither framing is a discovery about any operator. Both are reasons a reader’s first instinct - ask for it to be sent to the account that is convenient - is answered with a rule rather than a yes, and why the answer is usually accurate even when it sounds evasive.
Why the loop exists at all
Three reasons, and they are worth separating because only one of them is about the reader. First, a card payment can be charged back by its issuer long after it settled, so an operator that has paid a card deposit out to a bank account is left holding a reversed payment it cannot recover. Second, a payment that leaves by a different route than it arrived is the shape a money-laundering pattern takes, so the loop is written into anti-money-laundering procedure and sometimes into the conditions attached to the operator’s licence. Third, a rail that has paid a deposit has already been verified once, at the reader’s own bank, which makes it cheaper to trust than a rail the operator has never seen.
What a reader can take away in one pass
Three things on this site are meant to be used rather than read, and all three can be produced from a payment history a reader already has.
The rails table
Which payment methods on an account can return money at all, which cannot and why. It answers the question before a request is made, in one screen.
Your own cap table
Four columns - the rail, what it paid in less what came back, the cap, and the rail’s state - built from the payment history and finished in a few minutes.
The prediction
How many payments the next withdrawal becomes, which rail closes first, and whether any part of the balance is released money with no rail behind it. A slow payment and a missing one stop looking alike.
How to use this desk
The pages run in the order the rule applies. Read the first two to learn the shape of the arrangement, the next four to work out what a specific account can actually return, and the last three to deal with a payment that has stopped moving.
| The rail | Can carry in | Can return | The cap it creates | Its state |
|---|---|---|---|---|
| Card | deposits, up to the issuer’s own limit | up to what it paid in | what it paid in | open after one settled deposit |
| Bank transfer | deposits | up to what it paid in | what it paid in | open after one settled deposit |
| E-wallet | deposits | up to what it paid in | what it paid in | open after one settled deposit |
| Crypto address | deposits | to that same address only | what it paid in | open while the address is retained |
| Prepaid voucher | deposits | nothing at all | none | closed: no return path exists |
| Card since expired | nothing further | nothing | what it paid in, unreachable | gone: re-route only |
| The rule in one line | any rail may pay in | only a rail that paid may pay out | the cap is what it paid in | and only in the holder’s name |
| The rail | Paid in | Share of deposits | Waterfall: oldest first | Proportional | Difference |
|---|---|---|---|---|---|
| Card | 30.00 | 30.0% | 30.00 | 12.00 | +18.00 |
| E-wallet | 70.00 | 70.0% | 10.00 | 28.00 | −18.00 |
| Both rules | 100.00 in | 100.0% | 40.00 | 40.00 | 18.00 moves between the rails |