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. You will not be able to perform the REFUND that you are attempting as the total amount including all other REFUNDs performed against the original transaction exceed the total value of the original transaction. The Sage Pay system will cancel your transaction as default and present you with this error message after the third failed attempt. If you have not supplied the correct value in the RelatedVPSTxId field, have not submitted it in full or it is incorrectly formatted then you will receive this system message when our systems try to validate the post. You will need to ensure that your code is sending the customer's cardholder address to where the card is registered in the BillingAddress field. The Related transaction is not a DEFFERED payment. Original transaction was not a billing agreement. You will need to check you code and correct one or the other field to fix this problem. The only exceptions that can be provided as characters along with letters and numbers are hyphens(-), underscores (_) or full stops(.). You will need to check the URL to which you are attempting to send your POST to. 3D accelerator card is not supported! Pick Up Card. If a value is supplied, should contain either 0 or 1. The VPSProtocol value is outside the valid range. The IP address of each new server you POST from will need to be registered with Sage Pay. An active transaction with this VendorTxCode has been found but the TxType is different. The Authorisation was Rejected by the vendor rule-base. If you send an AccountType parameter with your POST, you must have an equivalent merchant account set up to handle that type of transaction. The credit or debit card number entered must be that of the card type selected before proceeding to enter the credit or debit card number. While the phone is on the restarting mode select "Wipe cache partition" in the Android service menu. A valid ##### value is required, this should be either ##### or #####. How can this new ban on drag possibly be considered constitutional? This is an important field as it allows us to identify and process the transaction through your account. as the VPSTxId, which uniquely identifies a transaction to the Sage Pay system, is generated by us and returned back to you. You will need to send the long card number only which is situated on the front of the customers card. The card type field contain a value which specifies the card that is being sent to us. The Delivery Surname contains invalid characters. Your code should send only the first 100 characters if your description is longer than this. 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 request was unsuccessful to the server being down or overloaded. If you have not registered your Sage Pay account to use the Form integration method and attempt to send a transaction registration POST using this method of integration, you will receive this error. The RelatedSecurityKey is a unique security value for each transaction and would have been sent back to your server in the status response of the original transaction. 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. 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. 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. You can only AUTHORISE an AUTHENTICATED transaction up to 115% of its value (with all previous AUTHORISEs against that transaction taken into account). You will need to ensure that your code is not sending invalid characters. You can follow the question or vote as helpful, but you cannot reply to this thread. If you are sending a RELEASE or ABORT POST to the Sage Pay system, but the related transaction you have specified is not a DEFERRED transaction, you will receive this system message. The Amount is outside the mininum and maximum limits. The Card Range not supported by the system. The PaymentSystem used for the original transaction does not support repeat transactions. Any current video adapter will meet this spec. Your transaction has been Authenticated successfully. The value which is being sent accross in this field is more than this. The given vendorsurcharge cannot be found. It would only be generated if you have integrated using the Direct method as this field indicates the type of card (Visa, Mastercard etc.) Please contact support to re-enable this functionality. You will need to check your code to ensure you are capturing the correct value being returned from Sage Pay and also that the VPSTxId you are submitting back to Sage Pay is correct. Please email support@sagepay.com with this error. 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. The Apply3DSecure field can only contain the following values: 0: Use the default setting on the Sage Pay System, 1: Force 3D-Secure checks and use appropriate rules 2: Force NO CHECKS for this transaction and always gain and authorisation 3: Force 3D-Secure checks but DO NOT apply rules and always gain an authorisation If any other characters or spaces are being passed or provided, then you will receive this error code and message. If you have sent an Amount field with an invalid number of digits after the decimal place. If a card StartDate value of 1509 was passed this would generate this error code. Please ensure that you are sending the correct value in the TxType field. This system message is only generated if you have integrated using the Direct method where you are collecting the card details to send across to Sage Pay. You will need to enter the name of the credit or debit card holder in the Card Holder box provided on the payment page. The Transaction type does not support the requested operation. You have not provided us with the correct value within the VPSTxId field. e card issue number length must be one or two digits long and entered exactly as it is displayed on the customer's card. 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. The GiftAid field can only ever contain two values : 1 : Allow Gift Aid 0: Do Not Allow Gift Aid. golden retriever breeders scotland. The Amount field should only contain numbers, with no separator characters and formatted to the correct number of decimal places for the specified currency. An active transaction with this VendorTxCode has been found but the some data fields are different. 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 method requested is not permitted against this resource. The Tranaction is not in a DEFERRED state. A transaction is unable to be registered without this information. When attempting to post a transaction registration using the Form integration method you will need to have had an encryption password generated by Sage Pay. The CardExpiry date that has been entered is not a valid month and year combination. Please check to ensure that a Failure URL is being provided with each transaction as this is a required field. Are you sure you want to create this branch? A required parameter is missing. In this case, please . Unfortunately, we are unable to process transaction values outside of these ranges. Unable to find the transaction for the