In‑App Provisioning Extension provides the cardholder with more ways to add a payment card to Apple Pay through the issuer’s iOS app — from Apple Wallet or within the Apple Pay payment sheet.

By leveraging the issuer’s iOS app, In‑App Provisioning Extension allows issuers to offer easier provisioning, strengthen fraud protection, and encourage top‑of‑wallet consideration through prominent placements across Apple Wallet and the Apple Pay payment sheet.

Yes. Refer to the Issuer Functional Requirements (IFR) for details.

A cardholder has to open and log in to the issuer app on their iPhone at least once for Apple Wallet to detect the In‑App Provisioning Extension integration.

Yes, issuers need to implement In‑App Provisioning before implementing the In‑App Provisioning Extension feature.

Cardholders can add a card to Apple Pay via the In‑App Provisioning Extension feature in two ways: from within Apple Wallet, or within the Apple Pay payment sheet during the in‑app checkout process.

From Apple Wallet:

1. A cardholder taps Add Card (+) in the top right corner of Apple Wallet.
2. The next screen displayed in Apple Wallet will include a From Apps on Your iPhone section. Issuer apps that have implemented the In‑App Provisioning Extension feature will appear in a list under the From Apps on Your iPhone section, as long as the issuer app has at least one available payment card that is not currently in Apple Wallet.
3. A cardholder can then tap on a listed issuer app to begin the provisioning experience. The extension will return the cardholder to Apple Wallet automatically once the provisioning process is complete.

During checkout: Cardholders tap the Apple Pay button, choose Select Payment Method, and then select from the list of enabled issuer apps to add a card to Apple Pay.

Cardholder devices must be running the following software in order to add a card using the In‑App Provisioning Extension feature:

• From Apple Wallet: iOS 14 or later
• From the Apple Pay payment sheet: iOS 26.0+, iPadOS 26.0+, Mac Catalyst 26.0+, or visionOS 26.0+ or later

No. All cards and payment networks are supported by the In‑App Provisioning and the In‑App Provisioning Extension features.

Yes. Issuers can choose from various verification methods (such as email, SMS, or call center support) to validate card ownership by the cardholders. This validation happens before issuers approve a card provisioning request. Learn more about Card Verification Methods here.

Data used during the provisioning flow — card art, the last four digits of the card number, and the card name — is not shared with Apple. It is passed directly to Apple Wallet for display purposes only and does not leave the device. Issuer-controlled verification and Apple Pay security measures, including end-to-end encryption, provide additional protection throughout the process.

Yes. Issuers can enhance the provisioning experience by enabling Multi-Device Provisioning, which allows cardholders to easily add their cards to all applicable devices logged in with the same Apple Account.

In‑App Provisioning Extension works with issuer‑supported payment reward cards (for example, a credit card linked to an airline for accruing miles), but not with general loyalty program cards (such as a grocery store rewards card).

Issuers should test In‑App Provisioning Extension by writing unit tests in Xcode and releasing beta builds of an iOS issuer app to TestFlight. Review the testing guidance for more information.

The integration length of In‑App Provisioning Extension will depend on the issuer’s development resources and skill set to manage Apple Wallet code. The issuer must also have access to the existing mobile banking app code base and have ability to test the app. In‑App Provisioning Extension by nature is a rebuild of the existing app to include the app extension. The new app must be installed and the user must login at least once to invoke the extension.

First implement In‑App Provisioning. Next, review In‑App Provisioning Extension documentation, add app extensions targets, develop UI extension, implement card eligibility logic, and update PNO metadata. Finally, test and certify. For more details, refer to the steps in Enable In‑App Provisioning Extension (above).

Issuers who have already implemented In‑App Provisioning successfully do not need to request additional entitlements for the In‑App Provisioning Extension feature.

The In‑App Provisioning Extension update, released with iOS 26, allows the Apple Pay payment sheet within a merchant app to automatically detect an issuer app on a cardholder’s device for direct card provisioning to Apple Pay — without the need to leave the shopping experience.

No, a cardholder doesn’t need to take additional steps to add a card through In‑App Provisioning Extension within the Apple Pay payment sheet. If a compatible issuer app is detected on their device, the extension will prompt them to add their card directly to Apple Pay without leaving the Apple Pay payment sheet.

Yes, cardholders will have control over which cards are added to Apple Pay, with prompts ensuring they consent to the setup of each card.

A cardholder can choose which card to add from any of the detected issuer apps. Prompts will guide the cardholder through this process.

Yes. Cardholders can select multiple cards from a specific issuer to add to Apple Pay. Each card will be provisioned in sequence.

Depending on iOS version and regional availability, a cardholder may be offered the ability to add a card to other devices where the card is not yet added.

A cardholder must open and log in to the issuer app on their iPhone at least once for Apple Wallet to detect the In‑App Provisioning Extension integration. Also check the PNO metadata and the identifiers of the extensions.