Skip to main content

Authorization v1

Authorization Push is one of the modules available through debiX PUSH. This use case enables issuers to receive near real-time notifications for new authorizations.

Currently, the events AuthorizationFulfilled and AuthorizationRejected 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.

Authorizations​

The payload specification of the events AuthorizationFulfilled and AutorizationRejected is identical. The payloads differ in the authorizationState values and the JMS Property pushEventType which enables easier triage on the issuer’s side.

authorization-payload.json

authorization-payload.json

Other Definitions​

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:

  • Store the authorization in the backend core banking systems and use the authorization in own work flows.

  • 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​

mqoverview.png