▣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 small print
Where the rule lives

Four places carry the loop, and only one of them is the terms

The rule that decides a withdrawal is spread across four surfaces with different weight. Reading the wrong one is how a reader ends up quoting a help-centre page at an operator that is applying its withdrawal terms.

Rail stub
Weight 1
the withdrawal terms
Weight 2
the licence conditions
Weight 3
the payment page
Weight 4
the help centre
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 loop appears in four places: the withdrawal terms, which govern; the licence conditions, which constrain the operator; the payment page, which shapes what a reader sees; and the help centre, which explains without binding. A support message is an explanation, and an explanation is not the clause.

The four surfaces, and what each can decide

The withdrawal terms

The governing text. It says which rails may be used, whether the loop is mandatory, the order rails are tried, and whether a re-route is offered at all. Where the terms are silent, the operator’s practice is the only evidence.

The licence conditions

The regulator’s requirements on the operator, which sometimes require a loop and sometimes require an exception to it. A licence condition is not a promise to the reader, though it is often cited as one - it binds the operator towards its supervisor.

The payment page

The page where a deposit method is chosen. It shapes expectations by omission: a method can be offered for deposits without saying that it can never return one, and the pre-selected destination can be a rail the reader has never used.

The help centre

Explanations, timelines and worked examples. Useful, specific and not binding. A helpful article that says a withdrawal “usually” returns to the deposit method is describing practice, and practice can be applied differently to one account without any clause changing.

How thin the published rule is, worked on the sampleplaces the loop appears 4 places that bind the operator towards the reader 1 (the withdrawal terms) places that describe practice 2 (the payment page, the help centre) sentences in the sample’s withdrawal terms 5 sentences that name the order rails are tried 1 readable in full 48 seconds share of the terms that carries the rule 5 / 412 = 1.2%

The last line is the point of the arithmetic. The clause that decides which of a reader’s rails is retired first can be about 1.2% of a long document, one sentence in a five-sentence section - and it is the sentence that determines whether an old card or a new bank account is spent. Most readers never see it, not because it is hidden, but because nothing about the deposit page points at it.

Which version applies to your withdrawal

The terms are updated, and the update decides which version governs a payment. The rule the desk would suggest is the one this series uses everywhere: the version that was in force when the request was made, on the date recorded on it - and the terms themselves say which date that is.

  1. Find the request date. Not the deposit date, not the account-opening date: the date the withdrawal was requested, which is usually shown on the transaction itself.
  2. Find the term’s effective date. The terms carry versions and dates, and the withdrawal section has usually changed at least once since the account was opened.
  3. Check for a notice period. Many terms provide notice before a change takes effect, which can make an earlier version govern a later payment - or the reverse. The notice clause is short and it decides this question by itself.
  4. Read the order, not the examples. The binding sentence is the one naming the sequence of rails. Worked examples on a help page describe the same rule applied once, and they are the part most likely to be out of date.
  5. Keep the version you are reading. A saved copy with its date answers a support conversation in one message, and terms pages change without an announcement.

What is not in the terms at all

Two things that shape the outcome are usually absent, and a reader should treat their absence as a gap rather than a promise.

The rule for dividing a request

Whether a partial request is met by waterfall or proportionally is often not stated. The payments themselves then become the only evidence, which is a poor basis for planning and a common source of surprise on the second withdrawal.

The re-route policy

Whether a rail that has gone can be re-routed, at what fee and with what indemnity, is frequently absent entirely - and absence is not a promise that a re-route will be granted. It is a decision made case by case at a desk.