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

Attributes

Field name	Required/ Optional	Description	Type
`id`	required	The unique identifier of the transaction message	string `uuid` format
`acceptor.id`	optional	The merchant’s card acceptor id as assigned by the acquirer/processor	string
`acceptor.acquirerId`	optional	Acquiring Institution Identification Code. Identifies the acquirer (for example, merchant bank) or its agent	string
`acceptor.city`	optional	The acceptor city. This is defined by the acquirer/ processor but may not always be reliable.	string
`acceptor.country`	optional	The acceptor country	string ISO 3166 format, alpha3
`acceptor.mcc`	optional	The merchant category code (MCC) provided by the acquirer/ processor. It is used to classify businesses by the types of goods provided or services rendered	string
`acceptor.name`	optional	The acceptor (merchant) name	string
`acceptor.state`	optional	The acceptor state (e.g. New York) if available. This is defined by the acquirer/ processor but may be unreliable.	string
`approvalCode`	optional	Unique code that authorizes a transaction message, sent by the issuer/the issuer processor on the issuer's behalf when approving it	string
`cardId`	required	The card identifier used by Astrada	string `uuid` format
`cardholderBillingAmount`	required	The amount in the currency of the country of issuance, converted from the original purchase currency. The `transactionAmount` and `cardholderBillingAmount` values may differ in case of international transactions.	number
`cardholderBillingCurrency`	required	The currency of the country of issuance	string ISO 4217 format, alpha3
`createdDateTime`	required	The timestamp of when the transaction message object was created in the Astrada system (UTC)	string ISO 8601 format, `YYYY-MM-DDThh:mm:ss.sssZ`
`dateTime`	required	The timestamp of the transaction message (e.g. authorization, movement of funds, etc) in either UTC or local time zone of the merchant/ acquirer. Note: We are not always able to provide a dateTime in UTC as this is not available at all sources. We are unable to provide the timezone. We may provide it in the future should it become available.	string ISO 8601 format, `YYYY-MM-DDThh:mm:ss`/ `YYYY-MM-DDThh:mm:ss.sssZ`
`messageType`	required	The message type is a direct representation of the network messages Astrada receives. Learn more about Message Types.	string enum: `AUTH_REQU`, `AUTH_ADVC`, `FINL_REQU`, `FINL_ADVC`, `CBCK_ADVC`
`network`	required	The card network on which the message occurred	string enum: `VISA`, `MASTERCARD`, `UNKNOWN`
`result`	required	The issuer’s decision on whether the transaction message was approved or declined	string enum: `APPROVED`, `DECLINED`
`subaccountId`	required	The Astrada Subaccount identifier	string `uuid` format
`transactionAmount`	required	The amount of the transaction message in the currency it was charged in. In the case of international transactions, the `transactionAmount` and `cardholderBillingAmount` may differ due to being in different currencies.	number
`transactionCurrency`	required	The currency in which the transaction took place	string ISO 4217 format, alpha3
`transactionReference`	required	`TransactionReference`: Identification of the transaction that has to be unique for a time period.	string
`transactionType`	optional	Types provide additional information about the transaction message, describing the effect that it had on the customer account and the type of accounts affected. Learn more about Transaction Types	string enum: Types
`transmissionDateTime`	optional	The timestamp of when the transaction message object was received by the data source (i.e. Mastercard or Visa) in UTC	string ISO 8601 format, `YYYY-MM-DDThh:mm:ss.sssZ`

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.