Welcome to our new developer portal! Use the "Ask" button to chat with our AI Agent.
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Replenish payment keys

Overview

Visa uses Limited Use Key (LUK) credentials that remain valid for a limited period, such as 10 days or 1 month.

If a LUK expires before any payment, the D1 SDK cannot replenish it without end user authentication. The LUK value is protected in the Android Keystore. Visa also requires the previous LUK data during replenishment to authorize retrieval of new credentials.

Mastercard uses Single Use Key (SUK) credentials for each transaction. Replenish SUK credentials when the remaining number is low.

Although this scenario is rare, the issuer application must handle it for end users who rarely open the application. Implement this check during issuer application startup, after the D1 SDK is initialized and before displaying the digital card list.

Flow

Replenishment with push notification

Push notifications are data messages handled silently by the issuer application. When the issuer application receives a push notification, it must forward it to the D1 SDK.

The D1 SDK processes the message and returns the message type PushResponseKey.TYPE_REPLENISHMENT and the related cardId when no error occurs. This indicates that the card requires replenishment.

The issuer application should then call the replenish API with isForced set to true.

See Message Handling.

Digital card list

D1PayDigitalCard provides the isReplenishmentNeeded() flag to indicate whether the issuer application must call the replenish API. If this method returns true, call replenish with isForced set to false.

See Digital card list.

SDK

This example shows how to trigger replenishment.

Last updated

Was this helpful?