▣The Closed Loop Open the partner account
paid
Affiliate disclosure. The partner link in the masthead and in the bands beside the copy on this page is a sponsored link to a partner operator, and this site may be paid if you open an account through it, at no extra cost to you. It carries rel="sponsored noopener" and opens in a new tab. That matters on this desk in particular: the subject is which rail a withdrawal may travel and how much each one may return, and this site’s revenue depends on a reader opening an account. No operator, bank, wallet or regulator is named, rated or recommended anywhere on this site.
The Closed Loop / The rule
The mechanism

A withdrawal is the reversal of a deposit, not a payment from a balance

The single idea behind every delay, split and re-route on this desk is that an outgoing payment has to be matched to an incoming one. Once that is clear, most of what looks arbitrary about a withdrawal stops looking arbitrary, including the parts that are genuinely unfair.

Rail stub
What opens a rail
one settled deposit
What closes it
the cap being reached
The order
published, and it differs
The default
oldest rail first
the railA payment method that has carried a completed deposit - not a method saved on the account
the capWhat a rail paid in, less what it has already returned, and never below zero
released moneyThe part of a balance above every cap: payable, and travelling by the operator’s own route
Direct answerA closed loop pairs each withdrawal to the deposits behind it, so the money leaves on the rails that brought it in. A rail opens when a deposit on it has settled and closes when it has returned everything it took in. That is why a balance is not a single pot and a withdrawal is not a single payment.

The rule in one sentence

Every unit of money on a gambling account remembers where it came from, and the withdrawal that removes it has to travel back along the same rail. In practice the operator does not track units, because it does not need to: it tracks what each rail has taken in and what it has already sent back, and the difference is the rail’s cap.

This is why the two most common surprises on a withdrawal are not errors. A reader who deposited by card and asks for the money back at a bank sees the request land on the card. A reader who deposited from three sources sees three payments arrive, at three different speeds, on three different days - and each of those days is set by the rail, not by the operator.

The loop in five steps

  1. A deposit settles. Not when it is requested and not when it appears as pending: when the rail has completed it and the operator can no longer lose it to a failed authorisation. The card’s own settlement is the clock, and it is why a deposit made moments ago may not yet have opened the rail.
  2. The rail opens and takes a cap. The cap is exactly what that deposit put in. A 200.00 card deposit opens a 200.00 cap. It does not open a share of the balance and it does not open a share of the account’s largest deposit.
  3. Play happens inside the account. Winning and losing does not move money between rails. A balance of 500.00 on an account whose deposits total 440.00 is 440.00 of cap plus 60.00 of what the desk calls released money.
  4. A request is bounded by the caps. The amount that can travel back along the rails is the smaller of the request and the total cap. Anything above the cap is released money and travels by whatever route the operator nominates for released funds.
  5. Each rail is paid its share and its cap falls. A rail that has returned its cap cannot return anything further, however large the balance still is. From then on the request is met by the next rail in the operator’s published order.
The bound, worked: a 300.00 request against S1caps 200.00 card + 240.00 bank = 440.00 requested = 300.00 looped min(300.00, 440.00) = 300.00 released 300.00 - 300.00 = 0.00 split card 200.00 (cap met), bank 100.00 (140.00 of cap left) after card 0.00 of cap, bank 140.00 of cap result two payments, no released money, one rail closed

The useful thing about the bound is that it is boringly predictable. A 300.00 request on this account is 200.00 to the card and 100.00 to the bank, every time, until the card’s cap is spent. A reader who knows their own deposit mix can predict the number of payments and which rail closes first without asking anybody.

Three reasons the arrangement exists

A card payment can come back

An issuer can reverse a settled card transaction long after it cleared. If the operator has already sent that money to a bank account, the reversal leaves it holding a debt it cannot collect. Returning the money to the card keeps the reversal and the recovery on the same rail.

A different route is a laundering shape

Money in by one route and out by another is the pattern that, in a different context, describes layering. The loop makes the account’s outgoing payments legible: each one has an incoming payment it answers, and an operator can show that to a supervisor.

A rail already verified itself

When a bank or a wallet completes a payment it has already checked the name and the account. Sending money back to the rail that paid means sending it to a destination that was verified once already, at somebody else’s expense. That is the operational reason, and it is the one that explains the test deposit.

What the loop is not

Three distinctions matter, because each of them is a place where a reader is told something by a support agent that does not match the mechanism.

Not a limit on the balance

The cap applies to the route out, not to the balance. Money above the caps is still theirs and still payable; it simply cannot travel on a rail that has already returned everything it took in. A balance larger than the total cap is normal, not a problem.

Not a fee and not a hold

A cap is an accounting boundary, not a charge. Reaching it does not cost anything and does not require a form. The fees and the forms live one level up, in the re-route that is needed when a rail has gone, which is a different mechanism with its own arithmetic.

One more: the loop is not symmetric. Money can be paid in by a rail that can never pay out. A prepaid voucher and a cash-based deposit are both accepted by most operators and both return nothing at all, because there is no destination behind them. Those deposits are still capped - the money entered, so it has a cap - but the cap can only be reached through a re-route, and the operator decides whether to offer one.

The asymmetry is the part worth noticing. A voucher adds to the balance and adds nothing to the routes out, which means a reader who funds an account only with vouchers has a balance and no working rail at all. Every subsequent payment depends on a re-route. That is a design choice the operator makes, and there is no rule that requires it to be disclosed where a reader first meets the rail.