Skip to main content
In-app push provisioning lets a cardholder add a card to their wallet by tapping a button in your app, instead of typing card details. It converts far better than manual entry and removes the step where cardholders mistype a PAN. It is the one provisioning method that requires integration work: with the wallet provider’s SDK, and with Synctera to obtain the payload that SDK expects.
Before you build, your program needs push provisioning entitlements from Apple and Google, and must pass their UX reviews. See Program Setup.

Apple Pay

The certificates, nonce, and nonce_signature come from Apple’s SDK. The response returns encrypted_pass_data, activation_data, and ephemeral_public_key to pass back to it. See Create Digital Wallet Token for Apple Pay.

Google Wallet

The response returns push_tokenize_request_data for Google’s SDK. See Create Digital Wallet Token for Google Pay.

Next Steps

Token Lifecycle Management

What happens to the token once it exists.

Provisioning Decisions

Why a provisioning attempt is challenged or refused.