ISO 8583 to REST
How a scheme's ISO 8583 message becomes the JSON these APIs speak, field by field.
A scheme sends a 0100 authorisation request. What reaches you is JSON. This is the same message on both sides of the conversion.
The same message, both sides 6
| DE | ISO 8583 | Example | Field |
|---|---|---|---|
| 2 | Primary account number | 4111 11•• •••• 1111 | maskedCardNumber |
| 4 | Transaction amount | 000000015000 | trnAmount |
| 18 | Merchant category code | 5812 | mcc |
| 37 | Retrieval reference number | 417210004217 | rrn |
| 38 | Authorisation identification | ZH41XR | authorizationNumber |
| 49 | Transaction currency | 784 | trnCurrencyCode |
No ISO parent 2
| utid | The platform's own transaction identifier. Unique without qualification, unlike rrn, which is unique per acquirer per day and no more. |
| sourceNetwork | Which scheme the message arrived from. ISO 8583 does not carry this; it is inferred from the link the message came in on. |