India iOS entry card: separate UPI purchase coverage from account top-ups

The India card draws a precise line around the payment evidence. Apple lists UPI and separately limits Net Banking to adding funds. These are different account actions. A launch plan should not merge them into an unsupported promise that every purchase accepts every listed method directly.

What the official record establishes

Apple’s service-availability record includes the App Store in its India section. Its payment-method record lists UPI; Net Banking is listed for adding funds only. These examples are not an exhaustive list: the live source’s eligibility notes still apply, and the page says methods can change. Storefront availability does not establish that your particular game is approved, distributed or purchasable there.

The first test to run

Create one observation row for funding an account and another for purchasing the configured item. Capture the resulting entitlement without retaining financial credentials. The first task may be unnecessary for an already funded account, but that does not mean its top-up path has passed a test.

Localise the observed journey

Choose language variants from the studio’s intended audience and commission reviewers for those variants. Do not claim that one translation represents India. Test script rendering, line wrapping and reward comprehension in the actual build; preserve results separately from checkout outcomes and paid-acquisition cohort quality.

Keep the decision tied to evidence

Use the editable launch checklist and CSV evidence matrix to keep documented availability separate from actual tests. Both include explicit untested states. The country card supplies no CPI, ROAS, payer-share estimate or legal clearance. Local expert review, game-specific distribution checks and real account observations remain outstanding.

Before a paid test, define the campaign identifiers, install cohort, offer event and purchase outcome you intend to reconcile. Inspect a permitted test transaction end to end, then preserve the raw event references. A successful walkthrough establishes implementation evidence for that case; it cannot establish campaign incrementality or expected acquisition economics.

Background in the existing archive: India: acquisition in a low-ARPU, high-volume market and Text-free playable design for global campaigns. These are contextual links, not a certification of every archived claim.

Research checked 19 September 2026. Local-market verification remains required. No observed campaign or purchase results are claimed.