post
https://api.aeronpay.in/api/serviceapi-prod/api/reports/transactionStatus
Check the current status of a transaction using the client reference ID, registered mobile number, and transaction date.
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
Use this endpoint to check the current status of a transaction using the client reference ID, registered mobile number, and transaction date.
Send a status enquiry only after 15 minutes if the original transaction is in PENDING or TIMEOUT (no response) status. For the same
client_referenceId, keep at least 2 hours between status checks.
Before you call this endpoint
- Add the
client-idheader with your unique client ID. - Add the
client-secretheader with your unique client secret. - Set the
content-Typeheader toapplication/json. - Use the same
client_referenceIdthat you sent in the original transaction request. - Send the registered mobile number of your partner API account in
mobile. - Send
date_of_transactioninDD-MM-YYYYformat.
1. Request headers
| Header | Type | Required | Description |
|---|---|---|---|
client-id | string | Yes | Unique client ID |
client-secret | string | Yes | Unique client secret |
content-Type | string | Yes | Content type. Default: application/json |
2. Request body
| Field | Type | Required | Description |
|---|---|---|---|
client_referenceId | string | Yes | Transaction ID used in the original API call for the service transaction |
mobile | string | Yes | Registered mobile number of the partner API account |
date_of_transaction | string | Yes | Date of the transaction in DD-MM-YYYY format |
Example request body
{
"client_referenceId": "ABC123456",
"mobile": "9876543210",
"date_of_transaction": "31-03-2026"
}Date format
- Use
DD-MM-YYYY - Example:
31-03-2026
3. Response status guide
| HTTP status | status value | What it means | Action (Yes or No) | Description |
|---|---|---|---|---|
200 | SUCCESS | The transaction completed successfully | Yes | This is the actual response of the Transaction |
201 | PENDING | The transaction is still pending | Yes | This is the actual response of the Transaction |
202 | ACCEPTED | The transaction was submitted to the bank and final confirmation is still pending | Yes | This is the actual response of the Transaction |
400 | FAILED | The transaction failed | Yes | This is the actual response of the Transaction |
404 | FAILED | The transaction was not found for the supplied client_referenceId | No | Do not Action. Recheck the Transaction Manually or Reconcile. |
429 | TOO_MANY_REQUESTS | The same client_referenceId was checked too many times | No | Do not Action. Prevent the Request of the Same Transaction. |
444 | FAILED | The system could not confirm the exact transaction status at this time | No | Do not act. Wait some time and recall. |
4. Response fields
| Field | Type | Description |
|---|---|---|
status | string | Transaction status returned by AeronPay |
statusCode | string | Transaction action code |
transactionId | string | AeronPay transaction ID |
enquiryTxnId | string | Unique enquiry transaction ID returned on every status API call |
client_referenceId | string | Partner reference ID |
acknowledged | string | "1" for success and "0" for pending and failed responses |
amount | integer | Transaction amount returned in the response |
utr | string or null | Bank UTR or reference number |
description | string | Human-readable transaction result |
message | string | Additional error detail for some non-success responses |
5. Example responses
Success response (200)
200){
"status": "SUCCESS",
"statusCode": "200",
"transactionId": "ARNPY17401487807871",
"enquiryTxnId": "ENQTXN921561740171536",
"client_referenceId": "327746288562",
"acknowledged": "1",
"amount": 1030,
"utr": "{{UTR}}",
"description": "Transaction Successful"
}Pending response (201)
201){
"status": "PENDING",
"statusCode": "201",
"transactionId": "ARNPY17401565698026",
"enquiryTxnId": "ENQTXN738461740171603",
"client_referenceId": "38486284628",
"acknowledged": "0",
"amount": 40000,
"utr": null,
"description": "Transaction Pending"
}Accepted response (202)
202){
"status": "ACCEPTED",
"statusCode": "202",
"transactionId": "ARNPY17401487807871",
"enquiryTxnId": "ENQTXN921561740171536",
"client_referenceId": "345542253",
"acknowledged": "1",
"amount": 1030,
"utr": "{{UTR}}",
"description": "Transaction is Submitted to the Bank. Awaiting the Final Confirmation."
}Failed response (400)
400){
"status": "FAILED",
"statusCode": "400",
"transactionId": "ARNPY17401375895794",
"enquiryTxnId": "ENQTXN842701740171662",
"client_referenceId": "28846285627",
"acknowledged": "0",
"amount": 13000,
"utr": null,
"description": "Transaction Failed",
"message": "Final Status - Failed from the Partner Bank or Operator"
}Not found response (404)
404){
"status": "FAILED",
"statusCode": "404",
"description": "Transaction not found",
"message": "Invalid Client Reference ID"
}Rate limit response (429)
429){
"status": "TOO_MANY_REQUESTS",
"description": "This client_referenceId was already checked multiple times. Try again in 57 seconds."
}Temporary enquiry issue (444)
444){
"status": "FAILED",
"statusCode": "444",
"message": "Unable to Check the Exact transaction at this time.",
"transactionId": "ARNPY17401375895794",
"enquiryTxnId": "ENQTXN842701740171662",
"client_referenceId": "28846285627",
"acknowledged": "0"
}Optional: Troubleshooting
- If you receive
404, verify thatclient_referenceIdmatches the value used in the original transaction request. - If you receive
429, wait for the retry interval in the response message before checking the same transaction again. - If you receive
444, try again later instead of treating the transaction as final. - If the transaction is still
PENDINGorACCEPTED, wait before checking again to avoid unnecessary retries.