Replenish payment keys
Overview
Payment keys are required to compute EMV cryptograms for contactless payments.
In a Host Card Emulation (HCE) model, payment keys are temporary. Replenish them before they run out to avoid payment interruptions.
This guide covers when to replenish and how to trigger it.
Prerequisites
Configure replenishment thresholds (onboarding)
Configure replenishment thresholds during onboarding with the Thales delivery team.
SDK Integration
Detect when replenishment is required
Use one (or both) of these signals:
Proactive check: read
DigitalCard.PaymentKeyInfo.needsReplenishment.Reactive push (TSP-triggered): process
MG:ReplenishmentNeededNotificationpush notifications from the TSP.
For push delivery and routing, see Handle push notifications.
Proactive check
Check regularly for each digital card, for example after each payment or at app startup.
Perform this proactive check:
After NFC Wallet SDK initialization.
After a payment.
When the card is set as default.
After connectivity returns (offline → online).
Trigger replenishment
Call ReplenishmentService.replenish(digitalCardID:) when you decide to replenish.
After you submit the replenishment request, the NFC Wallet backend sends a push notification. Your application processes it and the SDK retrieves the new payment keys.
Last updated
Was this helpful?