Transaction status codes indicate the current processing state or final outcome of a financial transaction initiated through Astragate APIs.
These statuses are returned when:
- initiating transactions
- checking transaction status
- receiving transaction callbacks
Transaction Lifecycle
Transactions may transition through multiple states during processing.
Typical flow:
Created
↓
Processing
↓
Pending
↓
Successful / Failed / Reversed / Timeout / Cancelled
Status Codes Reference
Created Transaction
Status Code
4000
Description
The transaction has been successfully received by Astragate and queued for processing.
Example Response
{
"success": true,
"statusCode": 200,
"message": "success",
"data": {
"id": 895,
"statusCode": 4000,
"statusDescription": "Created Transaction",
"...": "...",
}
}Integration Notes
- Initial transaction state
- Indicates Astragate accepted the request
- Does not indicate completion of transaction processing
Pending Transaction
Status Code
4001
Description
The transaction is awaiting customer confirmation or provider processing completion.
Example Response
{
"success": true,
"statusCode": 200,
"message": "success",
"data": {
"id": 895,
"statusCode": 4001,
"statusDescription": "Pending Transaction",
"...": "...",
}
}Integration Notes
- Do not treat pending transactions as failed
Callback Not Received
Status Code
4003
Description
Astragate has not yet received the provider callback confirming the transaction outcome.
Example Response
{
"success": true,
"statusCode": 200,
"message": "success",
"data": {
"statusCode": 4003,
"statusDescription": "Callback Not Received",
"...": "...",
}
}Integration Notes
- Temporary transaction state
- Retry transaction status checks after a short delay
Cancelled Transaction
Status Code
4005
Description
The transaction was cancelled before completion.
Example Response
{
"success": true,
"statusCode": 200,
"message": "success",
"data": {
"statusCode": 4005,
"statusDescription": "Cancelled Transaction",
"...": "...",
}
}Transaction Timeout
Status Code
4007
Description
The transaction exceeded the allowed processing window without receiving a final response.
Example Response
{
"success": true,
"statusCode": 200,
"message": "success",
"data": {
"statusCode": 4007,
"statusDescription": "Transaction Timeout",
"...": "...",
}
}Processing Transaction
Status Code
4008
Description
The transaction is actively being processed.
Example Response
{
"success": true,
"statusCode": 200,
"message": "success",
"data": {
"statusCode": 4008,
"statusDescription": "Processing Transaction",
"...": "...",
}
}Integration Notes
- Intermediate processing state
- Final transaction outcome not yet available
Failed Transaction
Status Code
4011
Description
The transaction could not be completed successfully.
Example Response
{
"success": true,
"statusCode": 200,
"message": "success",
"data": {
"statusCode": 4011,
"statusDescription": "Failed Transaction",
"paymentProcessorResponseMessage": "Transaction failed",
"...": "...",
}
}Integration Notes
- Failure may originate from provider, network, or validation issues
- Inspect provider response details where available
Reversed Transaction
Status Code
4220
Description
The transaction was reversed after initial processing.
Example Response
{
"success": true,
"statusCode": 200,
"message": "success",
"data": {
"statusCode": 4220,
"statusDescription": "Reversed Transaction",
"...": "...",
}
}Insufficient Balance
Status Code
4230
Description
The initiating wallet or account has insufficient funds to complete the transaction.
Example Response
{
"success": true,
"statusCode": 200,
"message": "success",
"data": {
"statusCode": 4230,
"statusDescription": "Insufficient Balance",
"...": "...",
}
}Integration Notes
- Transaction was not processed
- Merchant should top up wallet or funding account before retrying
Generic Transaction Error
Status Code
4777
Description
An unexpected transaction processing error occurred.
Example Response
{
"success": true,
"statusCode": 200,
"message": "success",
"data": {
"statusCode": 4777,
"statusDescription": "Transaction generic error",
"...": "...",
}
}Unassigned Transaction
Status Code
4999
Description
The transaction does not currently have a mapped processing state.
Example Response
{
"success": true,
"statusCode": 200,
"message": "success",
"data": {
"statusCode": 4999,
"statusDescription": "Unassigned Transaction"
}
}Status Code Summary
| Status Code | Status | Description | Final State |
|---|---|---|---|
4000 | CREATED_TRANSACTION | Transaction has been received and queued for processing | ❌ No |
4001 | PENDING_TRANSACTION | Awaiting customer or network confirmation | ❌ No |
4003 | CALLBACK_NOT_RECEIVED | Provider callback has not yet been received | ❌ No |
4005 | CANCELED_TRANSACTION | Transaction was cancelled before completion | ✅ Yes |
4007 | TRANSACTION_TIMEOUT | Transaction exceeded the allowed processing time | ✅ Yes |
4008 | PROCESSING_TRANSACTION | Transaction is actively being processed | ❌ No |
4011 | FAILED_TRANSACTION | Transaction failed during processing | ✅ Yes |
4200 | SUCCESSFUL_TRANSACTION | Transaction completed successfully | ✅ Yes |
4220 | REVERSED_TRANSACTION | Transaction was reversed after processing | ✅ Yes |
4230 | INSUFFICIENT_BALANCE | Insufficient funds to process transaction | ✅ Yes |
4777 | TRANSACTION_GENERIC_ERROR | Unexpected or uncategorized processing error | ✅ Yes |
4999 | UNASSIGNED_TRANSACTION | Transaction status is currently unassigned | ❌ No |
