📘

Important

The Mobile SDK allows customers to save up to four credit cards to reuse for faster checkout experience. This functionality first must be enabled on a merchant account. Reach out our Technical Operations or Client Relationship Teams to enable Save Card for your merchant account.

The payabl. Android SDK provides functionality for saving and reusing credit card tokens. In case of Android SDK, the tokens are stored locally within the Android secure storage and are displayed based on the userId parameter. This ensures secure and seamless handling of saved cards.

---

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 userId provided by your mobile app during the SDK initialization.

Key Points

• userId 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 userId

• Never Hardcode userId: To ensure the save card functionality works properly, userId should never be hardcoded.
• Unique per User: The userId 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 userId 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 userId is used.

Key Points

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

When user selects the previously saved card as a means of payment, they will be prompted to enter CVV / CVC card code:

SDK will execute a payment with the 'Pay' button is pressed after CVV / CVC code has been provided:

Notes

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