India Android entry card: separate UPI purchase coverage from discontinued Netbanking

This is the Google Play companion to the India iOS first-test card. Keep UPI purchase coverage, RuPay one-time limits and the Netbanking discontinuation notice in separate evidence rows. Read the companion iOS first-test card for Apple storefront evidence; this Android card does not replace it.

What the official record establishes

Google documents accepted payment methods for India. Documented route examples for this card: UPI (including Autopay mandates for subscriptions), Mastercard, Visa, RuPay for one-time purchases only, and Play balance or recharge codes; Netbanking discontinued from October 2025 until further notice. Google’s India payment record states that from October 2025 onwards Netbanking is discontinued as an accepted form of payment until further notice, and that RBI card-storage rules affect how card details are saved. Methods can change. Country payment documentation is not proof that your particular game is approved, distributed or purchasable there; confirm distribution and buyer currency in Play Console against the supported-locations record.

For digital goods and in-app features, Play’s payments policy requires Google Play’s billing system unless an enrolled alternative-billing or external-offers programme applies. A first test that has not enrolled in those programmes should observe Play Billing, not an invented off-Play checkout. User-choice or alternative billing eligibility for India is programme-specific; see Google’s user choice billing overview before treating an alternative path as in scope.

Shared Play readiness that can block an update before any country test is useful: target API requirements (new apps and updates must target Android 16 / API 36 from 31 August 2026, with an extension path to 1 November 2026); Play Billing Library 8+ by the same August date; and 16 KB page-size support for apps targeting Android 15+, with unsupported updates blocked from 1 February 2027. These are build checks, not country performance claims.

The first test to run

Create separate observation rows for a one-time UPI purchase, any Autopay/subscription mandate the product uses, and a card path if the tester’s account supports it. Do not treat a RuPay one-time success as subscription coverage. Do not record Netbanking as an available first-test route while the discontinuation notice remains on the live source.

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 Play build; preserve results separately from checkout outcomes.

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 across the ad network, MMP and Play order or voided-purchase signals. 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. Draft pending human editorial and local-market review. No observed campaign or purchase results are claimed.