NS Toor’s initiative to facilitate financial literacy ·

Banking India Update

— Independent · Daily —

Three-Account Limit Blocks 27% of Welcome Bonus Claims at Signup

Onboarding data shows a three-account cap blocked 27.4% of welcome bonus claims across 18,600 Indian signups, rejecting users before any deposit

Three-Account Limit Blocks 27% of Welcome Bonus Claims at Signup
Three-Account Limit Blocks 27% of Welcome Bonus Claims at Signup

A three-account cap applied at registration blocked 27.4% of welcome bonus claims in a sample of 18,600 Indian signups tracked across four operators between January and March 2025, according to onboarding data circulated to affiliates this month. The figure covers claims rejected before any deposit was made, meaning the affected users never reached a wagering stage. It is the first hard number attached to a rule that most India-facing brands introduced quietly over the past two years.

The mechanism is unremarkable on its face. Operators cap the number of accounts a single person may hold, usually at three, and enforce the cap by matching PAN, mobile number, device fingerprint and, in some cases, UPI handle at the point of registration. What the 27.4% figure exposes is how much of the acquisition funnel that check now consumes. The rejections are not fraud findings in the criminal sense; the overwhelming majority are duplicate or near-duplicate registrations by the same individual, often created to claim a second or third welcome offer.

What the 27.4% actually measures

The sample is narrower than it looks. The four operators are mid-tier brands with a combined Indian traffic base of roughly 1.1 million monthly visits, and the data covers only signups that arrived through affiliate links, not organic or paid search. Affiliate traffic skews toward bonus-seekers, so the rejection rate is almost certainly higher than it would be across the full funnel. A reasonable estimate for blended signup rejection sits closer to 15–18%, though no operator has published a blended figure.

The composition of the 27.4% matters more than the headline. Roughly two-thirds of blocked claims came from users who already held an account with the same operator — the classic multi-account bonus harvest. The remaining third were blocked for holding accounts at three or more sister brands under the same licence, a category that has grown as consolidation has put more skins behind a single compliance team.

That second category is where the policy gets contentious. A player who signed up with Operator A in 2022, took a welcome bonus, and then registers with Operator B — acquired by the same group in 2024 — is now treated as a fourth-account applicant if they hold two other accounts elsewhere in the group. They did not choose to become a multi-account user; the corporate structure changed under them.

The sister-brand problem

Group-level caps are usually disclosed in general terms ("one welcome offer per person, household or IP address") but rarely spelled out as a group-wide count. When a brand is folded into a larger licence, the effective cap tightens retroactively. Complaints to Indian-facing support desks about this specific scenario rose through Q4 2024, though operators do not publish dispute volumes and the sample here cannot quantify them.

Why operators moved the check earlier

Before 2023, most India-facing operators ran duplicate-account checks at first withdrawal, not at registration. The logic was commercial: let the player deposit, play, and only then decide whether the second account was legitimate. The cost was that bonus funds had already been credited and often partially wagered by the time the check fired, and clawing back a bonus from a player who had since lost the deposit created support nightmares and, occasionally, public complaints.

Moving the check to signup shifts the cost onto the player. A blocked registration produces no deposit, no bonus liability, and no reversal conversation. For the operator, the economics are straightforward: a welcome bonus at a typical ₹500–₹2,000 face value with a 30x wagering requirement carries an expected cost that is hard to recover once the funds are live. Blocking 27% of claims at the door removes that exposure entirely.

The trade-off is friction. Every false positive is a genuine new player who bounces. Device fingerprinting is the usual culprit — shared family phones, cybercafés, and hostel Wi-Fi in tier-2 and tier-3 cities produce collisions that have nothing to do with bonus abuse. Operators in the sample acknowledged the issue privately but would not put a number on false-positive rates.

The India-specific friction

Three factors make the cap harder to administer in India than in markets where it originated.

Identity matching is patchy. PAN is the strongest identifier available, but not every signup supplies it at registration; many operators collect it only at KYC, which for low-deposit players may not happen until withdrawal. Mobile numbers are recycled aggressively by Indian telcos, and a number that belonged to one person in 2022 may belong to another in 2025 — a recycled number attached to an old account will flag a genuinely new player as a duplicate.

UPI handles are not stable identifiers. A single person may hold handles across multiple banks and payment apps, and family members routinely use a shared handle for small transactions. Matching on UPI therefore produces both false negatives (the same person using a different handle) and false positives (a shared family handle).

Household definitions are loose. Most terms bundle "person, household or IP address" into one prohibition. In a shared-occupancy market where four adults may share one broadband connection and one address, an IP-based cap of three accounts is functionally a cap on the household, not the person. Whether that is intended is rarely stated.

What the number implies for acquisition economics

If roughly a quarter of affiliate-sourced signups never convert to depositors because of the cap, the cost per funded player rises accordingly. Affiliates are paid on registration or first deposit depending on the deal; under a revenue-share model the blocked users cost the affiliate nothing but the traffic, while under a CPA model the operator is paying for signups it then rejects. Several affiliates in the sample have begun demanding that rejected registrations be excluded from CPA counts, a contractual fight that is likely to intensify as caps tighten.

For players, the practical effect is that the welcome bonus is increasingly a one-shot instrument. The multi-account workaround that sustained bonus hunters through the 2010s — register, claim, withdraw, repeat at a sister brand — is closing, not because any single rule is new but because the checks now happen before the money moves.

The open question is whether the 27.4% is a stable cost of doing business or a transitional artefact. If the figure reflects a pool of habitual multi-accounters who will eventually be flushed out of the funnel, rejection rates should fall through 2025 as that pool exhausts itself. If it instead reflects false positives from shared devices and recycled numbers, the rate will hold steady or climb as more brands adopt group-level caps. The operators in the sample are not publishing follow-up data, and until someone does, the difference between a clean-up and a leak remains a matter of inference. Players who find themselves blocked on a first-ever registration should treat it as a KYC dispute rather than a ban, and ask which identifier triggered the match — the answer is usually more informative than the rejection itself.