Card and Response Codes

These codes help merchants identify the cause — whether it’s insufficient funds, expired cards, network issues, or other conditions.

How to use these codes

Each transaction includes a ResponseCode and message in the API or on your transaction report. Use the table below to understand what the code means and the recommended merchant or customer action.

Code	Meaning	Recommended Action
00	Approved or completed successfully	No action required. Transaction successful.
01	Refer to card issuer	Ask the customer to contact their bank.
04	Pick up card	Declined; retain the card if possible.
05	Do not honour	Declined. Ask the customer to use another payment method.
12	Invalid transaction	Check the transaction type and data submitted.
14	Invalid card number	Confirm the card number or try another card.
30	Format error	Verify the request format matches DPO’s integration specification.
41	Lost card	Declined. Advise the customer to contact their bank.
43	Stolen card	Declined. Customer must contact issuer.
51	Insufficient funds	Customer should use another card or retry later.
54	Expired card	Ask the customer to use a valid card.
57	Transaction not permitted to cardholder	Customer’s bank has blocked the transaction type.
61	Exceeds withdrawal limit	Customer has reached their card’s limit.
91	Issuer or switch inoperative	Temporary issue. Try again later.
96	System malfunction	Retry later. If repeated, contact DPO Support.

See this page for all the response codes.

📘
Response codes may vary depending on the acquirer and card network. Refer to your integration API for the complete list.

Common decline reasons

Incorrect CVV or expiry date.
Customer’s card issuer declined due to fraud suspicion.
Insufficient funds or exceeded limits.
Network timeout or communication issue.

Where to view response codes

In the Merchant Portal, under Transactions → Details.
In API responses, look for ResponseCode and ResponseDescription.
In the settlement or reconciliation report CSV.

View Full Code List Contact Support