Zamupay Transactions Response Codes - ZamuPay API Documentation

For status codes marked as Retry (Without New ID), this indicates there may have been intermittent connectivity issues, and the transaction with the same ID is not captured on our system.

For Retry (With New ID), the transaction has already been captured by our system, and attempting to retry the same transaction with the same ID will result in a duplicate error.

In cases where the status is inconclusive, you should wait for the callback (final response). Additionally, it is advisable to query transactions with status codes marked as Query, especially if your system may have missed a callback due to network issues, before attempting to retry the transaction.

For status codes marked as Escalate (rare failure cases), you will need to contact our support team to investigate the issue before attempting a retry, as retrying without resolution may result in duplicate payments, reversals, or potential loss of funds.

Code	Description	Action	Comments
0	Success	Success	Mark as Success
-1	Transaction timeout	Retry with new originatorConversationID
1	Insufficient funds	Mark as Failed
2	Transfer limit exceeded	Mark as Failed
3	Internal server error	Mark as Failed
4	Third party internal server error	Mark as Failed
5	Invalid debit account (B2C)	Mark as Failed
6	Invalid credit account	Mark as Failed
7	Transfer amount below limit	Mark as Failed
8	Invalid transaction element	Escalate
9	Duplicate transaction	Query Using originatorConversationID
10	Server busy	Mark as Failed
11	Transaction not found	Retry with same ID
12	General error	Escalate
13	Third party general failure	Escalate
14	Inconclusive status	Requery status
15	Insufficient wallet balance	Mark as Failed
16	Third party system unavailable	Query
17	AML Check failure	Mark as Failed
18	Declined	Escalate
19	Validation failed	Mark as Failed
20	Third party integration error	Escalate
21	Unmapped code	Escalate
22	Partner timeout	Escalate
202	Request accepted for processing	Wait for callback
200	Request processed successfully	Wait for callback
400	Bad request. For example, this happens when there is a validation error(missing fields) or when there is a duplicate entry(originatorConversationId)	Mark as Failed
401	Unauthorized request, Bearer token expired or invalid credentials	Mark as Failed
404	Request URL not found	Mark as Failed
429	Too many requests	Escalate
500	Internal server error	Mark as Failed
999	Your transaction cannot be completed at this moment. Please try again later. - System Code: 1	Mark as Failed