Skip to main content

Troubleshooting

Common Pitfalls​

This section describes the MPP SDK implementation common pitfalls and their potential resolution.

Use case 1 - Incorrect App ID is configured in payment scheme TSP​

Problem behaviour description

Mobile app can't retrieve payment pass information from Apple Pay Wallet. Example use case behavior is when method canAddPaymentPassWithPAI() return true but the card is already added to the wallet.

Root cause

Wrong App ID(associatedApplicationIdentifiers) is configured in payment scheme token service provider, e.g. VTS or MDES.

Resolution

Update token service provider configuration to reflect the correct App ID(associatedApplicationIdentifiers). Change propogation may be not immediate and may take up to 8 hours.

MeaWallet development portal - Apple Pay App ID configuration in TSP

Use case 2 - App is not whitelisted with Apple​

Problem behaviour description

In-App Provisioning is abandoned with message “Card Not Added. Contact your card issuer for more information.”. Error message appears before T&C are displayed.

Root cause

Mobile App is not whitelisted for In-App(Push) Provisioning with Apple.

Resolution

Whitelist mobile app with Apple.

MeaWallet development portal - Apple Pay Entitlement(Whitelisting)

Use case 3 - Card is not whitelisted for TestFlight​

Problem behaviour description

In-App Provisioning is abandoned with message “Your Issuer Does Not Yet Offer Support for This Card. Learn more about currently supported cards or ask your issuer if they offer cards that support Apple Pay.”. Error message appears before T&C are displayed.

Root cause

Card is not whitelisted in the payment scheme token service provider configuration.

Resolution

Whitelist cards for Apple Pay TestFlight with the Token Service Provider as MDES or VTS.