Monitor tokenization outcomes

Your notification feed provides the event record for your integration. Use the common summary to locate activity, then inspect the native scheme payload and enabled-service results for the detail behind it.

Keep the right context

• The message identifier and event time.
• The Paymentology card reference, scheme, wallet, and token requestor where available.
• The scheme's token reference and correlation identifiers.
• The provisioning decision and any decisioning reason or risk-service results supplied.
• The resulting lifecycle event and your processing outcome.

SUMMARY.Token_Status is the Paymentology card status. It is not the lifecycle state of an individual network token. Read the scheme token-state fields and lifecycle reason for that distinction.

Investigate a case

1. Find the card and relevant network token.
2. Locate the provisioning or authentication request and associated notifications.
3. Check whether the result came from card validation, a matching rule, or the default fallback.
4. Review the selected activation methods and subsequent completion event where step-up was required.
5. Share the message/correlation identifiers and observed behavior with the implementations team when investigation is needed.

Tune your configuration

Review approval, decline, and step-up outcomes for your own scheme and requestors. Ask the implementations team to adjust a specific rule when evidence supports the change. Test it against both the intended scenario and the default fallback before applying it to your programme.

See notification fields and building rules.