Implementation Flow
-
Client creates or activates a card.
Your system creates the card for the cardholder.
-
Client submits enrollment data.
Your system submits cardholder and payment instrument data through the Click to Pay enrollment API flow.
-
Client stores the enrollment result.
Your system stores the enrollment result, request reference, payment instrument reference, status, last attempt date, and error reason where applicable.
-
Client retries or investigates failed enrollments.
Failed, rejected, or pending enrollment records must be tracked and remediated through a controlled retry or exception process.
-
Client keeps Click to Pay data synchronized.
Your system updates consumer information and payment instrument information when cardholder data, card data, or lifecycle status changes.
-
Client deletes or disables Click to Pay data when required.
Your system processes payment instrument deletion, consumer deletion, or opt-out flows when applicable.
Implementation note
Enrollment should not block card creation. If enrollment cannot be completed immediately, your system should queue the enrollment attempt, track the status, and complete the process once the card becomes eligible.