OOB CallBack Validate Status Response Examples
This table provides examples for the possible responses to the OOB CallBack Validate Status API request.
OOB CallBack Validate Request API Reference: Interactive request/response specification
| Status | Response Code | RDX Response | Retry | Retry Count |
|---|---|---|---|---|
| Success | 200 | { "OrgUnitId": "660a54f6013f968261037f69", "TransactionId": "e86b1488-982c-4712-ae3c-21b666e75518", "ErrorDetails": "null", "Status": "Success" } | NA | NA |
| Failure | 400 | { "OrgUnitId": "660a54f6013f968261037f69", "TransactionId": "e86b1488-982c-4712-ae3c-21b666e75518", "ErrorDetails": { "ErrorCode": 400, "ErrorDescription": "Bad Request" }, "Status": "Failure" } | No | NA |
| Failure | 401 | { "OrgUnitId": "770a54f6013f968261037f69", "TransactionId": "e86b1488-982c-4712-ae3c-21b666e75518", "ErrorDetails": { "ErrorCode": 401, "ErrorDescription": "Unauthorized Transaction" }, "Status": "Failure" } | Yes | 3 max. |
| Failure | 404 | { "OrgUnitId": "660a54f6013f968261037f69", "TransactionId": "e86b1488-982c-4712-ae3c-21b666e75518", "ErrorDetails": { "ErrorCode": 404, "ErrorDescription": "Transaction Not Found" }, "Status": "Failure" | No | NA |
| Failure | 410 | { "OrgUnitId": "660a54f6013f968261037f69", "TransactionId": "e86b1488-982c-4712-ae3c-21b666e75518", "ErrorDetails": { "ErrorCode": 410, "ErrorDescription": "Transaction processing already completed" }, "Status": "Failure" | No | NA |
| Failure | 500 | { "OrgUnitId": "660a54f6013f968261037f69", "TransactionId": "e86b1488-982c-4712-ae3c-21b666e75518", "ErrorDetails": { "ErrorCode": 500, "ErrorDescription": "Internal Server Error" }, "Status": "Failure" | No | NA |
Note: Responses 400, 401, and 404 allow for authentication status retry before authentication times out (typically 10 minutes). If the cardholder closes the session prior to this timeout, the retry will not execute.
Updated 12 days ago
Did this page help you?