
FPAN is the actual card number. DPAN is a device-specific token that Apple Pay and Google Pay use instead of the real card number. MPAN is Apple's merchant-specific token, designed to stay the same across a customer's devices, which is why it's built for subscriptions and card-on-file payments. Google Pay has no MPAN equivalent.
Anyone working with Apple Pay or Google Pay eventually runs into three acronyms that sound similar but describe different things: FPAN, DPAN, and MPAN. Here's what each one is.
The FPAN is the actual card number. It's the 16 digits printed on the physical card, tied directly to the cardholder's account at their issuing bank. When a customer types their card number into a checkout form, that's the FPAN. It's the source of truth that every other token ultimately maps back to.
When a card is added to Apple Pay or Google Pay, the wallet doesn't store the FPAN on the device. Instead, the card network issues a Device Primary Account Number and provisions it onto the device's secure hardware. A DPAN looks like a card number but isn't one. It's linked to that specific device and that specific card, and each transaction using it comes with a dynamic cryptogram generated on the spot. Add the same card to a second device, a watch alongside a phone, and that device gets its own separate DPAN.
Google Pay works a little differently here. Depending on how the card was added to the wallet, Google can return either a DPAN or the FPAN itself, rather than always tokenizing the way Apple Pay does.
An MPAN is a token tied to the merchant rather than the device. Instead of a new token every time a card is added to a different device, the merchant sees the same MPAN every time that customer pays, on any device, on any channel, without ever handling the FPAN. This is what makes MPANs suited to card-on-file scenarios like subscriptions, recurring billing, or automatic top-ups.
MPAN is specifically an Apple Pay term. Apple acts as the token service provider issuing these merchant-bound tokens, and there's no Google Pay equivalent by that name. Google Pay's tokenization works through DPANs and the FPAN fallback described above, not through a separate merchant-token system.
FPAN, DPAN, and MPAN all describe the same underlying card, just at different levels of exposure.
Think of the FPAN as your home address, the real, permanent location everything ultimately routes back to. The DPAN is more like a PO box tied to one specific delivery route. It gets you where you're going, but there's a different one for every device, phone, watch, laptop. The MPAN is closer to a standing forwarding address held by one specific merchant. It always resolves to you, no matter which PO box or device was used to send it.