Brazil Android entry card: test PIX and wallet routes without stretching the iOS card

This is the Google Play companion to the Brazil iOS first-test card. Apple’s Brazil payment scope is narrower; Play’s country record adds PIX and named wallets that need their own observation 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 Brazil. Documented route examples for this card: PIX, PicPay, Mercado Pago, PayPal, Play balance, named credit cards, and debit only when added through Google Wallet. Google lists American Express, ELO, Mastercard and Visa for credit. Debit or combo cards must be added through Google Wallet; debit cards added directly on Google Play will not work, per the live help text. 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 Brazil 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

Use a Brazilian Play storefront test account and one authorised route available to the tester. For PIX, record code or QR generation, the stated expiry window, processing lag and entitlement delivery as separate observations. A successful credit-card test does not certify PIX, PicPay or Mercado Pago.

Localise the observed journey

Review Brazilian Portuguese in the playable, Play store listing assets and first paid offer as one sequence. Have the reviewer explain the purchase in their own words, then compare that account with the intended entitlement. Missing price context is a copy defect to investigate, not evidence that buyers require a lower price.

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: Brazil and LATAM: payments, pricing and UA 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.