Overview

The Save Card feature allows user to securely store tokenized card details for faster future transactions. The SDK securely saves card tokens in the iOS Keychain and associates them with the specific customerId

Best Practices

• User Identification: Ensure that a unique customerId is associated with each authenticated user to correctly link saved card tokens.
• Security: Leverage the iOS Keychain for local storage, ensuring that card tokens remain encrypted and secure in line with PCI requirements.
• User Consent: Always obtain explicit permission form users before saving any payment details.

User Flow

Initial Transaction

The first payment allows the cardholder to securely save their card details for future use. The saved card is linked to the customerId provided by your mobile app during the SDK initialization.

Key Points

• customerId to be unique per each app user during SDK initialization.
• The card details provided for the first payment are securely saved and stored locally within the SDK.

🚧

Important Notes on customerId

• Never Hardcode customerId: To ensure the save card functionality works properly, customerId should never be hardcoded.
• Unique per User: The customerId must be unique for every app user (e.g., generated when a new user registers in the app).
• Consistent for the Same User: Use the same customerId for a user in subsequent session. this consistency ensures saved cards are displayed properly for the correct user.

During the payment process, the SDK securely stores the card's token linked to the certain app user. To do that the user checks the checkbox "Save this card for future payments" before pressing the 'Pay' button:

Second Transaction

User can make payments using previously saved cards, which are automatically displayed by the SDK if the same customerId is used.

Key Points

Automatic Display of Saved Cards: saved cards appear in the payment UI if the customerId matches the one used during the saving process (initial transaction):

Enter the Card security code and press the 'Pay' button. The SDK will execute the payment:

Notes

• Security: payabl. iOS SDK securely stores saved card tokens locally, ensuring compliance with payment security standards.
• User Privacy: Cards saved by one customerId cannot be accessed by another customerId