get
https://api-approval.tingg.africa/v3/checkout-api/query//
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
The query status is used by the merchant if they want to query for the status of the request they raised. In this case this is a GET request where the merchant passes service_code and merchant_transaction_id as part of the query parameters
Live Endpointhttps://api.tingg.africa/v3/checkout-api/query/service_code/merchant_transaction_id
| Key | Value Type | Required | Description |
|---|---|---|---|
service_code | String | Yes | The merchant's service code. |
merchant_transaction_id | String | Yes | Unique transaction ID identifying the transaction as given by the merchant. |
Request Status Codes
| Status Code | Description |
|---|---|
| 129 | Request has expired with no partial payment received. |
| 130 | New request raised by the merchant. |
| 176 | Partial payment made for the request and has been marked as closed. Available for merchants who accept partial payments for their request |
| 178 | Full payment made for the request. |
| 179 | Request has expired with one or more partial payments made. The partial payment(s) will be reversed. |
| 180 | Request Fully paid for but acknowledged as rejected by the merchant. |
| 183 | Request fully paid for but acknowledged as accepted by the merchant. |
| 188 | The payment was received by the merchant. An accept/reject call will be initiated later by merchant. |
| 184 | This is indicates that a refund of part of the request amount has been initiated. |
| 185 | This is indicates that full refund the request amount has been initiated. |
| 186 | This is indicates that the part refund for the request was successfully processed. |
| 187 | This is indicates that the full refund for the request was successfully processed. |
| 191 | Refund Expired |
| 422 | Invalid Request |
Response Status Codes
| Status Code | Description |
|---|---|
| 200 | Success. Checkout request successfully logged in the checkout platform. |
| 500 | Failure. Generic failure occurred. Could be as a result of a system failure on the checkout platform. |
| 1001 | No request found. |
| 1007 | Missing country code. The checkout request posted was missing a country_code |
| 1013 | Not JSON. The checkout request posted was not valid JSON |
| 1014 | Missing merchant transaction id. The request did not have a merchant_transaction_id |
| 1015 | Missing checkout request id.The request did not have a checkout_request_id |
| 1017 | Invalid charge msisdn provided. The charge_msisdn provided was not valid in the country provided |
| 1027 | Invalid amount provided. The charge_amount should be between the minimum and maximum amounts provided for the payment option. |
Failed Payment Status (Work in Progress)
Kindly note on query under the failed_payments array we will respond with the exact failed status code under payment_status field of why the request failed on the MNO's end. Here the overall_status for the request will be 130 or 129 however the individual failed payment will have the correct status code with the reason for failure. Note the new field showing the actual failure reason will be under failed_payments[].payment_status
| Status Code | Description |
|---|---|
| FAILED | Generic failure reason given by the payment provider. |
| TIMEOUT | There was a timeout when MNO was sending request to end users handset or customer did not enter their pin in time. |
| INVALID_PIN | Customer entered incorrect pin. |
| BLOCKED | Customers mobile number was blocked by the MNO. |
| INSUFFICIENT_BALANCE | This indicates customer does not have enough money in their wallet to complete these transactions. |
| CANCELLED | Request was cancelled by the customer. |
| LIMIT_EXCEEDED | Declined due to limit rule: would exceed or fall below the transfer limits |
| SUCCESS | Payment was debited successfully. |
| ERROR | Internal error / network timeout when trying to reach the MNO / Authentication error when sending the request to the MNO |
| NOT_ALLOWED | Customer is not allowed to make such a transaction either due to decimals or their account is on hold or it is a suspected fraudulent transaction |
| ENGAGED | Handset has a similar request they are processing hence cannot proceed. |
| INVALID | For the request sent one of the parameters are not correct and has a problem. |
| ACCOUNT_NOT_FOUND | MSISDN or wallet is not available on the acquirers end. |