Card Lifecycle v1

Card Lifecycle Push is one of the modules available through debiX PUSH. This use case enables issuers to receive near real-time notifications for lifecycle events related to cards.

Currently, the events CardBlocked, CardUnblocked and CardDeleted are supported. An event is wrapped in an envelope providing metadata such as API version and payload type. A subset of the metadata is also available as JMS properties.

JSON Schema

Push Event Envelope

event-envelope.json

event-envelope.json

Payloads

Payloads are delivered as stringified JSON in the envelope. The possible types are defined below. Notes for implementation: make sure to destringify the payloads before mapping them to their respective types.

Card Status Changes

The payload specification of the events CardBlocked, CardUnblocked and CardDeleted is identical. The payloads differ in the value of the field blockInformation which is set only in the case of a CardBlocked event and null otherwise.

card-status-changed-payload.json

card-status-changed-payload.json

Other Definitions

Common Card Lifecycle Definitions

card-lifecycle-definitions.json

card-lifecycle-definitions.json

CommonDefinitions

common-definitions.json

common-definitions.json

JMS Properties

A subset of the metadata provided in the envelope, is also available as JMS Properties, mainly to facilitate event deserialization. The available JMS properties are:

• pushEventType
• pushModule
• pushModuleApiVersion
• pushTransactionId

Issuer-Side Processing

Upon receiving a message, the issuer can:

• Update card status in the backend core banking systems.

• Inform cardholder via push notification in the issuer’s own apps, i.e., mobile banking.

• Use the debiX API for follow-up actions, e.g., immediate token revocation.

Schematic Example