Apple Pay vs AutoFill Cards: Understanding Apple Wallet’s Dual System

Apple’s Wallet application, beyond simply storing payment cards, operates with a layered system of security and functionality that many users may not fully understand. While Apple Pay provides a method for contactless transactions, AutoFill Cards offer a separate, yet related, way to manage and utilize payment information within Safari and compatible apps. The distinction lies in how card data is stored and accessed, a complexity revealed in a deep dive by Glenn Fleishman for Six Colors.

The Dual System: Apple Pay vs. AutoFill Cards

Apple allows users to store credit and debit card information in two distinct locations: Apple Pay for point-of-sale transactions and within apps, and AutoFill Cards, specifically for automatically completing payment forms in Safari and other browsers supporting Apple’s autofill framework. This separation isn’t arbitrary. The setup for each is similar, but fundamentally different in how the information is handled.

AutoFill Cards have been a feature since at least 2013, originating with Mac OS X 10.9 Mavericks and iOS 7. Users can manually enter card details, or on iPhones and iPads, use the camera to scan card information for automatic input. Regardless of the entry method, authentication is required to view or modify stored card details, acknowledging the sensitive nature of the data.

The Secure Element: A Key Distinction

The core difference between Apple Pay and AutoFill Cards centers around the “Secure Element,” a dedicated hardware component within Apple devices. While the Secure Enclave focuses on storing and protecting security keys and private information, the Secure Element facilitates two-way communication with card issuers and payment networks.

When a card is added to Apple Pay, the actual card number is not stored by Apple. Instead, it’s passed to the Secure Element, which negotiates a secure connection with the card issuer. This process results in the creation of a device-specific card number (a Device Account Number or DAN) that is stored within the Secure Element. This DAN is unique to the device and cannot be used for traditional swipe transactions or manual entry on websites.

Apple has no access to this DAN. it’s managed entirely within the Secure Element. Only the last four digits are displayed in Wallet for user identification. Transactions made via Apple Pay, whether through NFC or within Safari, are cryptographically secured and processed directly between the device, the merchant, and the card issuer.

Why Both Systems Exist

The existence of both Apple Pay and AutoFill Cards addresses different needs. Apple Pay prioritizes security by tokenizing card numbers and enabling contactless payments. AutoFill Cards, provide convenience for online forms, particularly in situations where Apple Pay isn’t supported. Notably, AutoFill Cards can store information for cards not compatible with Apple Pay, such as some store-branded or stored-value cards.

A key distinction is that Apple Pay cards are not synchronized across devices. Each device requires individual enrollment and the creation of a unique DAN. AutoFill Cards, however, do synchronize across devices via iCloud, provided Wallet syncing is enabled in iCloud settings. This synchronization is possible because AutoFill Cards store the actual card details (protected by iCloud security and device authentication), rather than a tokenized number.

Streamlining Apple Pay Enrollment

While Apple Pay cards don’t automatically sync, Apple offers a feature to streamline the enrollment process on new devices. Wallet can identify cards previously used on other devices and prompt the user to verify ownership, simplifying the addition of cards to Apple Pay. This leverages the fact that ownership has already been established on another device.

Looking Ahead

As of February 4, 2026, Apple’s Wallet continues to evolve, with iOS 26 bringing expansions to AutoFill functionality for credit cards, making autofill easier within apps. The underlying architecture, however, remains consistent: a dual-system approach balancing security and convenience, powered by the Secure Element and iCloud synchronization. Understanding these nuances can help users maximize the benefits of Apple’s payment and identity management platform.