Identify cards without receiving PAN data
Use the card reference supplied by Lume Token in issuer-facing messages.
Card Gateway protects issuer-facing messages by replacing sensitive card data with a card reference. This lets your backend associate tokenization events with a funding card without consuming its raw PAN or CVV in those messages.
What you receive
The protected payload contains a card reference together with eligible native scheme fields and enabled-service enrichment. Removing sensitive card data does not remove the wallet, device, requestor, or decision context that is eligible for delivery.
SUMMARY.Token is the Paymentology card token in the common notification envelope. Scheme identifiers, such as a token reference or funding-account reference, remain separate fields in ADDITIONAL_MESSAGE_DATA.
Agree the reference mapping and your interface fields during implementation. The scheme examples illustrate the payload shape using synthetic identifiers.
Sensitive-data integrations
Card-data protection is the standard issuer integration. If you need to receive and validate sensitive card data in Advice mode, agree that scope and the required arrangements with Paymentology. Receiving a protected tokenization message does not by itself determine the PCI scope of your other systems.
Updated 20 days ago