What is a device account number?

How the number fits into an Apple Pay transaction

When a customer adds an eligible card to Apple Pay, the card details are evaluated by the relevant issuer and payment network participants. After approval, a device-specific Device Account Number is created for that card on that device. Apple says the original card number is not stored on the device or on Apple servers as part of Apple Pay provisioning.

When the customer authorizes an Apple Pay purchase, the device provides the Device Account Number and a transaction-specific dynamic security code along with the other information needed to process the payment. Apple documents this behavior for purchases at a contactless point of sale and for purchases made through participating apps or websites. The Device Account Number is therefore part of the payment credential used for the transaction, not a new bank account, a merchant account number, or a number chosen by the merchant.

How it differs from the card number

The number printed on a physical payment card is commonly called the primary account number, or PAN. EMVCo describes payment tokenization as replacing the PAN with an alternative payment value whose use can be limited to a particular device, merchant, or payment scenario. Apple's Device Account Number is the Apple Pay term merchants and customers may encounter for a device-specific value used in that wallet.

• Physical card number: identifies the underlying card account and appears on the card or within issuer-controlled account information.
• Device Account Number: is created for an approved card on a particular Apple device and is used as part of Apple Pay transaction processing.
• Dynamic security code: is generated for a specific transaction and accompanies the Device Account Number when the payment is authorized.

These terms describe different parts of the payment flow. A Device Account Number should not be treated as a duplicate physical card number, and a dynamic security code should not be treated as a reusable card verification value.

Why the last four digits may look unfamiliar

A receipt, payment report, or support screen may show the last four digits of the payment value used for a wallet transaction. Those digits can differ from the last four digits printed on the physical card because Apple Pay used the Device Account Number. Apple also lets a customer view the last four digits of the Device Account Number in Wallet card details on supported devices.

If a customer is trying to identify a purchase, do not conclude that the transaction used the wrong card merely because the visible last four digits differ from the plastic card. Compare the transaction date, amount, merchant name, wallet used, and the last four digits shown in the customer's Wallet with the information available through the business's approved payment reporting tools. Screen labels and report fields vary by provider, so staff should use the provider's current documentation when interpreting a particular field.

A practical merchant review process

1. Start with the transaction record. Locate the purchase using the date, amount, location or channel, transaction identifier, and the payment method label shown by the approved system.
2. Ask the customer to check Wallet privately. The customer can open the relevant card details on their own device and compare the displayed last four digits. Staff should not ask for screenshots containing unnecessary personal or payment information.
3. Compare non-sensitive details. Confirm the last four digits, amount, time, and merchant descriptor without requesting the full physical card number or full Device Account Number.
4. Use the correct support path. If the records still do not align, follow the payment provider's documented transaction-research process or direct the customer to the card issuer. Do not guess which credential was used.

The Device Account Number can help explain an apparent mismatch, but it does not by itself establish whether a transaction is valid, refunded, disputed, or settled. Those questions require the relevant transaction status and provider or issuer records.

Privacy-safe handling for staff

Use only the minimum information needed to locate a transaction. A general contact form, email thread, or chat is not an appropriate place to collect a full card number, Device Account Number, security code, password, bank credential, or secret API key. When support is necessary, use the business's approved payment system and the official support channel connected to that system.

Keep internal instructions focused on recognizable, non-sensitive fields such as a transaction ID, date, amount, and masked last four digits. Access to payment reports should follow the business's assigned roles. If a customer loses an Apple device, Apple directs the customer to use Find My, the Apple Account page, or the card issuer to suspend or remove the affected Apple Pay cards; merchant staff should not attempt to manage the customer's wallet.

Related digital wallet guidance

Visit the digital wallets and alternative payments FAQ hub for an overview of related topics. Learn how digital wallets work for merchants, review the plain-language guide to Apple Pay, or explore wallet tokenization. These resources explain the broader payment flow without assuming that every wallet, processor, report, or checkout uses the same terminology.