Integrate your card scheme
Follow the Notification-mode journey for your programme.
Choose the scheme used by your card programme. Wallet journeys share the same broad steps, but each scheme uses its own request names, fields, and token identifiers.
| Scheme | Guide focus |
|---|---|
| Mastercard / MDES | Five method examples: AuthorizeService, RAM, code delivery, activation and token updates |
| Visa / VTS | Six provisioning/lifecycle method examples plus existing-token device binding |
| Jaywan | v1.2 examples: provisioning with methods, OTP delivery and primary/auxiliary lifecycle context |
| MADA programme planning | Confirm the integration and wallet scope with the implementations team |
All Lume Token Notification integrations use the same message envelope. SUMMARY exposes common values; ADDITIONAL_MESSAGE_DATA retains the eligible native fields and service results. Do not copy one scheme's field paths into another scheme's parser or rules.
The examples use synthetic values and selected fields. They explain the payload structure rather than define a complete endpoint schema. Apply the scheme/interface version agreed for your programme.
For a method-by-method example index, see scheme requests and issuer events or the notification-to-method matrix. Each example shows the common envelope and its scheme-specific additional data.
Updated 20 days ago