When you receive the notice: "card not supported" on your credit card machine, it means just that - the specific card brand (or type) you are attempting to charge is not supported by your processor (or you are yet to register for processing that card brand). 3) Live with it as is. Please ensure that you are posting this field with each transaction and that you use the correct value. If you are providing a value which has more that 20 characters then you will receive this system message. One or more of the specified already exists for the merchant number/currency combination. the card range not supported by the system In case your SD card is missing a drive letter, click on the 'Add' button. This system message would only be generated if you have integrated using the Direct method where you are colleting the customers card details to send across to Sage Pay. Please try again. Styling contours by colour and by line thickness in QGIS. More than 50,000 rows returned. The Delivery City contains invalid characters. You will need to ensure that you do not submit more than the maximum of 255 characters within this field. The Delivery Phone contains invalid characters. The Billing Surname contains invalid characters. You will need to check your code to ensure that your server is not sending more than 50 characters within this field. You might receive an error message while making a payment which says "Your card does not support this type of purchase." There are a few reasons why you may receive this error: 1. This field is numerical only and can only support values from 0.01 to 100000.00. The Sage Pay service that you are attempting to contact does not exist or is currently unavailable. Sexta, 26 de novembro de 2021 A valid

value is required in the format 123.123.123.123. If the feature is not supported, response code is anything else but 206 and the response doesn't include Content-Range header. You will need to check to ensure that the correct value is being submitted. For example, if you send M, you must have a MOTO enabled Merchant Number registered with Sage Pay. If you double click on the card and go to the Drivers tab of the dialog that opens, give us the Driver Version. Does a summoned creature play immediately after being summoned by a ready action? The Amount including surcharge is outside the allowed range. You signed in with another tab or window. The Apply3DSecure flag is invalid. You will need to ensure that your crypt string contains a Fully Qualified Domain name and page which will allow us to return the customer back to a visible Failure Page on your site once the transaction has been registered as unsuccessful. Check your code to ensure that you only use a fully qualified URL. A transaction is unable to be registered without this information. You will only be able to enter up to 50 characters in the card holder name box on the payment pages. If your customer is trying to use one of these cards, they will need to use another card to make the purchase. You will need to check the Protocol for the integration method (Form, Server or Direct) that you are using to ensure that you are sending the correct value in the TxType field. If you are passing any other characters, or spaces, you will receive this error. The TxType requested is not active on this account. You will need to check your code to ensure that your server is sending a valid e-mail address which does not contain more than 255 characters in length. Please contact support to re-enable this functionality. This enabled test mode on the gateway and allows test cards to be used on the account so I can test a full payment. The related transaction that you are attempting to send a RELEASE or ABORT POST to is not a DEFERRED transaction. A valid value is required,this must be value between 0 and 100000.00. The Failure URL value will need to be provided within your crypt string when posting your transaction registration. Client IP address is restricted by the vendor. This will be due to the transaction timing out and will result in transactions not being authorised and being registered as failed payments. There is not really any big negative to having the CSM enabled. The message POSTed to the Sage Pay system was of an invalid type. Success! You will also need to check the content of this field to ensure that it is valid. This could be due to several reasons such as funds not being available, spending limit may have been reached or bank account has been closed. This will always be 16 characters or less, and only contain letters and numbers with no spaces or unusual characters. Unfortunately, we are unable to authorise your transactions as the network connection to the bank is currently unavailable. You will need to check your code to ensure you are submitting the correct value. The PaymentSystem is not supported on the account. Cannot complete request. You will need to check your code to verify the SecurityKey from the original transaction to which you are attempting to send your REFUND, REPEAT or AUTHORISE request to. A VendorTxCode has not been provided within your transaction registration. By clicking Accept all cookies, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy. As detailed above the card security code will consist of either three or four digits only depending on the card type selected. The request was unsuccessful because the URL specified is longer than the server is willing to process. If you are wishing to accept American Express, JCB or Diner cards, it is likely that you will need to contact these merchant acquirers directly to obtain a new merchant number. The CardExpiry date that has been entered is not a valid month and year combination. You must ensure that you are sending no more than 50 characters within your transaction registration POST and if the cardholder's name is longer than this you will need to send the first 50 characters only. Please check with our support team if you are uncertain which cards your account has been set up with. You can only AUTHORISE an AUTHENTICATED transaction up to 115% of its value (with all previous AUTHORISEs against that transaction taken into account). Easiest way is likely hit the Windows key (Windows 7 through 8.1), and start typing Device Manager. The expiry date of the card that you have entered on the payment pages is in the past. The card ExpiryDate value should always be presented in a MMYY format (a two-digit month followed by a two-digit year) and this should never include any separators such as a forward slash (/) or a hyphen (-). 2. The Currency fields should only ever contain the 3-letter ISO 4217 codes and a valid currency code type that has been set up on your Sage Pay account. The CardNumber field should only contain numbers. You will need to check the URL to which you are attempting to send your POST to. The CardStart date that has been entered is not a valid month and year combination. This will be required if you have AVS turned on within your Sage Pay account. Why are physically impossible and logically impossible concepts considered separate in terms of probability? Unable to find the transaction for the supplied. There is a problem with the details that have been entered for a European Payment Type. Cost of Item n including tax: Total cost of item n. Please refer to the integration documentation for more information. You will need to check that you are sending the correct SecurityKey of the original transaction in this field. The RelatedSecurityKey does not match the original transaction. The deferred transaction has been successully released and will be sent for settlement. Share Improve this answer Follow answered Nov 28, 2018 at 14:06 snack_overflow 536 2 11 27 Please check the related transaction is a AUTHENTICATED transaction. 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 is normally a number, but can contain characters depending on the acquiring bank. You will need to ensure that you have logged back into your My Sage Pay admin account and selected the Default templates in order for the Sage Pay payment pages to re-appear. This is a standard HTTP Error. Please ensure you are only passing values within this range and not including any separator characters other than the decimal point. The Authorisation was Rejected by the vendor rule-base. If the transaction has already been VOIDed you will be presented with this error message as you are only able to VOID a transaction once. If you're pointing to the live.sagepay endpoint then test cards will not work and will return the error you've mentioned. VOID operation is not supported for PAYPAL transaction. The Card Range not supported by the system. Account type selected requires 3D secure authentication to process Maestro or SOLO cards. You will need to ensure that the start date selected is not later than the current date. The given vendorsurcharge cannot be found. We could not process your message, please check your integration settings or contact the support team. The FailureURL 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 fails. The Vendor configuration is missing or invalid. The card is a Visa Electron or pre-paid Visa Debit card. A graphics or video driver is the software that enables communication between the graphics card and the operating system, games, and applications. 3D Secure rule not added. Check your code to ensure you are checking the validity of all CV2 numbers entered on your site before forwarding them to Sagepay. This system message is usually generated when your are attempting to action on an original transaction (such as a refund, void, repeat, release etc) and the details of the original transaction (RelatedVendorTxCode) has not been provided. This URL must be http:// or https:// and be less than 255 characters long. The TxType field determines how the transaction will be processed by the Sage Pay system. The VendorName field should only ever contain the Vendor Name supplied by Sage Pay or selected by you during your application process. The request to ABORT a deferred transaction was successful. The VendorEMail field can only ever contain a maximum of up to 255 characters and if you pass more than this within this field, you will receive this system message. Delete the problematic software, then redownload it from Nintendo eShop. The GiftAid field can only ever contain two values : 1 : Allow Gift Aid 0: Do Not Allow Gift Aid. Please use the mobile device. If the card has expired it will need to be destroyed and a different card type will need to be used ensuring that the expiry date has not passed. If you receive this error, then the Vendor account has not been successfully set up on the Sage Pay servers. Your Vendor Name must contain no more than 16 characters with no spaces or unsual characters. A valid card number has not been supplied in the Card Number field. 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. An ERROR has occurred on the Sage Pay System. The nature of simulating nature: A Q&A with IBM Quantum researcher Dr. Jamie We've added a "Necessary cookies only" option to the cookie consent popup. You must provide the first 9 digits of the card number in the field. You must ensure that a post code value has been entered within the edit box that has been provided on the payment page. You will be able to locate the required Protocol and Integration guidelines for each solution under the Downloads section on the Sage Pay support web site. Returned when a transaction is declined or rejected. All issue numbers must be entered exactly as they appear on the card, without spaces (either 1 or 2 digits). If you receive this error message and are experiencing this on all your transactions, please contact our customer services team who will need to contact your merchant acquirer to ensure that everything has been set up correctly. Form transactions are disabled for this vendor in the test environment. TransactionType of the related transaction is not supported for this operation. The Related transaction is not a DEFFERED payment. Invalid request. The total value of all REFUNDs can never ever exceed the original transaction value amount. 3D-Authentication failed. The NotificationURL which you have provided is not recognised by the Sage Pay servers and therefore we cannot send you all the transaction completion information. This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To learn more, see our tips on writing great answers. The Amount field value can only contain numbers with no separator characters and this should be formatted to the correct number of decimal places for the specified currency. You must check your code to ensure that you only use a fully qualified URL. You will need to check your code to ensure that you are entering numeric values only and that no letters are being passed over. You will need to ensure that you have entered the full card number correctly and only those numbers that appear on the front of the card and try again. Learn more about bidirectional Unicode characters. Cannot retrieve contributors at this time. If we receive a POST from any other server, you will see this error message. The Sage Pay system has a maximum and minimum acceptable transaction value which are 100,000GBP and 0.01GBP respectively, with approximate equivalents in other currencies. If you had entered the start date incorrectly please enter the correct date and try again. You will need to send the long card number only which is situated on the front of the customers card. In the new Run window popped up, type msconfig, and hit Enter. If you are wishing to use custom templates, you will need to download the relevant files, amend and send over to use to be uploaded. All VendorTxCodes must be unique. If no security code (CV2/CVV) has been provided, you will receive this system message. The server received an invalid response from the upstream server while trying to fulfil the request. 1 Answer Sorted by: 0 Check which environment you are using. After each of the following steps, check to see if the issue is resolved: Ensure that your console has the latest system update installed. Please ensure that you only ever use a fully qualified URL. 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 send an AccountType parameter with your POST, you must have an equivalent merchant account set up to handle that type of transaction. You will receive this system message if you have not provided us with a CardType field within your Direct transaction registration POST. The eMailMessage field can contain a maximum of 7,500 characters. The command cannot be run for the vspvendorname provided. Cannot authorise this card. The certificate must have the digital signature key usage. If you are providing a value which has more that 20 characters then you will receive this system message. The following currency code(s) are either not valid or not supported:. 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. Authentication credentials are missing or incorrect. The Card Type selected does not match card number. It should be less than 40 characters long, contain only letters and numbers and match the value passed in the original transaction. 4021 : The Card Range not supported by the system. The Authorisation process timed-out. Any current video adapter will meet this spec. Should be between 2.00 and 2.22. This error message relates to the Vendor account not having been set up successfully on the Sage Pay servers. The card number that you have entered cannot be validated and/or identified by the Sage Pay systems. You will need to check your code to ensure that the field is sending the correct code. You are not passing the currency field through with your transaction. If this is correct, then the card is not yet valid and must not be used and you will need to use your previous card if this was a replacement card issued by your bank. No further action required. The StartDate is in the future. The Delivery Address1 contains invalid characters. The simulator saw the Vendor Name ''. You must enter the address to which the card being used is registered in the card address box provided on the payment page. Cannot create a token from a token transaction. The currency field can only accept the ISO - 4217 codes. Any URL's which are longer will generate this system message. A surreal understated experience about loss and finding new life inspired by real-life experiences. The Contact Fax contains invalid characters. You have not provided us with the correct value within the VPSTxId field. How can this new ban on drag possibly be considered constitutional? The PhoneID is not registered to any vendor account. A valid ##### value is required, this should be either ##### or #####. The issue is normally associated when you are attempting to automate these actions. The card number has failed our validity checks and is invalid, Merchant session key or card identifier invalid, Operation not allowed for this transaction, This refund amount will exceed the amount of the original transaction. How to notate a grace note at the start of a bar with lilypond? Possible solutions. The VendorTxCode should contain your unique reference identifier for your transaction. Every transaction you send to the Sage Pay Systems must have a unique VendorTxCode. Please check to ensure that a Failure URL is being provided with each transaction as this is a required field. Should not include leading zero's, and only include values in the range of 0 to 255. The card StartDate value should always be presented in a MMYY format (a two-digit month followed by a two-digit year) and this should never include any separators such as a forward slash (/) or a hyphen (-). Overlaps with an existing rule. If you are using your Simulator encryption password you will receive this error message when posting to the test or live servers. The server has refused to fulfill the request. It would only be generated if you have integrated using the Direct method as this field indicates the type of card (Visa, Mastercard etc.) If you have received this system message, it is likely that you are incorrectly supplied the Start date. Please select the card type you would like to use for the transaction. Invalid command. 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. The card number that you have entered on the payment pages is not a valid card type. The Billing Address2 contains invalid characters. If a value is supplied, should contain either 0 or 1. We also return to you the 2 digit Decline Code from the bank. The Success URL value will need to be provided within your crypt string when posting your transaction registration. Please check to ensure that a Vendor name is being provided with each transaction as this is a required field. The Billing Address contains invalid characters.