Introduction

Transaction Messages provide a granular insight into the behind-the-scenes activities of the payments ecosystem and correlate with specific card network messages. When a user pays for goods or services on a linked card, Astrada captures the transaction message and sends this to you in real time. This allows you to build customized experiences that engage users at the time of the transaction.

Transaction Message Resource

Message Types

Transaction Messages are direct representations of the network messages Astrada receives. Learn more about the transaction life cycle in Home.

All AUTH messages are informational, while FINL indicates money movement. REQU signifies that there is a request and response, while ADVC does not require a response.

Astrada Message Types are based on the ISO 20022 MessageClass1Code and Function16Code.

Message Type	Description
`AUTH_REQU`	An authorization request is like asking, "Is this card able to make this transaction?". This message also contains the issuer's answer to this question - based on a check of available funds and applicable restrictions (see result: `APPROVED` or `DECLINED`). ISO 8583:2003 MTI: x100/x110 (dual message)
`AUTH_ADVC`	The authorization advice updates the authorized amount before the funds are cleared. If the authorization amount is positive, it replaces the previously authorized balance. One example of this are gas station transactions, where the initial authorization request is sent before the final amount is known and then adjusted. If the `AUTH_ADVC` amount is negative, this means that the original authorization request is being reversed or voided. This happens when a merchant cancels a purchase before the funds are cleared. ISO 8583:2003 MTI: x120, x400/x410, x420 (dual message)
`FINL_REQU`	A financial request is a one-step authorization and fund movement process that initiates money movement rather than requiring a separate financial message. It contains the issuer's decision to allow or not allow this transaction message to proceed (result: `APPROVED` or `DECLINED`). ISO 8583:2003 MTI: x200/ x210 (single message)
`FINL_ADVC`	A financial advice triggers the movement of funds after an authorization. If it follows after a `FINL_REQU`, it adjusts the amount of the financial request. A positive amount replaces the previously authorized and cleared balance. If the `FINL_ADVC` is negative, this means that the original financial request is being reversed by the merchant acquirer. ISO 8583:2003 MTI: x220 and x420 (single message)

Transaction Types

Transaction types provide additional information about the transaction, describing the effect that it had on the customer account and the type of accounts affected.

Transaction Type	Description
`DEBIT_01`	Goods and service
`DEBIT_02`	Cash (ATM)
`CREDIT_01`	Payment Transaction
`CREDIT_02`	Returns
`INQUIRY_01`	Available funds inquiry
`TRANSFER_01`	Cardholder accounts transfer
`ADMIN_01`	PIN Unblock
`ADMIN_02`	PIN Change

Webhook event types

Applicable webhook event types:

Event Type Name	Trigger	Content
transactionmessage.created	Whenever a new Transaction Message is registered in the Astrada system	A complete understanding of the created Transaction Message object

Learn more about Webhooks.