▣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 / Myths
Six beliefs, checked

Six things readers believe about withdrawals, and what is actually true

Each belief below is common, half-true in a specific way, and worth separating from the mechanism. Where the desk takes a position it is about the arithmetic rather than about any operator’s conduct.

Rail stub
Checked
six beliefs
Verdicts
two true, three partly, one false
The false one
a smaller request cannot be split
The useful one
the caps decide, not the balance
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 answerThe beliefs that survive contact with the mechanism are that the caps and not the balance decide what can travel, and that a split is normal. The one that does not survive is that asking for less avoids a split - a small request can touch every open rail under a proportional rule.
False

“Ask for less and it will not be split.”

The number of payments is set by the rails the request reaches, and the rule that divides it. On S2 a 40.00 request touches two rails and becomes two payments under either rule. Under a proportional rule a 5.00 request still touches every open rail, because each one pays its own fraction.

True

“The caps, not the balance, decide what can travel.”

This one holds without qualification. S1 has 440.00 of cap behind a 500.00 balance, so 60.00 has no rail at all. A reader can win for a year and the caps still record only what came in - which is what makes the table predictable and the balance beside the point.

Partly

“A test deposit unlocks a rail.”

It opens the rail and it caps it at its own amount. A 10.00 test on S3 creates 10.00 - 2.5% of a 400.00 request - and the remaining 390.00 still needs rails that took it in. The rail is unlocked; the capacity is not.

Partly

“The withdrawal must go to the method you used most.”

It must go to methods you used. Frequency is not in the rule: the caps and the published order decide, and a rail used once for 240.00 carries a larger cap than a rail used five times for 10.00 each. Percentage of deposits is only relevant if the operator applies a proportional rule.

True

“A split is not a fee and not a fault.”

Two credits where one was expected cost nothing and are not an error. They are the loop paying each rail its own cap. What a reader should check is not the count but the arithmetic: if the caps account for the whole request and the credits do not, then something really is missing.

Partly

“The operator can send it wherever it likes.”

Not anywhere - the name rule and the caps bind it. But above the total cap the money is released, and released money does travel by whatever route the operator nominates. On S1 that is 60.00, a tail the operator controls that is invisible on a balance screen.

The one belief worth replacing

Most of the six are half-right because they describe the loop from the outside, where a balance and a single “withdraw” button make the account look like one pot. The belief worth actually replacing is the first: that a smaller request behaves like a simpler one. It does not, under a proportional rule, and the reason is worth holding on to because it explains a whole category of surprise - the reader who asks for a modest amount, sees it arrive in four credits over three days, and concludes the operator is withholding something.

What the desk does not claim. These verdicts are about the mechanism, not about any operator’s fairness. A loop applied to a reader who has deposited 440.00 and wants 500.00 out is doing exactly what it says. Whether the same mechanism should apply to released money, what a re-route should cost, and whether a help page should say so are questions about policy, and this desk rates nobody.