Orca

Google Pay (pass-through wallet) Rail Facts

How money moves on this rail, in 12 sourced records: what is final, what can be returned, recalled or refunded, who decides, and what the limits are. A profile belongs to the rulebook, so no reason code list is published on this page.

What the tier labels mean, and how far this page has been checked
Draft
An agent wrote it from published material and nobody has checked it. Use it as a lead to confirm, never on its own as the basis for a retry, a return, a deadline or a compliance decision.
Corroborated
A validator found the same answer in one or more named public sources; the class in brackets says how strong they are. "Secondary sources only" means bank, processor or industry guides and nothing from the operator or regulator. Corroborated does not mean checked against the governing rulebook, so confirm before you act.
Verified
A person checked it against Google LLC, through the Google Pay API Terms of Service and the Google Pay and Wallet APIs Acceptable Use Policy, for the wallet's own rules; the card network, the card issuer and the merchant's card acquiring bank for the payment itself's own current text and recorded the edition and date. The strongest tier here, and still reference material, not legal or compliance advice.

On a rail fact, every detail line names the section or instrument it rests on and whether that is a rule, a law, operator guidance, or observed practice.

Known gaps in this build

Not yet covered: no money moves on this rail: Google Pay hands a card credential to a merchant, and the payment is a card payment on the card network, so every facet below says what Google rules and what the network rules, and links to the visa and mastercard facts rather than restating them; two credentials, and only one is a token: CRYPTOGRAM_3DS returns an Android device token with a cryptogram, PAN_ONLY returns the card number saved to the user's Google Account with no cryptogram; the device-token rules, the eciIndicator and Google's liable-party table do not reach a PAN_ONLY payment; the network rules themselves are not restated here and no Visa or Mastercard document was read for this rail; the wallet facts link by uid to corpus/visa, corpus/mastercard and corpus/visa-dispute, which rest on those rulebooks; the pages read cover the Google Pay API for the web; Google Pay used to tap in a store, the Android API and the merchant and PSP APIs were not read, so no in-store transaction type is recorded; the Google APIs Terms of Service, which the Google Pay API Terms of Service incorporate, the Google Pay API Brand Guidelines, the Google Wallet consumer terms and the token lifecycle management guide: named on the pages read but not read; no amount limit of Google's own was found in the pages read; the one amount rule is that a merchant may not set a minimum or maximum specific to a buyer paying through the API; the reach of Google's own report-a-problem flow for a card payment to a third-party merchant is not stated on the help page that was read; Google merchant tokens (merchantTokenId, tokenUpdateUrl) for merchant-initiated charges: how one is revoked or disputed was not read, so no Mandate is drafted; outside this rail: Google's stored balance and bank-transfer features, Google Pay in India (a UPI app), Google Wallet passes, and purchases of Google's own goods and services such as Google Play and YouTube, where Google is the seller.