transactionReference that was sent with it. Use it after a timeout or an error response to find out what happened. It only reads: it never sends or finishes a transfer.GET /transfer/intrabank-universal/{transactionReference}| Field Name | Type | Required | Description |
|---|---|---|---|
| transactionReference | string | TRUE | The reference that was sent with the transfer |
POST /transfer/intrabank-universal), as it stands now. The status is always 200 when the transfer is found: read outcome.| outcome | Meaning | What to do |
|---|---|---|
| Credited | The source was debited and the destination credited | Nothing |
| Pending | Not finished. code says where it stands. RECEIVED means it was received but has no answer yet | Send the same transfer request again to finish it. Do not use a new reference |
| Refused | Refused before any money moved | The customer is not out of pocket. For a new instruction use a new reference |
| Reversed | The source was debited, the destination refused the credit, and the debit was returned | The customer has their money. For a new instruction use a new reference |
POST /core/transfer/intrabank-universal is read with GET /core/transfer/intrabank-universal/{transactionReference}. A reference that does not exist, that another client sent, that was sent on the core route, or that was sent before this call existed answers 404.