Clients must have a controlled process to enroll eligible cards after card creation, card activation, or e-commerce enablement. Enrollment must also be connected to lifecycle events so Click to Pay data remains accurate after cardholder or card changes.
| Trigger | Expected client action |
|---|---|
| New eligible card created | Submit enrollment or queue enrollment. |
| Card activated | Enroll if not already enrolled. |
| E-commerce enabled | Enroll if the card becomes eligible. |
| Cardholder data updated | Update consumer information. |
| Card reissued/replaced | Update the existing payment instrument or enroll the replacement payment instrument. |
| Card suspended or restricted | Evaluate whether the payment instrument must be updated or disabled. |
| Card closed/terminated | Delete or disable the payment instrument as applicable. |
| Cardholder opts out | Delete consumer and/or payment instrument data as applicable. |
| Rule | Required value / condition |
|---|---|
| Scheme | Visa |
| Product type | Consumer |
| E-commerce capability | Enabled |
| Card status | Active or eligible for activation, depending on the approved enrollment flow. |
| Card type | Physical or reusable virtual. |
| Excluded card type | Single-use virtual cards. |
| Reloadable status | Reloadable, if prepaid. |
| Program setup | Click to Pay enabled for the applicable program, BIN, and product. |
| Cardholder status | Cardholder has not opted out. |
| Required data | Name, email and/or phone, payment instrument data, billing data, and any other required enrollment fields. |