Find out why a payment may not have been processed successfully.
If you’re a partner, for example with a gateway that you want to integrate with our acquiring platform, the following codes can help you to understand why and how a payment has failed. Each response code has one of the following prefixes:
V indicates a validation error (for example, invalid card number)
D indicates a declined transaction
For information, see What do Dx response codes mean?
R indicates a referral (to be treated as a declined transaction)
For information, see What do Rx response codes mean?
C indicates a cancelled transaction (for example, a user selected Cancel on a payment page)
For information, see What do Cx response codes mean?
S indicates a system error
For information, see What do Sx response codes mean?
The prefix is followed by three digits, for example x01. The first digit, for example the x, is for internal use only. The next two digits, for example the 01, provide more details about the response. The following list presents the code and the message for each response.
Validation errors
|
Code |
Message |
Explanation |
|
Vx01 |
Invalid merchant details |
The transaction was refused by the card issuer. The customer should contact their bank for clarification. The customer can try again after resolving the issue with their bank. Alternatively, the customer can use a different payment method. |
|
Vx02 |
Invalid expiry date |
The expiry date does not match the expiry date on the card. The expiry date must be numeric. Ask the customer to check the card details and try again. |
|
Vx03 |
Invalid start date |
The start date does not match the start date on the card. The start date must be numeric. Ask the customer to check the card details and try again. |
|
Vx04 |
Invalid issue number |
The issue number does not match the issue number on the card. The issue number must be numeric. Ask the customer to check the card details and try again. |
|
Vx05 |
Invalid CVV |
The security code (CVV) does not match the code on the card. The security code (CVV) must be numeric. Ask the customer to check the card details and try again. |
|
Vx06 |
Invalid card number |
The card number does not match the number on the card. The card number must be numeric. Ask the customer to check the card details and try again. |
|
Vx07 |
Cardholder name not set |
The name of the cardholder was not included in the Cashflows Remote API request. |
|
Vx08 |
Insufficient address details |
The address details required by the Cashflows Remote API are incomplete. |
|
Vx09 |
Invalid country code |
The country code is not a standard country code. The country code must be in the format specified on the ISO Country Codes list. |
|
Vx11 |
Invalid email address |
An email address was not found, or the email address provided is not valid. Ask the customer to check the spelling. Check that there are no spaces and there is a full stop before.com, .org and so on. |
|
Vx12 |
Invalid phone number |
The phone number is not a valid phone number or may be incomplete. Check that the country code and/or area code is valid. Phone numbers must be numeric and must not include spaces. |
|
Vx13 |
Invalid amount |
The card issuer has declined the payment because a field or format is invalid. This typically applies to Debit and Prepaid Cards or cards that are not for online payments. Ask the customer to retry or use a different payment method. |
|
Vx14 |
Invalid currency code |
The currency code is not a standard currency code. The currency code must be in the format specified on the ISO Country Codes list. |
|
Vx15 |
Invalid customer IP |
The Customer IP address isn't formatted correctly. |
|
Vx16 |
Original trans not found |
The ParentTransactionID or tran_orig_id is not correct. |
|
Vx18 |
Unknown transaction type |
The type of transaction is incorrect or not recognised. |
|
Vx19 |
Card number changed |
|
|
Vx21 |
Original trans ref required |
For a recurring transaction, we need the ParentTransactionID or the tran_orig_id. |
|
Vx20 |
Currency changed |
|
|
Vx22 |
Amount exceeds original |
A refund has been attempted but the amount requested for the refund is higher than the value of the original sale. A refund cannot be more than the value of the original payment. |
|
Vx23 |
Can not refund this type of transaction |
Refunds apply only to Sale transactions. You cannot refund any other type of transaction. |
|
Vx26 |
Invalid request |
The payment request that we’ve received doesn't match the configuration of the MID. Send an email to support@cashflows.com |
|
Vx29 |
Card/currency combination not supported |
The transaction request doesn't match the configuration of the Merchant ID (MID). Please contact Cashflows. |
|
Vx30 |
Unknown card type |
|
|
Vx33 |
Duplicate transaction |
The same transaction reference or order reference has been used more than once. For every authorised transaction, these values must be unique. |
|
Vx34 |
Unable to void transaction |
|
|
Vx35 |
Original trans was not authorised |
The original transaction wasn't authorised and therefore the recurring transaction failed. |
|
Vx36 |
Invalid PIN |
The customer has entered an incorrect PIN. Ask them to re-enter their PIN or use a different payment method. |
|
Vx37 |
Unknown transaction class |
The transaction class provided is incorrect. |
|
Vx39 |
Card expired |
The customer has entered an incorrect expiry date or is attempting to pay with a card that has passed its expiry date and is no longer valid. Therefore, it may not be used. Ask the customer to check that the expiry date is correct or to use a different payment method or card. |
|
Vx40 |
CVV Required |
A security code (CVV) is required but the customer has not provided one. |
|
Vx41 |
Original transaction already settled |
An attempt has been made to capture or release a transaction, but it has already been settled. |
|
Vx42 |
Original transaction already cancelled |
The customer has already cancelled the original transaction. |
|
Vx44 |
Transaction details do not match original |
|
|
Vx47 |
Card holder name does not match |
The issuer of the card may have declined the payment because the cardholder’s name provided doesn’t match the cardholder’s name in their system. Check the spelling of the cardholder’s name. Also check the title for example Mrs, Ms or Mr. |
|
Vx48 |
User details not valid |
|
|
Vx49 |
Duplicate transaction still processing |
|
|
Vx50 |
Original transaction too old |
|
|
Vx51 |
Transaction not currently supported |
|
|
Vx52 |
3DS not enabled |
|
|
Vx53 |
3DS data invalid |
Authentication data is required for this payment, but the extra details were either incomplete or incorrect and therefore did not meet the requirements for Strong Customer Authentication (SCA). Check that all required data is correct and included and retry. |
|
Vx54 |
Concurrent authorisations |
|
|
Vx55 |
Invalid funds recipient data (applies to MCC 6012 Merchants) |
|
|
Vx56 |
Terminal mismatch |
|
|
Vx57 |
Transaction not allowed on this card |
The customer has tried to use a card that does not support the type of payment. |
|
Vx58 |
Original transaction requires 3DS attempt/auth |
Authentication data is required for this payment, but the extra details were either incomplete or incorrect and therefore did not meet the requirements for Strong Customer Authentication (SCA). Check that all required data is correct and included and retry. |
|
Vx59 |
ECOM transactions require 3DS attempt/auth |
Authentication data is required for this payment, but the extra details were either incomplete or incorrect and therefore did not meet the requirements for Strong Customer Authentication (SCA). Check that all required data is correct and included and retry. |
|
Vx60 |
Verify not supported for acquirer |
|
|
Vx61 |
Recurrence Flag usage invalid |
|
|
Vx62 |
Initial Sale/Verify ARN missing for subsequent sale |
|
|
Vx63 |
Initial Sale/Verify for subsequent sale not approved |
|