Transaction Types
| Value | Description |
| 01 | Sale |
| 02 | Refund / Credit |
| 03 | Authorisation |
| 04 | Authorisation Reversal |
Result Codes
| Result Status | Result Code | Result Description | Possible cause | Action |
| 0 (Okay) | 0 | Approved | ||
| -1 (Not okay) |
1 | Timeout waiting for response | No response to the transaction has been received from the Issuer or the Acquirer. | The transaction must be declined to the card holder but can be retried at a later stage. |
| -1 (Not okay) |
3 | Hot card | The card has been reported as lost or stolen by the card holder or the Issuer of the card. | The transaction must be declined to the card holder. Retrying this transaction will not result in a different result so there is no point in retrying the transaction. |
|
-1 |
4 | Denied | The cards' account is not in good standing at the Issuer due to, amongst other reasons, insufficient funds. It is also possible that the fraud score on this card has caused this transaction to be Denied. | The transaction must be declined to the card holder. Retrying this transaction will not result in a different result so there is no point in retrying the transaction. |
|
-1 |
5 | Please call | The Issuer regards this transaction as suspicious and refuses to authorise the transaction online. | The transaction must be declined to the card holder but the Merchant may choose to try to process this transaction out of band. To do this the Merchant must contact the Merchant Help Desk by telephone. The Merchant Help Desk will, in turn, contact the issuer to obtain an AuthorisationCode and this AuthorisationCode may be used to process the transaction. It is important to note that this process is out of band to the original transaction. |
|
-1 |
6 | Card Address failure | The Card Address submitted with the transaction does not match the address on record at the Issuer. This is commonly referred to as an AVS failure. | The transaction must be declined to the card holder. After the Merchant obtains the correct Card Address from the card holder the Merchant may retry this transaction. |
| 1 (Warning) |
6 | Warning: Approved but Card Address failure | Approved but the Card Address submitted with the transaction does not match the address on record at the Issuer. This is commonly referred to as an AVS failure. | The Merchant must decide whether to accept the approval in spite of the failure of the AVS check or to decline the transaction. If the Merchant decides to decline the transaction a Void MUST be processed in order to roll the transaction back. If a Void is not processed the card holder will be charged since the transaction was Approved by the Issuer. |
| -1 (Not okay) |
7 | Card Security Code failure | The CSC/CVV submitted with the transaction was either absent or incorrect. | The transaction must be declined to the card holder. After the Merchant obtains the correct Card Security Code from the card holder the Merchant may retry this transaction. |
| 1 (Warning) | 7 | Warning: Approved but Card Security Code failure | Approved, but the CSC/CVV submitted with the transaction was either absent or incorrect. |
The Merchant must decide whether to accept the approval in spite of the failure of the Card Security Code check or to decline the transaction. If the Merchant decides to decline the transaction a Void MUST be processed in order to roll the transaction back. If a Void is not processed the card holder will be charged since the transaction was Approved by the Issuer. |
| -1 (Not okay) |
8 | Card Type not accepted | The card type (garage, fleet etc.) or association (visa, mastercard, etc) cannot be processed for the ApplicationID specified in the transaction. | The transaction must be declined to the card holder and the Merchant must contact their Merchant Help Desk to resolve this. The Merchant must request that the card type that was rejected be added to the list of of supported Card Types for the ApplicationID. |
| -1 (Not okay) |
9 | Unable to process the transaction | This indicates a temporary problem of indeterminate origin. | The transaction must be declined to the card holder but can be retried at a later stage. |
| -1 (Not okay) |
10 | Card blocked | The card number is configured to be disallowed by the Merchant and/or Acquirer for this ApplicationID. This configuration is controlled by the Merchant and/or the Acquirer. | The transaction must be declined to the card holder. |
| -1 (Not okay) |
11 | Invalid amount | The transaction amount may be invalid, too big or exceeds a daily limit. | The transaction must be declined to the card holder but may be retried with a lesser/valid amount at a later stage. |
| -1 (Not okay) |
12 | Invalid budget period | The number of months specified for the budget period in the transaction is not acceptable for the issuer. | The transaction must be declined to the card holder but may be retried with a valid budget period at a later stage. |
| -1 (Not okay) |
13 | Void unsuccessful | The original transaction that is the target of the Void can no longer be voided typically as a result of a change over of the bank settlement cycle. | The Merchant must stop sending a Void for the original transaction. Retrying this transaction will not result in a different result so there is no point in retrying the transaction. |
| -1 (Not okay) |
14 | Invalid card number | The card number specified in the transaction failed the Mod10 check or does not exist at the issuer. | The transaction must be declined to the card holder. After the Merchant obtains the correct card number from the card holder the Merchant may retry this transaction. |
| -1 (Not okay) |
15 | Invalid track2 | The track2 specified in the transaction is not in the correct format or does not exist at the issuer. | The transaction must be declined to the card holder. After the Merchant obtains a correct track2 from the card holder the Merchant may retry this transaction. |
| -1 (Not okay) |
16 | Invalid card date | Either the expiry date or the start date specified in the transaction is either invalid or expired. | The transaction must be declined to the card holder. After the Merchant obtains the correct start and/or expiry date from the card holder the Merchant may retry this transaction. |
| -1 (Not okay) |
18 | Invalid authorisation code | The authorisation code specified in the transaction has invalid characters or does not exist at the issuer. | The transaction must be declined to the card holder. After the Merchant obtains a valid authorisation code from the Merchant Help Desk the Merchant may retry this transaction. |
| -1 (Not okay) |
19 | Incorrect PIN | CAUSE : The PIN entered by the card holder was incorrect. | The transaction must be declined to the card holder. After the Merchant allows the card holder to enter his or her PIN again, hopefully correctly this time, the Merchant may retry this transaction. |
| -1 (Not okay) |
20 | Device PIN Key has expired | This only applies to PINBlock where the encryption used is MasterSession as opposed to DUKPT. | The transaction must be declined to the card holder. After the Merchant has used the V_XML GetDevicePINKey command to get the new key the Merchant may retry the transaction. |
| 1 (Warning) |
21 | Warning: Approved but Cash Denied | The sale amount component of a “sale with cashback” transaction was approved, but the cash amount component of the transaction was not approved by the Issuer. | The Merchant must deliver the goods and/or services purchased to the card holder but must decline to deliver the cash amount requested in the transaction to the card holder. |
| -1 (Not okay) |
22 | EMV not supported | The POS device used in this transaction is not certified to do EMV (chip) transactions. | The transaction must be declined to the card holder. The Merchant should contact the Merchant Support Desk to resolve why the POS device is not capable of supporting EMV (chip). |
| -1 (Not okay) |
23 | Card information not present | The PAN data relating to the token supplied in a tokenized PAN transaction could not be found in the database. This can happen if the original transaction identifiers supplied in the transaction are either invalid or no longer exist in the database. | The transaction must be declined to the card holder. The Merchant should investigate whether the original transaction identifiers supplied in the transaction were invalid or referred to a transaction that was processed more than 6 months prior to this transaction. |
| -1 (Not okay) |
100 | File is not available for download | The filename requested is not available for download. This is usually because the filename requested has not completed processing. | The Merchant should retry this transaction after an appropriate amount of time has elapsed. An appropriate amount of time would be 20 minutes. If after a number of retries the error is still being received the Merchant should stop retrying and contact the Merchant Help Desk to investigate. |
| -1 (Not okay) |
101 | File has already been uploaded | The same file has previously been uploaded. | The Merchant should investigate whether the file really should be uploaded or not. If the file should be uploaded, the Merchant should upload it with a different filename. |
| -1 (Not okay) |
255 | General error (default description) | This result can have various causes but essentially they should all relate to either a configuration or development issue that needs to be resolved. | The transaction must be declined to the card holder and the Merchant should contact the Merchant Help Desk for assistance. The error description returned describes the actual cause and the transaction should not be retried until the root cause has been investigated and resolved. |