Do not block card creation Enrollment may be handled after card creation and should not block the card creation process. Use a queue, retry process, and status tracking to complete enrollment after the card is created, activated, or made eligible.

Keep data synchronized Your system is responsible for keeping Click to Pay data synchronized with cardholder and card lifecycle changes. This includes consumer profile updates, payment instrument updates, card replacements, card closures, and opt-out requests.

Use the API Explorer as source of truth This guide explains the implementation responsibilities and required lifecycle behavior. Use the API Explorer for exact endpoint paths, required fields, schemas, and request/response examples.

Maintain evidence Payblr may request enrollment evidence, exception reports, and remediation status for applicable Visa consumer card programs.