Why a second account exists, and which one survives

Second accounts are not all suspected fraud. Some are opened deliberately to get around a rule, and some arrive by accident - a forgotten login, a name change, a registration completed twice - but the comparison treats every duplicate the same way and resolves the pair the same way. This page covers the reasons and the resolution.

Open the partner account Start with what the clause says

Joins the two: one artefact, one person expectedKeeps them apart: a verified fact that differsA person decides: an overlap a household also produces

Direct answerA second account at one operator is opened either deliberately, to escape a limit, an exclusion or a restriction, or by accident through a forgotten login, a change of name or a duplicated registration. The comparison treats both the same way once the signals match. Where the operator concludes the two records are one person, the account it recognises is normally the earlier one, and the later account's balance is resolved under the terms, which usually means the deposit returned and anything built on it removed.

Why the pair gets resolved rather than both closed

Because the operator's interest is in one accurate relationship with one known person, not in the number of records. Closing both would leave the customer with no account and no way to settle a balance or act on an exclusion; keeping both would leave the first account's limits, conditions and checks blind to the second one's activity. Recognising one is the only resolution that keeps every other obligation working, which is why it is the one the terms describe.

Worked example - which record survives, and what that leaves (illustrative) Account A opened 4 March 2021, verified, holds limits set by the customer. Account B opened 11 August 2026, verified, no limits set, balance 1,850.00. Signals joining the two: the same name, the same date of birth, the same verified document number = 3. Decisive. The recognised account is A, because it predates B. Resolution for B: the deposits made into it are returned - here 640.00 - and the outcome built on them is removed, which in this example is the 1,210.00 of withdrawals already taken out being set against the position rather than returned twice. Amounts: balance at review 1,850.00; deposits 640.00; withdrawals 1,210.00. Deposits minus withdrawals = -570.00, which is the net position the operator works from rather than the balance on the screen. That is the part of the arithmetic a reader is least prepared for: the figure that is dealt with is not the account's balance, it is the account's deposit history net of what has already gone out.

The four reasons a duplicate appears

A rule is in the way of the first account. A deposit limit, a loss limit, a self-exclusion, a stake restriction or a bonus exclusion is the most common deliberate reason, and it is the case the clause is aimed at. It also fails most reliably, because the signals that trigger the restriction are the signals the comparison already holds.
An accident with the paperwork. A forgotten login, an email address that changed, a name change after a marriage or a correction, a registration completed twice on a slow connection. These are ordinary, they usually link, and they are usually resolved with an explanation rather than a penalty.
A shared household member opening their own account badly. The second adult registers with the first adult's details still auto-filled in the browser, or with a shared email address. The joining signals can then be artefacts of inattention rather than of intent - which is precisely what the household page prepares a reader to explain.
Two people, one facility, one funded by the other. Third-party use rather than duplication: the money is one person's and the play is another's. This is treated under the personal-use obligation, and both accounts can be affected rather than just one.

What happens in the days between

A duplicate is not usually noticed at the moment it is created. It surfaces on a withdrawal, when a check runs on the destination and something in the comparison returns two records; on a limit being set and something in the history looking inconsistent; or on a periodic review. Between creation and discovery the account has been trading, and that is what makes the resolution more complicated than a form being corrected: bets have been placed, conditions have been partly met, and a balance has moved.

The mechanics of that unwinding - what is removed, what is kept, and in what order the money is counted - are on the consequences page, because they are the part of this desk where the arithmetic does the most work and where a reader's expectations are furthest from the terms.

The one thing that helps, and when

Raising the duplicate before it is found. An operator told about a forgotten second account with no activity on it has an administrative correction in front of it, and the case is usually resolved by closing the later account and moving the deposit back. The same duplicate discovered during a withdrawal review, with a balance built on it, is a dispute about money. The two are the same facts in a different order, and the order is the only input the reader controls - which is the honest reason this page exists at all.

What this page is not. It is not advice about which account to keep, and it does not describe how a duplicate can be kept from being noticed. It is a description of how a duplicate is treated once it is: the earlier account is recognised, the later one is resolved, and the figure that gets dealt with is the net deposit position rather than the balance a reader can see.