The destination must carry the name on the account, and nothing else fixes that

The name rule is the part of the loop with no arithmetic and the most consequences. It is also the one most often met as a surprise, because a rail can be perfectly healthy - funded, verified, working - and still unable to receive a payment that the operator has no way to release.

Rail stub

What must match: the account holder’s name
What is checked: name, and country of the account
Ignored: the card number, the date of the deposit
A mismatch: a hold, not a refusal

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 destination account must be in the same name as the gambling account. A deposit made from somebody else’s card or bank account creates a rail whose cap cannot be paid out, so the money behind it is held while the operator decides whether to re-route it. It is a hold, not a confiscation.

What exactly has to match

The comparison is between the name registered on the gambling account and the name on the destination the money is going to. In practice an operator checks three things and ignores a fourth.

Checked: the name

The account holder’s name against the destination account’s name. Minor formatting differences - initials, accents, a middle name present on one and not the other - are usually resolved by a person rather than rejected outright.

Checked: the country

The country of the destination account is compared with the account’s own registered country. A destination in a country the operator does not serve, or does not serve under the licence the account sits on, is stopped even when the name matches.

Checked: the name on the rail

The payer name recorded on the incoming deposit. This is what catches a partner’s card, an employer’s card or a parent’s account, and it is the check that creates most of the holds on this desk.

Ignored: everything else

The card number, the date of the deposit and the amount are not part of the name test. A reader who explains a discrepancy by reference to a card number will usually be trying to settle a question that was never being asked.

The checks, counted: S5 against a two-field testfields compared 3 name, destination country, payer name fields ignored 1 the instrument itself S5 deposits 150.00 from a card in another name match on name yes - the card was not in their name hold created 150.00 share of a 440.00 account 150.00 / 440.00 = 34.1% held days, the sample 9 working days documents asked 3

The arithmetic here is only one line of division, and that is the point: a mismatch does not scale with the size of the account, it removes one rail’s cap from the working set. On S5 that removes 150.00 of 440.00, or 34.1%, from the money that can travel, and leaves everything else payable. A reader whose other deposits are clean is not waiting on the whole balance.

Why the hold exists rather than a refusal

A refusal would be simpler and would answer the wrong question. The operator is not saying the money is not the reader’s; it is saying that the rail it came from is not a rail it can safely pay back to, and that it cannot yet tell whether this was a one-off family payment or an account being run for somebody else. So it holds the amount and the reader is asked for evidence of the relationship.

What counts as evidence is set by the operator, and the sample asks for three things: a statement from the payer identifying the payment, confirmation of the relationship, and identification of the payer. The pattern worth recognising is that none of the three is about the reader’s own identity - which was already verified to open the account - and all three are about a third person, which is why these requests feel intrusive and why they take days rather than minutes.

A joint account is not a match. Two names on the destination do not answer a check that is looking for one, and the usual outcome is a second review rather than a release. If the destination is joint, say so at the start: it decides which document is asked for and can save one round of correspondence.

What to do when the mismatch is yours

Find every deposit that was not paid from an account in your own name. The own-payment history is the first thing to read, and it lists the payer name on each credit.
Add up those deposits. That total, not the balance, is the amount currently behind a frozen cap - 150.00 in S5.
Take the untouched rails first. Any rail funded entirely by you can still carry its cap, so a withdrawal can be split around the frozen one instead of waiting on it.
Ask which documents are wanted before sending any. The list is short and specific, and sending identification that was not asked for slows the review rather than speeding it up.
Keep the request in one thread. The decision to release a held cap is made by a person looking at one record, and two parallel queries usually end with two people each waiting for the other.