Orca

Apple 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 Apple, through the Apple Developer Program License Agreement and the Acceptable Use Guidelines for Apple Pay on the Web, for the wallet's own rules; the card network, the card issuer and the merchant's acquirer 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: Apple 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 Apple rules and what the network rules, and links to the visa and mastercard facts rather than restating them; 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; Apple Pay Platform Web Terms and Conditions: accepted inside a developer account, no public copy, not read; Apple Platform Security (the Apple Pay chapter), the Apple Pay planning and marketing pages, the Human Interface Guidelines and the Apple Pay Marketing Guidelines: not among the pages saved on 2026-09-20 and not read, so the in-store contactless flow, the Secure Element's role and the branding rules rest only on what the pages that were read say; PKPaymentError and the other PassKit error codes: not read; there is no code list for this rail and the token fields sit in the messages fact; no amount limit of Apple's own was found in the pages read; whether one exists is unverified; Apple merchant tokens for recurring and merchant-initiated charges: how one is revoked, disputed or expires was not read, so no Mandate is drafted; the public Developer Program License Agreement is a convenience copy; the version a developer accepts in its account is the binding one, as the page itself says; outside this rail: Apple Cash, Apple Card, transit, identity, loyalty and access passes, Tap to Pay on iPhone, and purchases of Apple's own goods and services, where Apple is the merchant.