A list containing labels that can be used to discover this transaction or group it with other transactions sharing labels with the same label name and value. Transaction labels should never be used to make transaction processing decisions.

The randomly generated UUID identifying this transaction, as defined for a variant 4 UUID in RFC 4122

The date and time of the message as recorded by the sender. The format shall be as defined for date-time in RFC 3339 section 5.6. It is recommended that the optional time-secfrac be included up to millisecond precision

The Originator object encapsulates data relating to the originator of the transaction

Originating, acquiring, processing, or receiving institution details

Originating, acquiring, processing, or receiving institution details

Originating, acquiring, processing, or receiving institution details

An array of identifiers which each identify the transaction within each entity's system.

Data that may be printed on the customer slip for information purposes

Used to group multiple transactions which would otherwise be considered independent.

Data relating to the type of transaction taking place (i.e. cash withdrawal, goods and services etc.).

This specifies the type of source account being used in the transaction (i.e. cheque, savings).

This specifies the type of destination account being used in the transaction (i.e. cheque, savings).

The System Trace Audit Number can be used to locate transactions across different systems.

This is a reference set by the original source of the transaction.

A PIN required to authorise a transaction. EncryptionParameters should be provided where the service will be performing operations on the encrypted PIN, such as PIN translation. Only the PIN block need be provided where the service is expected to forward it to a third party, where the calling client and said third party have agreed upon encryption parameters beforehand.

Reference used by the recipient to redeem the order. This must be printed on the receipt.

Reference used by the service provider to uniquely identify the money transfer order on their system. This field can be used if the provider supplies a supplementary reference for the order in addition to the orderRedeemRef. Note that any reference issued by the provider that is specific to a particular leg of the order process should be set as a ThirdPartyIdentifier (i.e. the authorization and redeem legs of the order should each have its own reference).

Uniquely identifies customer's profile on the upstream entity's system.