Skip to main content
WeavrApple Pay

Apple Pay, certified on Weavr.

Lab-tested push provisioning, the architecture choices Apple recognizes, and the support you need to launch your card on iPhone.

Start with the primary mobile app guide

Apple Pay compliance overview

Before you can launch an app that adds cards to Apple Pay, Apple must certify your integration. The certification process verifies that your app meets Apple's functional, security, and user-experience requirements for issuer appsIssuer app Apple's term for the mobile app that authenticates a cardholder and provisions their card to Apple Wallet. Apple's certification, brand, and Card Lifecycle Management requirements apply specifically to this app. In a primary + companion architecture, your primary app remains the issuer app even if the provisioning step happens in a companion app..

This section guides you through the choices and requirements involved, so you and our team can plan the most efficient route to launch.

Why certification matters​

Apple Pay is a regulated environment. Card issuers and their embeddersEmbedder A company or developer that integrates Weavr's embedded finance services into their own application to provide financial services to their end customers. must demonstrate that:

  • Cards are added to Apple Wallet only by the legitimate cardholder.
  • The cardholder authentication is strong enough to prevent unauthorized provisioning.
  • The app provides the lifecycle controls Apple requires (for example, lock, unlock, replace, view PIN).
  • The user experience matches Apple's brand and interaction guidelines.

Failing to meet these requirements means Apple rejects the integration during lab certificationLab certification The formal test pass run by an Apple-affiliated test centre that verifies an issuer app meets Apple Pay's functional, security, and brand requirements. The test exercises every Card Lifecycle Management operation, the in-app provisioning flow, and the Wallet Extension. A successful pass is required before launching Apple Pay on a card programme; most first-time integrations fail at least one item and need a remediation round., which delays launch.

How our SDK fits in​

Our Push ProvisioningPush Provisioning A method that allows cardholders to add their card to a digital wallet (such as Apple Pay or Google Pay) directly from your app. The card details are securely tokenized and sent to the wallet provider, streamlining the process and enhancing the user experience compared to manual provisioning. This feature is currently in beta. SDK — available for both iOS native and React Native — handles the technical part of adding a card to Apple Wallet. It does not, on its own, satisfy Apple's certification requirements — those depend on how the SDK is integrated, which app it lives in, and what surrounding controls (authentication, card lifecycle managementCard Lifecycle Management The set of in-app card operations Apple and Mastercard expect an issuer app to surface so cardholders can self-serve without leaving the app. Typical operations: view card number / CVV / PIN, lock and unlock, freeze and unfreeze, replace, report lost or stolen, view balance, and view transactions. Issuer apps that omit any of these are flagged at lab certification., deep links) are in place.

The pages in this section describe the app architecture options Apple recognizes, and what each one demands of you as an embedderEmbedder A company or developer that integrates Weavr's embedded finance services into their own application to provide financial services to their end customers.. The architecture and certification requirements are the same whether you build a native iOS app or a React Native app — only the SDK integration steps differ.

Certification paths​

Apple recognizes several app architectures for issuer integrations. The right one for you depends on what you already operate, what you are willing to build, and how your end-users access your service.

As of Q1 2026, the primary mobile app path is the route we recommend and the only one we have a fully supported solution for.

  • Primary mobile app — recommended. Your existing app handles authentication, card lifecycle managementCard Lifecycle Management The set of in-app card operations Apple and Mastercard expect an issuer app to surface so cardholders can self-serve without leaving the app. Typical operations: view card number / CVV / PIN, lock and unlock, freeze and unfreeze, replace, report lost or stolen, view balance, and view transactions. Issuer apps that omit any of these are flagged at lab certification., and in-app provisioningIn-app provisioning The flow that adds a card to a digital wallet (Apple Pay, Google Pay) from inside an issuer's mobile app, using the issuer's own authentication. In Weavr's stack, in-app provisioning is implemented via our Push Provisioning SDK on iOS or React Native. to Apple Wallet.
  • Primary + companion mobile app — fallback for embeddersEmbedder A company or developer that integrates Weavr's embedded finance services into their own application to provide financial services to their end customers. that prefer to keep development on their primary app to a minimum. Our companion app handles in-app provisioningIn-app provisioning The flow that adds a card to a digital wallet (Apple Pay, Google Pay) from inside an issuer's mobile app, using the issuer's own authentication. In Weavr's stack, in-app provisioning is implemented via our Push Provisioning SDK on iOS or React Native., deep-linked from your primary app.

See Certification paths for a side-by-side comparison.

note

Other architectures (web-initiated provisioning) are not yet documented here. Contact our support team if you are considering an alternative route.

How our team supports you​

The Weavr support team works with you throughout certification:

  • Mapping your product to the right certification path.
  • Providing the technical artifacts Apple requires (allow-listing, BIN ranges, configuration files).
  • Reviewing your app against the requirements before you submit.
  • Coordinating the lab certificationLab certification The formal test pass run by an Apple-affiliated test centre that verifies an issuer app meets Apple Pay's functional, security, and brand requirements. The test exercises every Card Lifecycle Management operation, the in-app provisioning flow, and the Wallet Extension. A successful pass is required before launching Apple Pay on a card programme; most first-time integrations fail at least one item and need a remediation round. appointment with the Apple-affiliated test centre.

Reach us at [email protected] to start the conversation early — certification timelines depend heavily on Apple's queue.

Next steps​

  1. Read the Primary mobile app guide if you can integrate Apple Pay directly into your app — this is the route we recommend.
  2. If a single-app integration is not feasible, see Primary + companion mobile app instead.
  3. Engage our support team to schedule lab certificationLab certification The formal test pass run by an Apple-affiliated test centre that verifies an issuer app meets Apple Pay's functional, security, and brand requirements. The test exercises every Card Lifecycle Management operation, the in-app provisioning flow, and the Wallet Extension. A successful pass is required before launching Apple Pay on a card programme; most first-time integrations fail at least one item and need a remediation round..