Why the money has to leave the way it came in

Nearly every regulated operator returns withdrawals to the method that funded the account, at least up to the amount deposited. Deposit by card, be paid back to that card. Deposit from a particular wallet, be paid to that wallet. This is the closed-loop rule, and it is the cause of a large share of “why won't they pay me the way I asked” complaints.

Where the rule comes from

Consider what a gambling account looks like to someone laundering money: a place to put funds in by one route and take them out by another, with a plausible explanation for the movement. That is the specific abuse the rule closes. If money can only return to its origin, the account cannot be used to change the shape of the funds.

Because it is an obligation rather than a preference, support cannot waive it for you, and there is no form of politeness that produces an exception. What they can sometimes do is tell you which route is eligible, which is the more useful question.

The consequences people actually hit

Winnings above your deposits

The loop applies to returning your own money. The surplus above it is often paid by a different method, frequently bank transfer, because not every rail can receive an arbitrary amount. So one withdrawal can legitimately arrive in two parts, by two routes, on two timetables.

Several deposit methods on one account

The operator may split the payout across them in proportion, or return to the most recent, or to the largest. All three are defensible and the terms will say which — this is the detail worth reading before you deposit by a second method.

A method that cannot receive money at all

Some funding routes are one-way by design. Prepaid vouchers are the classic case, which is why they get a piece of their own.

A card that has expired or been replaced

Now the loop points at something that no longer exists, and resolving it needs documents proving the new card belongs to the same person. Solvable, slow.

A whitelisted coin address that is not the depositing one

The loop can override your own security setting, because the two rules were written by different people for different reasons. See whitelists.

The third-party case, which is not a technicality

The loop has a companion rule: the account must be funded from a payment instrument in the account holder's own name. Depositing from someone else's card or wallet — a partner's, a friend's, a shared family account — creates a situation the operator cannot resolve cleanly, because returning the money to its origin means paying a third party, and paying you instead breaks the loop.

The usual outcome is that the deposit is returned to source and the account is restricted while it is sorted out. This is the one item in this piece that can cost you a whole balance rather than a few days, and it is entirely avoidable.

What to do before the first deposit

Three minutes, once per operator:

• Fund from an instrument in your own name, and from the one you want to be paid back to.
• Check the withdrawal terms for how they handle winnings above deposits and multiple funding methods.
• Avoid funding by a route that cannot receive — or accept in advance that the payout will come by another, slower one.
• If you intend to use a coin rail, deposit from an address you control rather than straight off an exchange, so the return address is one you can actually be paid at.

That last point is the one that catches crypto players: an exchange deposit address is not yours in the sense the loop means, and a payout sent to a wallet you did not deposit from may need justifying. It is also the same habit that protects you from the memo problem, for unrelated reasons.

When the rule is used as cover

Being a real obligation does not stop it being cited loosely. The honest version names the eligible method and the reason. The less honest version refuses a payout citing policy without naming what route would work. The question that separates them is short: “which method is this balance eligible to be withdrawn by?” An operator that cannot answer it has a different problem, and the piece on refused payouts covers what that looks like.