---
page_title: DPAN vs MPAN
product: Digital Wallets
page_source: https://juspay.io/in/docs/digital-wallets/docs/resources/dpan-vs-mpan
llms_txt: https://juspay.io/in/docs/llms.txt
product_llms_txt: https://juspay.io/in/docs/digital-wallets/llms.txt
---


# Understanding Apple Pay token type



Apple Pay never shares the customer’s actual card number. Instead, it provides a **tokenized card number** , which may be either **DPAN**  or **MPAN** , depending on the card issuer and network.This token type affects how the transaction is processed **and must be passed correctly in your integration** .

The exact parameters required can vary based on your **Integration Type**  (HyperCheckout, Express Checkout SDK, or Express Checkout API) and **Platform**  (Web or iOS Native). 


| Token Type | Full Name | Scope | Usage Behavior | Suitable For |
|---|---|---|---|---|
| DPAN | Device Primary Account Number | Generated per device (e.g., iPhone, Apple Watch) | A new DPAN may be returned on each transaction. Cannot be reused reliably for future charges. | One-time payments |
| MPAN | Merchant Primary Account Number | Assigned to your merchant across all the customer’s devices | Stable token that remains consistent for your merchant. Can be safely stored and reused for future payments. | Subscriptions, Auto-debits, Saved card flows (if supported by issuer) |


---

## See Also

- [Process Call](https://juspay.io/in/docs/digital-wallets/docs/how-to-integrate-native/process-call)
- [Troubleshooting & FAQ's](https://juspay.io/in/docs/digital-wallets/docs/resources/troubleshooting--faqs)