Transaction Receipt
Constructors
Properties
Also known as the authorisation response code. EMV tag 8A set by the acquirer.
The custom data set in TransactionMetadata
Additional response information (from gateway or acquirer).
Application label of the card that was presented
Cardholder Verification Method
The amount of the transaction that was authorised by the acquirer. In most cases the same as amount, but can differ e.g. partial approvals.
The currency of the transaction.
Gratuity amount confirmed by the customer, in pence. Set either via TransactionMetadata.gratuityAmount or via the built-in gratuity flow when services.cabcard.toro.core.model.GratuityConfig mode is not services.cabcard.toro.core.enums.GratuityMode.NONE.
Identifier set by the initiator (merchant) to reference the transaction. The Toro SDK handles this internally and cannot be overridden by the host application.
The last 4 digits of the Primary Account Number (PAN).
The payment interface used to process the transaction. E.g. Contactless.
Identifier set by the recipient (acquirer) to reference the transaction. This can be the same as the initiatorTransactionId depending on the acquirer.
The result of the authorisation (acquirer decision). Typically APPROVED or DECLINED.
The reason for the ResponseCode.
Unique reference number to identify the transaction. Can be set in TransactionMetadata.
Cardholder signature base64 encoded if applicable.
Indicates whether the signature verification failed, either due to merchant rejection or customer cancellation during signature entry.
The serial number of the terminal the transaction was processed on.
Unique identification of the transaction assigned by the POI (Point Of Interaction)