the card range not supported by the system

4. The VPSProtocol value is outside the valid range. You do not have any Custom templates uploaded onto your Sage Pay account and have selected to use the Custom templates option within your live My Sage Pay account. I need the MLNX_OFED for the infiniband network card works properly. Success! If you have sent an Amount field with an invalid number of digits after the decimal place. If the shopper has made an error with the card number then simply have the customer. Please refine the search. For example if your currency is GBP, the Amount field value can be sent as 123.45, 4567.89, 0.36, 12.30 but not as 123.456, 4,567.89, .36 or 12.3. If you are unable to identify the cause, please contact the Sage Pay support team if you are still being presented with this error message and we will look into this issue further. Troubleshooting an "Your card does not support this type of purchase" error: Is it a debit card? If a card ExpiryDate value of 1509 was passed this would generate this error code. You are attempting to perform an AUTHORISE request against an AUTHENTICATED transaction which will exceed the maximum value of 115% of its orginal value. The ReleaseAmount value must also be less than or equal to the amount of the original Deferred transaction in which you are attempting to perform the Release. The AccountType is not setup on this account. This URL must be http:// or https:// and be less than 255 characters long. Please check you code to ensure the Currency field of your POST contains a valid currency code, you may need to contact our customer services team to check which currencies are set up on your Sage Pay account. The Card Range not supported by the system. This URL must be http:// or https:// and be less than 255 characters long. Share Improve this answer Follow answered Nov 28, 2018 at 14:06 snack_overflow 536 2 11 27 The resource requested is no longer available and no forwarding address is available. If this value is incorrect or invalid, then our system will be unable to identify the original transaction. Surcharge not allowed on this payment system. You will need to check your card, and if it has expired, you will need to destroy the card and use a different card type for the transaction. If the card address consists of more than 200 characters please just entered the first 200 characters in order to continue. All previous AUTHORISE requests in total must not exceed the 115% value and any further AUTHORISE requests will be denied if they exceed the maximum limit. If you receive this system message, it means you have successfully registered a transactions using the Direct integration method. Also here is some document on how to fix the problem you are having right now. You can do this by highlighting each device and pressing the Delete key. You will need to check your code to ensure that the currency type is the same as the original transaction. This is a notification system message to inform you that the transaction was cancelled by the customer. Refund can no be performed until original transaction is settled. A tag already exists with the provided branch name. The BillingPostCode field, if provided, can only contain a maximum of up to 10 characters. the card range not supported by the system. An active transaction with this VendorTxCode has been found but the TxType is different. The payment will now appear as a failed transaction. If you have not requested that you are wanting to use the Form solution and attempt to post a transaction registration you will be presented with this error message. This URL must be http:// or https:// and be no more than 255 characters in length. The currency field will dictate what currency is being processed through your Sage Pay account and must be included in the post. Cannot retrieve contributors at this time. This is a required value within the Protocol and you will need to check your code to ensure that you are sending this information for each transaction you register with Sage Pay. It should contain no more than 40 characters consisting of letters and numbers only with no spaces or special characters. Invalid system used for the related transaction. Please check the related transaction is a AUTHENTICATED transaction. The Delivery Address1 contains invalid characters. You will need to check your code to ensure that you are not passing more than the maximum value of 7,500 characters and that there are no additional spaces being passed as these will be determined as additional characters. The Authorisation has been declined by the bank. The RelatedVendorTxCode value is too long. When the card number is entered into the Opayo system we use the range to identify the card type, and validity of the number before processing the transaction. Cannot create the new user. A VendorTxCode has not been provided within your transaction registration. If you did not provide a vendor name, then it would have been supplied by Sage Pay. The SuccessURL field must contain a Fully Qualified Domain Name and page reference pointing to the externally visible page on your site which your customers can be returned to if a transaction succeeds. You will need to check your code to ensure that you are providing a valid month and year format with no spaces or separator characters, eg 0712 and not as 07/12 should be sent for an expiry date of July 2012. Please use mobile device to refund transaction. You will need to check your code to ensure that you are retrieving the correct value from your database before passing this through in the RelatedVendorTxCode field. The check digit invalid. You have not provided us with the correct value within the VPSTxId field. Per HTTP spec that should be okay. The link is: http://www.sagepay.com/system_monitor.asp. 2. Until I get a response, is there anything else that I could be looking out for? System boots fine with secure boot off. Your Cancel was Successful, the authenticated payment will now appear in your failed transaction list. If you are using our Form integration method, you may also sometimes receive this message if your Encryption Password is incorrect, so we would suggest you check this information as well. The bank did not respond within an acceptable time limit. Similar results when you try and use an active card on the test.sagepay. You will need to use the previous card if this was a replacement card issued by your card-issuing bank. If you attempt to refund in another different currency to the original payment then you will receive this system message. The Authorisation process timed-out. You must also ensure that there are no spaces within this card number. The related transaction that you are attempting to send a RELEASE or ABORT POST to is not a DEFERRED transaction. You will need to check your code to ensure that you are providing a valid month and year format with no spaces or separator characters, eg 0710 and not as 07/10 should be sent for an expiry date of July 2010. There is a problem with the details that have been entered for a European Payment Type. The Vendor Rule Bases disallow this card range. You set up the length and range of card numbers that are acceptable for each card type. You will need to check your code to ensure that you have not entered more than 200 characters within this field on the payment pages. The SuccessURL field must contain a Fully Qualified Domain Name and page reference pointing to the externally visible page on your site which your customers can be returned to if a transaction succeeds. Transaction is not allowed without 3D secure authentication. You would have received this system message if you have not provided us with the correct value within the VPSTxId field. Browse other questions tagged, Where developers & technologists share private knowledge with coworkers, Reach developers & technologists worldwide, SagePay: Test card details not being accepted, How Intuit democratizes AI development across teams through reusability. If you have received this system message it it likely that you have not provided us with a valid card number within the CardNumber field. If you need to process this transaction, you will need to process the Authenticated transaction again. You will need to ensure that your code is passing either a value of 1 (Allow Gift Aid) or 0 (Do not Allow it) within this field. If you had entered the start date incorrectly please enter the correct date and try again. The ephemeral port range depends on the server operating system that the client operating system is connected to. Accepted values for the CardType field are: VISA (Visa Credit), MC (Mastercard Debit and Credit), DELTA (Visa Debit), UKE (Visa Electron), SOLO, MAESTRO (Solo and Maestro), AMEX (American Express), DC (Diner's Club), JCB (Japan Credit Bureau cards) and LASER (Laser cards). Please contact support to re-enable this functionality. The Amount value contains a decimal point. The Transaction was Registered Successfully with Sage Pay. If we receive a POST from any other server, you will see this error message. The BillingAgreement flag is invalid. The card number that you have entered cannot be validated and/or identified by the Sage Pay systems. Please try a different card. It is normally a number, but can contain characters depending on the acquiring bank. The Success URL value will need to be provided within your crypt string when posting your transaction registration. The PayPal billing agreement was not accepted or failed. The Vendor field should contain the Vendor Name which you specified on your application form when you signed up to Sage Pay. The VPSProtocol value is not supported by the system in use. The issue is normally associated when you are attempting to automate these actions. If you submit a value which is not in line with the ISO 4217 codes or is not set up on your account, you will get this system message. Please try again. No further refunds can now be performed against the original transaction. Returned when a transaction is declined or rejected. Either the currency requested is not available for this payment system, or the supplied combination of currency and paymentsystem is not available for this vendor account. A valid card number has not been supplied in the Card Number field. The MM and YY values should also be valid month and year numerics, for example the MM values should only ever be between 00 and 12 and the YY values should only ever be between 00 and 99. You are only able to RELEASE a DEFERRED transaction once and any further attempts will result in this system message being displayed. It should contain the type of transaction you wish to perform including values such as PAYMENT, DEFERRED, AUTHENTICATE etc as outlined within the Protocol and Integration guidelines. If you are wishing to add another card type to your account, please check with your acquiring bank first before notifying Sage Pay to ensure that your merchant number has been set up to accept this new card type. The first step to resolving this issue is to identify if the shopper has made an error when they have entered the card number when making the payment. You will need to enter the name of the credit or debit card holder in the Card Holder box provided on the payment page. Cannot create a token from a token transaction. Start Row and End Row range too large. Connect and share knowledge within a single location that is structured and easy to search. If you are providing a value which has more that 20 characters then you will receive this system message. What is the problem? You must provide at least one ##### element within ##### node. You will also need to check the content of this field to ensure that it is valid. 3D Secure rule not added. If you're trying to use one of these cards, you'll need to use another card to make the purchase. A valid