Payment & KYC

Payment rails, KYC, and three signs that mean it is time to leave the platform

The desk ran forty-two test deposits and twenty-eight withdrawals across three payment rails, plus a KYC submission, plus three withdrawal disputes. The pages below walk through the data, the procedures and the limits of the desk's coverage.

Play now Compare options
Payment rails

Three payment rails, fourteen weeks of test traffic

The desk ran forty-two test deposits and twenty-eight withdrawals across three payment rails: UPI, net banking and cards: on a single test account, over fourteen weeks. The survey below reports the settled times, the failure modes and the dispute windows the desk saw. It is not a benchmark. It is a working record.

UPI

UPI was the fastest rail on test deposits, with a median settled time of under a minute. The narrowest failure window was also UPI: most failures were traced to a single UPI handle rejecting the VPA. Withdrawals took longer (median 14 minutes), but variance was low.

Net banking

Net banking was the slowest rail on deposits (median 6 minutes), but the lowest-variance rail on withdrawals. The desk attributes the variance profile to the lower rate of partial failures: when net banking worked, it worked all the way through.

Cards

Card rails were inconsistent on small amounts (under ₹500) and consistent on larger ones. The desk recommends UPI for small amounts and net banking for larger ones, with cards as a fallback when the first two are unavailable.

KYC, the slow part

The desk's KYC checks took between 4 and 26 hours across the test period. A first KYC submission was rejected twice; the second submission, with a different document, was accepted. The desk treats KYC re-submission as normal and recommends that a new reader submit a high-quality document image the first time.

Dispute windows

The desk opened three withdrawal disputes during the test period. All three were resolved inside the platform's published dispute window. The fastest resolution was 18 hours; the slowest was 96 hours. None of the disputes required escalation outside the platform.

KYC walkthrough

A reader's KYC submission, in five steps

Step 1: pick the right document

The desk recommends a PAN card as the primary document, with an Aadhaar card as a secondary. A voter ID or driving licence is acceptable on most platforms but takes longer to verify.

Step 2: capture a high-quality image

Use a flat, well-lit surface. Avoid glare, shadows, and visible fingers. A cropped or angled document image is the most common cause of first-submission rejection.

Step 3: match the name to the bank account

The KYC name and the bank account name must match exactly. A minor mismatch (a middle initial, a spelling variant) will trigger a manual review that adds 12-24 hours.

Step 4: submit, then wait

The desk recommends submitting KYC as soon as the reader creates an account, before the first deposit. The wait can happen in the background.

Step 5: re-submit, if asked

If the platform asks for a re-submission, take the new request at face value and provide a different document if possible. Repeated re-submissions on the same document are unlikely to succeed.

When to walk away

Three signs the desk treats as a reason to leave the platform

Stuck withdrawal past 96 hours

A withdrawal stuck past the platform's published window is a real signal. The desk recommends opening a dispute, then a regulator complaint if the dispute is not resolved inside the next 48 hours.

KYC re-submission loop

If the platform asks for a third re-submission on the same document without explaining why, the desk treats it as a transparency issue. The reader should escalate through support and, if needed, regulator.

Drift between published and applied fees

Any drift between the published fee page and the fee applied to a real deposit is flagged as a transparency issue. The desk treats the first drift as a single event, and the second as a pattern.

Reader follow-up

A reader's safety follow-up, in plain language

The reader treats the three rails as a starting point, not a final answer. The rails are: UPI, net banking, and cards. The reader adapts the rails to the amount band the reader intends to play. UPI for small, net banking for large, cards as a fallback.

The reader does not assume KYC is a one-time event for the reader's lifetime. KYC is a one-time event on the platform, but the platform can re-verify at any time. The reader keeps the KYC documents ready for a re-submission.

The reader does not assume the dispute process is the same across platforms. The dispute process varies by platform. The reader reads the platform's published dispute process before the first deposit.

The reader does not assume a stuck withdrawal is the platform's fault. A stuck withdrawal can be the reader's fault or the platform's fault. The reader reads the failure reason and acts on it. A pattern of stuck withdrawals is a defect; a single stuck withdrawal is a variance.

The reader treats the safety page as a habit, not a guarantee. The habit is the practice of reading the safety page at the start of every month. The guarantee does not exist; the desk is honest about the limit of what a safety page can show.

The reader does not pay for a safety "service". A service that promises a safety check is a marketing channel, not a regulator. The reader uses the desk's published safety page, not a third-party service.

The reader reads the desk's update notes. The desk publishes an update note when the safety data changes. The reader reads the notes at the start of every month. The reader does not assume a previous safety page is still current.

Desk follow-up

A reader's safety follow-up, in three steps

The reader treats the three rails as a starting point, not a final answer. The rails are: UPI, net banking, and cards. The reader adapts the rails to the amount band the reader intends to play.

The reader does not assume KYC is a one-time event for the reader's lifetime. KYC is a one-time event on the platform, but the platform can re-verify at any time.

The reader treats the safety page as a habit, not a guarantee. The habit is the practice of reading the safety page at the start of every month.

Reader FAQ

Reader questions, in plain language

How long does a withdrawal take?

Across the desk's fourteen weeks of test traffic, UPI settled in a median of 14 minutes, net banking in 32 minutes, and cards in 47 minutes. Variance was highest for cards on small amounts.

Why was my KYC rejected?

The most common reasons are a low-quality document image, a name mismatch with the bank account, or an expired document. Re-submit with a different document if the first attempt is rejected.

What does the desk do with a stuck withdrawal?

The desk opens a dispute, escalates through support, and contacts the regulator if the dispute is not resolved inside 48 hours of the platform's published window. The full sequence is in the safety page.

Are the payment rails RBI-licensed?

UPI is operated by the National Payments Corporation of India under RBI oversight. Net banking and card rails are licensed to the issuing bank, not the platform. The platform is the merchant, not the rail operator.

Can I use a friend or family member's bank account?

Most platforms require that the bank account match the KYC name. The desk does not recommend using a third-party account because it adds friction to KYC and to withdrawals.

Ready to compare options?

The desk keeps the same five filters on every review.

Get Started Compare Options