Implementation Notes

Use the following notes as final implementation reminders when integrating the Card Status Management flow.

• Use the card’s publicToken when updating or retrieving card status.
• After a status update, retrieve the latest status to confirm what should be shown to the cardholder.
• Treat status updates as lifecycle state transitions, not simple field updates.
• Where supported, use a unique IdempotencyKey header value to protect retry scenarios from duplicate processing.
• Store request and response references for troubleshooting, audit, and support purposes.
• Do not assume all status changes are reversible. Some statuses represent archived, fixed, or terminal states.