Understand decisions
Distinguish approval, decline, step-up, and completed activation.
| Outcome | Meaning | What your Notification integration does |
|---|---|---|
| Approve / green | Provisioning is allowed to proceed | Record the outcome; wait for the token lifecycle event before treating activation as complete |
| Decline / red | Provisioning is refused | Record the reason and support the cardholder as appropriate |
| Additional authentication / yellow | Cardholder verification is required | Support the selected method and follow the activation outcome |
Decision context
The enriched payload can include the decision, matched rule, matched conditions, and selected activation methods where applicable. Card-validation failures are a separate source of decline from a configurable business-rule match. The examples use decisioningReason to illustrate this context; use the interface agreed for your programme when implementing field mappings.
In Notification mode, Lume Token makes the decision. In Advice mode, the issuer returns the scheme-specific response after receiving the request and any recommendation.
Methods and scheme responses
For Mastercard provisioning, AuthorizeService and RAM arrive in parallel. Methods are returned in RAM when step-up is needed; an approve or decline has no methods. Post-tokenization e-commerce RAM is handled separately.
For Visa, Approve Provisioning supplies the provisioning decision and Retrieve Step-Up Methods supplies the methods. For Jaywan v1.2, methods are included in the provisioning response.
See activation profiles and your scheme guide.
Updated 20 days ago