Transaction Result

Overview

This hook is activated after receipt processing and before returning to the idle screen. The transaction result is sent as an intent broadcast, informing the Third Party application receiver the outcome of the transaction.

Request Structure

Element	Type	Description	Size	Required
apiVersion	String	API version number	V20	Required
correlationId	String	Correlates a series of requests within the same flow.	V50	Required
requestDateTime	String	Date and time of the request (YYYY-MM-DDTHH:MM:SSZ). The format is based on the standard RFC 3339 internet profile — a subset of ISO 8601.	F20	Required
terminalId	String	Destination Terminal ID.	F8	Optional
action	String	"TRANSACTION_RESULTS"	V50	Required
language	String	Card Language. Provides the two letter language code according to the ISO 639-1 standard. For a complete list of language codes, visit:https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes.	F2	Required
receipt	String	Financial receipt data sent using ISO-8895-1 encoding	V4000	Conditional
status	String	HTTP Status Codes for the overall transaction request.	F3	Required
transactionType	String	Transaction that the terminal is currently performing. Valid values: "PURCHASE" "PRE_AUTHORIZATION" "PRE_AUTHORIZATION_COMPLETION" "REFUND" "INDEPENDENT_REFUND" "VOID"	-	Required

{
  "apiVersion": "2025-01-09",
  "correlationId": "example_correlationId",
  "requestDateTime": "2025-12-31T23:59:60Z",
  "merchantId": "example_merchantId",
  "terminalId": "example_terminalId",
  "action": "TRANSACTION_RESULTS",
  "language": "en",
  "status": "200",
  "transactionType": "PURCHASE"
}

Response Structure

The Third Party application doesn't have to send a response.