Response Codes
Code
Description
Further Details
0
OK
Transaction completed successfully. No further action required.
10
Card number doesn't exist/not active
OR
PIN is invalid
In the case of some transactions, this indicates that the card number either does not exist within the database or it exists but has status of "Valid, Not Sold".
For PIN-protected transactions, this code also indicate an incorrect PIN
16
Card is locked
This is returned in response to PIN-protected transactions when a card has been locked due to 3 subsequent transaction attempts with an incorrect PIN. The card can only be unlocked via the Card Status page in Card Manager
20
Merchant cannot complete the requested transaction against the card
This is a generic "catch all" response code used for all endpoints, and is returned in a number of different scenarios.
For example:
- where the Chain and or merchant is invalid;
- if the merchant/card pan is set to "don't allow" the transaction;
if a daily limit is exceeded or if a currency mismatch occurs.
Due to the catch all nature of this response code we have further detail on its use here
21
This Merchant is invalid for the Pan.
For the Load, Balance and BalanceNoPIN endpoints, this is returned when a transaction cannot be completed due to a PAN/Merchant mismatch.
24
Transaction restricted due to merchant/card policy settings
For the Load endpoint, this is returned when a transaction cannot be completed due to a restriction configured in MID Transaction Control in the Connect Manager portal
30
Partial purchase transaction
This may occur in response to a Redeem transaction.
The card balance is insufficient to cover the transaction amount.
The entire remaining balance is debited from the card and this revised amount is returned in the amount field of the response message.
The integrator / merchant may offer the cardholder the choice at this point as to whether they wish to proceed and pay the outstanding amount by an alternative means. If the cardholder chooses not to proceed with partial payment, the transaction must be reversed
40
Exchange rate not present
The request message specifies a currency other than the card’s base currency, and the merchant does not have an exchange rate configured in Card Manager to allow currency conversion.
50
Maximum load exceeded
This may occur in response to a Load transaction.
The amount specified exceeds the maximum load limit configured for the merchant in STORE24.
The transaction amount is recalculated to the merchant’s maximum load limit and applied, and the new card balance is returned in the balance field of the response.
Depending on the needs of the integrator/merchant, the operator/cardholder may be prompted whether they wish to accept the maximum load value. If they do not wish to proceed, the transaction should be reversed.
51
Minimum load not met
This may occur in response to a Load transaction
The amount specified is less than the minimum load limit configured for the merchant in STORE24.
The transaction amount is recalculated to the merchant’s minimum load limit and applied, and the new card balance is returned in the balance field of the response.
Depending on the needs of the integrator/merchant, the operator/cardholder may be prompted whether they wish to accept the minimum load value. If they do not wish to proceed, the transaction should be reversed.
52
Maximum card balance exceeded
This may occur in response to a Load transaction.
The amount specified would cause the card balance to exceed the maximum card balance limit configured for the merchant in STORE24
The transaction amount is recalculated to the largest amount that will not cause the card's balance to exceed the merchant’s maximum permitted card balance and applied, and the new card balance is returned in the balance field of the response.
Depending on the needs of the integrator/merchant, the operator/cardholder may be prompted whether they wish to accept the maximum available load value. If they do not wish to proceed, the transaction should be reversed.
53
Limit Breach
(transaction not processed)
This may occur in response to a Load transaction
The card balance limit or daily/monthly limit configured for the merchant has already been reached and therefore no additional funds can be loaded.
60
Card is expired
The card has passed its expiry date. The expiry date will be returned in the Message field of the response message and should be displayed to the terminal operator.
73
Message details are incorrect
A combination of Card Number, Transaction Number and MID does not correspond with the original transaction.
75
Start/Expiry Date invalid
OR
Transaction not found
The date provided is not in the future
Reversal failed as 1 or more elements provided to find transaction are incorrect.
80
Mandatory field(s) missing
One or more mandatory fields is missing from the request message.
98
Limit Breach
This is a generic response code when hard decline = 'true' and one of the conditions described above as "Maximum load exceeded"; OR "Minimum Load not Met"; OR "Maximum card balance exceeded" has been breached.
99
Lost / Stolen Card
OR
Card Number is not active
This is returned in response to any message type when the card number in the message has been flagged as lost or stolen.
In the case of some transactions, this indicates that card number exists in the database but does not have a status code of "Active".