If any of the fields change from one transaction to the next, Authorize.Net will not view the transactions as duplicates.
The twin transaction window will constantly be two minutes for all transactions submitted through the Virtual Terminal. If you wish to adjust the duplicate transaction windowpane for transactions submitted from your software, such as a web site or denounce haul, you may do therefore by adding the field duplicateWindow to your web site script.
If you are unable to adjust or add this variable to your shopping handcart settings, please contact your shopping cart subscribe team for extra aid in this attentiveness. The variable duplicateWindow tells us, in seconds, how a lot fourth dimension we should check for duplicates after a transaction is submitted.
The largest value we will accept for duplicateWindow is 28800, which equals eight hours. If a rate greater than 28800 send, the requital gateway will default to 28800. If duplicateWindow is set to 0 or to a negative number, no duplicate transaction window will be enforced for your software ’ mho transactions. If no value is sent, the default option value of 120 ( two minutes ) would be used.
For exemplar, if you wished to set a duplicate transaction windowpane of five minutes ( = 300 seconds ) you would set duplicateWindow to 300.
Note : By submitting duplicateWindow with your on-line transactions, we will return further details along with this error reply, including :

• The original transaction ID that was duplicated;
• AVS and CVV responses for the original transaction;
• The original authorization code, if the transaction was authorized;
• The MD5 hash, if a MD5 hash value was generated for the original transaction.

If you do not submit the duplicateWindow field, we will not return any details from the original transaction, even if you submit a duplicate transaction . A transaction with identical amount and credit card information was submitted within the previous two minutes. 12 An authorization code is required but not present. The transaction request required the field authCode but either it was not submitted, or it was submitted without a value. 13 The merchant login ID or password is invalid or the account is inactive. This error indicates you are either posting the incorrect API Login ID within your script, connecting to a server that does not recognize your account, or using an account which is inactive. Please follow these steps to ensure that your software is connecting correctly:

• If you are posting your transaction requests to the gateway URLs https://test.authorize.net/gateway/transact.dll and you are using an account given to you by an Authorize.Net Reseller or from Authorize.Net Sales, you may encounter this error. The gateway URLs mentioned above only work with specific test accounts, available upon request by completing the form at https://developer.authorize.net/hello_world/sandbox/
• Please check your script and verify you are posting the API Login ID for the account in question. If you are not posting the correct API Login ID, or if you are not sending an API Login ID, please edit the script and confirm that the field name is set to the API Login ID that you may obtain from the Authorize.Net Merchant Interface. Please see the Getting Started Guide at https://www.authorize.net/content/dam/authorize/documents/gettingstarted.pdf for instructions on obtaining the API Login ID.
• If you are unable to log into your Authorize.Net Merchant Interface, this could indicate that your account is inactive. Please contact Merchant Support for assistance.
• If the account is active and the API Login ID is correct, please use the Data Validation Tool to validate the fields you are passing to us.

• Login to your Merchant Interface at https://account.authorize.net/
• Click Settings in the main left side menu
• Click Response/Receipt URLs
• Click Add URL
• Enter your Response URL
• Click Submit

• Login to your Merchant Interface at https://account.authorize.net/
• Click Settings in the main left side menu
• Click Payment Form
• Click Form Fields
• Uncheck the field provided in the Error 33 text.
• Click Submit

• Check that your script permissions are correct and that it can accept an HTTPS POST.
• Check that the script is not completing other functions before writing to the screen, such as writing to a database or sending emails.
• Please check to see if there are different processes that are used in your script for approvals, declines, or errors. Check each process to be sure that they will write to the screen before any other functions.
• Check if your script is using redirects immediately upon receipt of the response from our servers. Redirects are discouraged because they can potentially interfere with the process.

On affair, timeouts will occur that are outside of the control condition of your script or our servers. typical reasons for these timeouts include Internet traffic, your server is overloaded or malfunctioning, or Internet routing issues. Depending upon your waiter placement and what route is used to send data, it is possible that you may occasionally receive the message you are seeing . 53 The transaction type is invalid for ACH transactions. The transactionType value is not valid for ACH transactions. If payment type is bankAccount, transactionType cannot be set to captureOnlyTransaction. 54 The referenced transaction does not meet the criteria for issuing a credit. The referenced transaction does not meet the criteria for issuing a credit. It may be unsettled, an invalid type, the wrong currency, an invalid reference transaction ID or settled more than 120 days ago.
Consider applying for Expanded Credit-Return Capabilities if the merchant needs to refund transactions older than 120 days. 55 The sum of credits against the referenced transaction would exceed original debit amount. The transaction is rejected if the sum of this credit and prior credits exceeds the original debit amount. 56 Credit card transactions are not accepted by this merchant. The merchant processes eCheck.Net transactions only and does not accept credit cards. 57 An error occurred during processing. Please try again. This error is caused when a transaction is submitted with data that the credit card processor does not recognize or is unable to interpret. In most cases our system will prevent this from happening with front-end safeguards, but since every processor is unique in the way they handle data, some transactions could get through to the processor with invalid or missing data. Examples of these types of discrepancies include placing the incorrect number of characters in the Card Verification Value (Card Code), or sending non-alphanumeric characters in the Zip Code. 58 An error occurred during processing. Please try again. 59 An error occurred during processing. Please try again. 60 An error occurred during processing. Please try again. 61 An error occurred during processing. Please try again. 62 An error occurred during processing. Please try again. 63 An error occurred during processing. Please try again. If you receive an Error 63 repeatedly, please check that the Merchant Business country is set correctly. This is especially pertinent on accounts which use TSYS (formerly Vital or Visanet) as the payment processor, as we have to transmit a number of the Business Information fields on each Transaction attempt. TSYS/Vital/Visanet transactions will fail if all the information is not set correctly.
To update the Business Information details for your account:

• Login to the Merchant Interface at https://account.authorize.net
• Click Merchant Profile in the main left side menu
• Click Edit Business Information
• Update your Address, Phone Number, Fax Number, Products/Services Description, Web Site Address, and Shopping Cart Solution as necessary.
• Click Submit
• Click Continue to return to the Merchant Profile page.

If the Merchant Profile has your correct address-including the country-then you may need to contact your Merchant Service Provider to confirm that TSYS/Vital/Visanet has the compensate address for establishment . 64 The referenced transaction was not approved. This error is applicable to Wells Fargo SecureSource merchants only. Credits or refunds cannot be issued against transactions that were not authorized. 65 This transaction has been declined. The transaction was declined because the merchant configured their account through the Merchant Interface to reject transactions with certain values for a Card Code mismatch. 66 This transaction cannot be accepted for processing. Transaction was submitted using HTTP GET which does not meet payment gateway security guidelines. If you are using the SIM connection method, make sure your code is providing values for the SIM required fields listed below:

• • The sequence number of the transaction (x_fp_sequence)
  • The time when the sequence number was generated (x_fp_timestamp)
  • The Fingerprint Hash (x_fp_hash)

“ 67 The given transaction type is not supported for this merchant. This error code is applicable to merchants using the Wells Fargo SecureSource product only. This product does not allow transactions of type CAPTURE_ONLY. 68 The version parameter is invalid The value submitted in x_version was invalid. 69 The transaction type is invalid The value submitted in transactionType was invalid. 70 The transaction method is invalid. The value submitted in x_method was invalid. 71 The bank account type is invalid. The value submitted in accountType was invalid. 72 The authorization code is invalid. The value submitted in authCode was more than six characters in length. 73 The drivers license date of birth is invalid. The format of the value submitted in x_drivers_license_num was invalid. 74 The duty amount is invalid. The value submitted in duty failed format validation. 75 The freight amount is invalid. The value submitted in freight failed format validation. 76 The tax amount is invalid. The value submitted in tax failed format validation. 77 The SSN or tax ID is invalid. The value submitted in x_customer_tax_id failed validation. 78 The card code is invalid. The value submitted in cardCode failed format validation. 79 The drivers license number is invalid. The value submitted in x_drivers_license_num failed format validation. 80 The drivers license state is invalid. The value submitted in x_drivers_license_state failed format validation. 81 The requested form type is invalid. Invalid value for x_show_form. The merchant requested an integration method not compatible with the AIM API. 82 Scripts are only supported in version 2.5. The system no longer supports version 2.5; requests cannot be posted to scripts. 83 The requested script is either invalid or no longer supported. The system no longer supports version 2.5; requests cannot be posted to scripts. 84 The device type is invalid or missing. deviceType is either missing or invalid. deviceType is required when the retail element is submitted. Invalid value for deviceType. 85 The market type is invalid marketType is either missing or invalid. marketType is required when the retail element is submitted. Invalid value for marketType. 86 The Response Format is invalid Invalid value for x_response_format. 87 Transactions of this market type cannot be processed on this system. This can happen for four reasons:
1) You are attempting to process a type of transaction that your account is not designed for. An example would be using a card swipe machine to process transactions on an e-commerce or mail order/telephone order (MOTO) account.
2) You are passing an incorrect value for “marketType” parameter. For a merchant account processing “retail” type transactions, you would want to pass a value of “2”. The possible values for the “marketType” parameter can be found in our API Reference Guide.
3) Your Merchant Service Provider may be incorrectly setup for this account.
4) Your account may be configured incorrectly with an incorrect Merchant Service Provider or an incorrect MCC or SIC code. 88 Track1 data is not in a valid format. Invalid value for track1. 89 Track2 data is not in a valid format. Invalid value for track2. 90 ACH transactions cannot be accepted by this system. ACH transactions cannot be processed using a card present account. 91 Version 2.5 is no longer supported. 92 The gateway no longer supports the requested method of integration. This error can occur for several possible reasons, depending on which method your software uses to connect to your Authorize.Net account. Usually it is due to mixing methods in unsupported ways.
Advanced Integration Method (AIM) Suggestions:
1. When using AIM to integrate with Authorize.Net, the HTTP POST request must be made from a script located in a secure location on your server, and not through an HTML page. Submitting an AIM request from an unsecured HTML page may cause this error.
2. Be sure that your account settings allow delimited responses.
To check your settings:

• Login to the Merchant Interface at https://account.authorize.net/
• Click on Settings
• Click on Direct Response
• Change Delimited Response to “True”

3. Confirm that you are sending us the playing field x_delim_data, and that it is set to TRUE.
4. besides confirm that you are sending the field, x_relay_response, set to FALSE. otherwise, we will attempt to use any default option Relay Response or receipt links listed in your Response/Receipt URL settings in the Merchant Interface, which causes this erroneousness.
simple Integration Method ( SIM ) Suggestions :
1. You will receive this error if there are variables being sent that are not applicable to SIM. Two of the variables that are most normally incorrect include :
x_adc_relay_response – the variable name should be sent as x_relay_response
x_adc_relay_url – the variable name should be sent as x_relay_url.
2. You will receive this mistake if the proper fingermark hash variables are not being sent with the transaction request. The variables that need to be included ( with allow values ) :
x_fp_hash< x_fp_sequence x_fp_timestamp
These variables are used in creating and then passing the fingerprint hash with the transaction request. Authorize.Net then uses the evanesce variables and the store transaction key to attempt to create the same fingerprint hashish. If the two fingerprints match, we accept the transaction. If not, the transaction request is refused.
We highly recommend that you upgrade your connection method acting.
Please visit our Developer Center for up-to-date software documentation . " 93 A valid country is required. This code is applicable to Wells Fargo SecureSource merchants only. Country is a required field and must contain the value of a supported country. 94 The shipping state or country is invalid. This code is applicable to Wells Fargo SecureSource merchants only. 95 A valid state is required. This code is applicable to Wells Fargo SecureSource merchants only. 96 This country is not authorized for buyers. This code is applicable to Wells Fargo SecureSource merchants only. Country is a required field and must contain the value of a supported country. 97 This transaction cannot be accepted. Please use the Response Code 97 Tool Applicable only to the SIM API. Fingerprints are only valid for a short period of time. This code indicates that the transaction fingerprint has expired. 98 This transaction cannot be accepted. Part of the security feature for SIM (Server Integration Method) includes the generation of a fingerprint hash. The fingerprint hash is generated by a function in the scripting that uses five parameters to generate the fingerprint hash.

• The amount of the transaction;
• A sequence number—usually an invoice number generated by your scripting, but can be randomly generated as long as it doesn't repeat;
• Your server's timestamp, expressed in Greenwich Mean Time (GMT) or Coordinated Universal Time (UTC);
• Your account's Transaction Key; and
• Your account's API Login ID.

Any fingermark hashish can merely be used once in 24 hours .
If a customer fills in wrong information and the transaction is declined, they can not click Back and re-enter the information as this will attempt to use the same fingerprint hash in resubmitting the transaction request, which will result in error 98 .
The customer must be directed rear to the page that sets the come of the transaction request, then re-enter information from that compass point on . Applicable only to the SIM API. The transaction fingerprint has already been used. 99 This transaction cannot be accepted. Please use the Response Code 99 Tool. Applicable only to the SIM API. The server-generated fingerprint does not match the merchant-specified fingerprint in the x_fp_hash field. 100 The eCheck type parameter is invalid. Applicable only to eCheck.Net. The value specified in the echeckType field is invalid. 101 The given name on the account and/or the account type does not match the actual account. Applicable only to eCheck.Net. The specified name on the account and/or the account type do not match the NOC record for this account. 102 This request cannot be accepted. NOTE: This response is valid only for an integration method that has been sunset and is no longer available. If you encounter this error, please contact Merchant Support for assistance.
If you are receiving this error, it indicates that either x_password or x_tran_key is being submitted with your WebLink request. This represents a security risk as the password or transaction key could be viewed in your reservoir code .
We highly recommend that you upgrade your association method.

Please visit our Developer Center for up-to-date software documentation . A transaction key was submitted with this WebLink request. 103 This transaction cannot be accepted. This error is generated when your account is in "Password-Required Mode" and you are not sending a valid password, transaction key or hash fingerprint with your transaction request, which is a recommended security measure.
Please consider the following details when encountering this error:

• If you are using SIM, make sure you are using a valid transaction key to generate and send a fingerprint hash to us along with your transaction request.
• If you are using AIM please make sure you are posting the gateway defined field transactionKey.
• If you are using a third party shopping cart which uses AIM and are receiving this error, please check with your shopping cart provider to ask if your application can pass the transaction key to the Authorize.Net payment gateway.
• If you are using an older Authorize.Net account and you submit a password instead of a transaction key with your transactions, you may experience this error. Please ensure that you are posting a transaction key instead.
• Some shopping carts, for backwards compatibility with older connection methods, may provide the means to submit both a transaction key and a password. You should not use both the transaction key and the password simultaneously; doing so may also result in this error. We recommend using the transaction key instead of the password whenever possible, as transaction keys tend to be more secure than passwords. In such a situation, please leave the password field blankIf the shopping cart has a field for the password but no field for the transaction key, please put the transaction key in the password field. Our system will recognize and validate the transaction key properly.
  Also, while most shopping cart software will have a field for the transaction key, password, or both, some software may not. Please contact your shopping cart provider for details on how to upgrade to a more secure version of your shopping cart software.

• Chase Paymentech
• FDMS Nashville (formerly FDC)
• Global Payments (GPS)
• TSYS (formerly Vital)
• Wells Fargo (Verified by Visa only)

besides, this error can be received in the event that a special quality is included in the cardholder authentication rate. To resolve this write out, the special character must be URL encoded . This code is applicable only to merchants that include the cardholderAuthenticationValue in the transaction request. The CAVV for a Visa transaction or the AVV/UCAF for a Mastercard transaction is invalid or contains an invalid character. 118 The combination of card type, authentication indicator and cardholder authentication value is invalid. For example, when the Mastercard value for authenticationIndicator is 1, cardholderAuthenticationValue must be null. In this scenario, if a value is submitted for cardholderAuthenticationValue, the transaction fails validation and is rejected.
besides, verify that the merchant 's central processing unit supports Verified by Visa and Mastercard SecureCode authentication values through Authorize.Net .

• Chase Paymentech
• FDMS Nashville (formerly FDC)
• Global Payments (GPS)
• TSYS (formerly Vital)

• Log into the Merchant Interface at https://account.authorize.net/
• Click Settings in the main left side menu
• Click API Login and Transaction Key
• If an API login ID has already been generated, it will be visible here. If an API Login ID needs to be generated, you will want to enter the answer to your Secret Question in order to see the API Login ID.

• Set marketType to "0" to flag the transaction as e-commerce.
• Set transactionType to authCaptureTransaction or authOnlyTransaction.
• Specify both opaque data parameters.
• Do not include card number, expiration date, or track data.
• Do not include 3DS data.
• Ensure that you submit data that can be successfully decrypted.
• Only submit decrypted data that belongs to the merchant submitting the request.
• Encode the submitted data in Base64.

`` 154 Processing Apple Payments is not enabled for this merchant account. 155 This processor does not support this method of submitting payment data. 156 The cryptogram is either invalid or cannot be used in combination with other parameters. 165 This transaction has been declined. System void failed. CVV2 Code mismatch based on the CVV response and the merchant settings. 170 An error occurred during processing. Please contact the merchant. Concord EFS - Provisioning at the processor has not been completed. 171 An error occurred during processing. Please contact the merchant. Concord EFS - This request is invalid. 172 An error occurred during processing. Please contact the merchant. Concord EFS - The store ID is invalid. 173 An error occurred during processing. Please contact the merchant. Concord EFS - The store key is invalid. 174 The transaction type is invalid. Please contact the merchant. Concord EFS - This transaction type is not accepted by the processor. 175 This processor does not allow voiding of credits. Concord EFS - This transaction is not allowed. The Concord EFS processing platform does not support voiding credit transactions. Please debit the credit card instead of voiding the credit. 180 An error occurred during processing. Please try again. There are three different reasons that an Error 180 might occur:

1. There was an attempt to void a refund on a processor that does not allow that.
2. A merchant on the Concord EFS platform is attempting to pass AMEX CID, when they are not signed up to validate this value with AMEX.
3. Transactions submitted from test credit card numbers (both ours and others') by merchants on the TSYS payment processing platform, will return a response of: "(180) An error occurred during processing. Please try again. Invalid processor response format," rather than "(2) Declined. This transaction has been declined."

note that the TSYS payment process platform was once known as Vital or Visanet. On TSYS/Vital/Visanet, Error 180 is an valid reception indicate that a transaction was submitted and correctly received, but rejected due to using a test card number. If the processor is incorrectly configured, the answer will be something more generic like a response of 30, 34, or 35 . The processor response format is invalid. 181 An error occurred during processing. Please try again. The system-generated void for the original invalid transaction failed. (The original transaction included an invalid processor response format.)" 182 One or more of the sub-merchant values are invalid. 183 One or more of the required sub-merchant values are missing. 184 Invalid Token Requestor Name. 185 This transaction cannot be processed. Merchant is not configured for VPOS. 186 Invalid Token Requestor ID Length. 187 Invalid Token Requestor ECI Length. 191 This transaction has been declined. 192 An error occurred during processing. Please try again. 193 The transaction is currently under review. 195 One or more of the HTML type configuration fields do not appear to be safe. 200 This transaction has been declined This error code applies only to merchants on FDC Omaha. The credit card number is invalid. 201 This transaction has been declined This error code applies only to merchants on FDC Omaha. The expiration date is invalid. 202 This transaction has been declined This error code applies only to merchants on FDC Omaha. The transaction type is invalid. 203 This transaction has been declined This error code applies only to merchants on FDC Omaha. The value submitted in the amount field is invalid. 204 This transaction has been declined This error code applies only to merchants on FDC Omaha. The department code is invalid. 205 This transaction has been declined This error code applies only to merchants on FDC Omaha. The value submitted in the merchant number field is invalid. 206 This transaction has been declined. This error code applies only to merchants on FDC Omaha. The merchant is not on file. 207 This transaction has been declined This error code applies only to merchants on FDC Omaha. The merchant account is closed. 208 This transaction has been declined This error code applies only to merchants on FDC Omaha. The merchant is not on file. 209 This transaction has been declined This error code applies only to merchants on FDC Omaha. Communication with the processor could not be established. 210 This transaction has been declined This error code applies only to merchants on FDC Omaha. The merchant type is incorrect. 211 This transaction has been declined This error code applies only to merchants on FDC Omaha. The cardholder is not on file. 212 This transaction has been declined This error code applies only to merchants on FDC Omaha. The bank configuration is not on file. 213 This transaction has been declined This error code applies only to merchants on FDC Omaha. The merchant assessment code is incorrect. 214 This transaction has been declined This error code applies only to merchants on FDC Omaha. This function is currently unavailable. 215 This transaction has been declined This error code applies only to merchants on FDC Omaha. The encrypted PIN field format is invalid. 216 This transaction has been declined This error code applies only to merchants on FDC Omaha. The ATM term ID is invalid. 217 This transaction has been declined This error code applies only to merchants on FDC Omaha. This transaction experienced a general message format problem. 218 This transaction has been declined This error code applies only to merchants on FDC Omaha. The PIN block format or PIN availability value is invalid. 219 This transaction has been declined This error code applies only to merchants on FDC Omaha. The ETC void is unmatched. 220 This transaction has been declined This error code applies only to merchants on FDC Omaha. The primary CPU is not available. 221 This transaction has been declined This error code applies only to merchants on FDC Omaha. The SE number is invalid. 222 This transaction has been declined This error code applies only to merchants on FDC Omaha. Duplicate auth request (from INAS). 223 This transaction has been declined This error code applies only to merchants on FDC Omaha. This transaction experienced an unspecified error. 224 This transaction has been declined This error code applies only to merchants on FDC Omaha. Please re-enter the transaction. 225 This transaction cannot be processed. The transaction has an invalid dynamic currency conversion (DCC) action. 226 This transaction cannot be processed. Incomplete set of Dynamic Currency Conversion (DCC) parameters. 227 This transaction cannot be processed. Merchant is not configured for Dynamic Currency Conversion (DCC). 228 This transaction cannot be processed. Dynamic Currency Conversion (DCC) is not allowed for this transaction type. 229 Conversion rate for this card is available. 230 This transaction cannot be processed. Transaction could not be found. 231 This transaction cannot be processed. Incoming data is different than the referenced Dynamic Currency Conversion (DCC) transaction. 232 This transaction cannot be processed. Merchant is not configured for Dynamic Currency Conversion (DCC). 233 This transaction cannot be processed. Cannot perform Dynamic Currency Conversion (DCC) action on this transaction. 234 This transaction cannot be processed. This transaction has been voided. 235 This transaction cannot be processed. This transaction has been captured previously. 236 This transaction cannot be processed. Dynamic Currency Conversion (DCC) data for the referenced transaction is not available. 237 This transaction cannot be processed. The referenced transaction has expired. 238 This transaction cannot be processed. The transaction version does not support Dynamic Currency Conversion (DCC). 239 This transaction cannot be processed. The response format for this transaction does not support Dynamic Currency Conversion (DCC). 240 This transaction cannot be processed. Currency for Dynamic Currency Conversion (DCC) transactions must be US dollars. 241 This transaction cannot be processed. Invalid response from card processor. 242 This transaction cannot be processed. Recurring billing flag not allowed on Dynamic Currency Conversion (DCC). 243 Recurring billing is not allowed for this eCheck.Net type. The combination of values submitted for recurringBilling and echeckType is not allowed. 244 This eCheck.Net type is not allowed for this Bank Account Type. The combination of values submitted for accountType and echeckType is not allowed. 245 This eCheck.Net type is not allowed when using the payment gateway hosted payment form. The value submitted for echeckType is not allowed when using the payment gateway hosted payment form. 246 This eCheck.Net type is not allowed. This error also occurs if you submit a check number for your WEB, TEL, CCD, or PPD eCheck.Net transaction. Check numbers are only valid for ARC and BOC eCheck.Net transactions. See the eCheck.Net User Guide for details on eCheck.Net transaction types and requirements. The merchant's payment gateway account is not enabled to submit the eCheck.Net type. 247 This eCheck.Net type is not allowed. The combination of values submitted for transactionType and echeckType is not allowed. 248 The check number is invalid. Invalid check number. Check numbers can only consist of letters and numbers, up to 15 characters. 250 This transaction has been declined. This transaction was submitted from a blocked IP address. 251 This transaction has been declined. This transaction was submitted from a blocked IP address. The transaction was declined as a result of triggering a Fraud Detection Suite filter. 252 Your order has been received. Thank you for your business! The transaction was accepted, but is being held for merchant review. The merchant may customize the customer response in the Merchant Interface. 253 Your order has been received. Thank you for your business! The transaction was accepted and was authorized, but is being held for merchant review. The merchant may customize the customer response in the Merchant Interface. 254 This transaction has been declined. The transaction was declined after manual review. 260 Reversal not supported for this transaction type. Only authorizations and credits can be reversed. 261 An error occurred during processing. Please try again. The transaction experienced an error during sensitive data encryption and was not processed. Please try again. 262 The PayformMask is invalid. 265 This transaction cannot be processed. The transaction was submitted with an invalid Solution ID. For details on how to register and submit a Solution ID, please see The Solution ID Implementation Guide. 270 Line item %1 is invalid. A value submitted in lineItem for the item referenced is invalid. 271 The number of line items submitted is not allowed. A maximum of %1 line items can be submitted. The number of line items submitted in lineItem exceeds the allowed maximum of 30. 280 The auction platform name is invalid. 281 The auction platform ID is invalid. 282 The auction listing type is invalid. 283 The auction listing ID is invalid. 284 The auction seller ID is invalid. 285 The auction buyer ID is invalid. 286 One or more required auction values were not submitted. 287 The combination of auction platform ID and auction platform name is invalid. 288 This transaction cannot be accepted. 289 This processor does not accept zero dollar authorization for this card type. 290 There is one or more missing or invalid required fields. 295 The amount of this request was only partially approved on the given prepaid card. An additional payment is required to fulfill the balance of this transaction. 296 The specified SplitTenderID is invalid. 297 Transaction ID and Split Tender ID cannot both be used in the same request. 298 This order has already been released or voided therefore new transaction associations cannot be accepted. 300 The device ID is invalid. Invalid deviceId value. 301 The device batch ID is invalid. Invalid batchId value. 302 The reversal flag is invalid. Invalid x_reversal value. 303 The device batch is full. Please close the batch. The current device batch must be closed manually from the POS device. 304 The original transaction is in a closed batch. The original transaction has been settled and cannot be reversed. 305 The merchant is configured for auto-close. This merchant is configured for auto-close and cannot manually close batches. 306 The batch is already closed. 307 The reversal was processed successfully. 308 Original transaction for reversal not found. The transaction submitted for reversal was not found. 309 The device has been disabled. 310 This transaction has already been voided. 311 This transaction has already been captured. 312 The specified security code was invalid. The SIM hosted payment form features a Security Code option (sometimes called CAPTCHA) used to confirm that the payment is being entered by a human being. This feature helps protect your site from automated scripts that may try to test credit card numbers through the payment form.
The Security Code works by generating an prototype that contains random numbers and letters that can not be read by scripts. The customer is then prompted to enter the letters and numbers precisely as they appear in the image. If the customer enters the decline Security Code, the transaction is accepted as valid .
erroneousness 312 indicates that the customer had entered the wrong Security Code. Should this error occur, a fresh Security Code is generated, and the customer is prompted to try again until they are successful .
To turn off the Security Code option :

• Login into the Merchant Interface at https://account.authorize.net/.
• Click Account from the main toolbar.
• Click Settings in the main left side menu.
• Click Payment Form.
• Click Form Fields.
• Deselect the box labeled "Require the Security Code feature on the Payment Form."
• Click Submit to save the settings.

note : When using Simple Checkout, the customer is always required to verify a Security Code. flush if the Security Code is disabled from the payment human body, the customer is required to verify a Security Code on the Simple Checkout regulate page . 313 A new security code was requested. The SIM hosted payment form features a Security Code option (sometimes called CAPTCHA) used to confirm that the payment is being entered by a human being. This feature helps protect your site from automated scripts that may try to test credit card numbers through the payment form.
The Security Code works by generating an trope that contains random numbers and letters that can not be read by scripts. The customer is then prompted to enter the letters and numbers precisely as they appear in the image. If the customer enters the correct Security Code, the transaction is accepted as valid .
If they enter an faulty value, the customer is prompted to try again until they are successful.

To turn off the Security Code choice :

• Log into the Merchant Interface at https://account.authorize.net/.
• Click Account from the main toolbar.
• Click Settings in the main left side menu.
• Click Payment Form.
• Click Form Fields.
• Deselect the box labeled "Require the Security Code feature on the Payment Form."
• Click Submit to save the settings.

note : When using Simple Checkout, the customer is always required to verify a Security Code. even if the Security Code is disabled from the payment phase, the customer is required to verify a Security Code on the Simple Checkout order page . 314 This transaction cannot be processed. 315 The credit card number is invalid. This is a processor-issued decline. 316 Credit card expiration date is invalid. This is a processor-issued decline. 317 The credit card has expired. This is a processor-issued decline. 318 A duplicate transaction has been submitted. This is a processor-issued decline. 319 The transaction cannot be found. This is a processor-issued decline. 320 The device identifier is either not registered or not enabled. 325 The request data did not pass the required fields check for this application. The request is missing one or more required fields. Merchants processing transactions via one of the following processors (AIBMS UK, Barclays, Cardnet, HBOS, HSBC, Streamline, FdiAus and Westpac) are required to submit the following billing information fields:

• First Name (firstName)
• Last Name (lastName)
• Address (address)
• City (city)
• State (state)
• Postal Code
• Country (country)
• Email Address (email)

NOTE: State and Postal Code are optional if the placard address is not in the U.S. or Canada. If the address is in the U.S. or Canada, the two-digit State/Province code must be provided, along with the Zip/Postal Code. '' 326 The request field(s) are either invalid or missing. 327 The void request failed. Either the original transaction type does not support void, or the transaction is in the process of being settled. 328 A validation error occurred at the processor. 330 V.me transactions are not accepted by this merchant. 331 The x_call_id value is missing. The x_call_id value is missing. 332 The x_call_id value is not found or invalid. The x_call_id value is not found or invalid. 333 A validation error was returned from V.me. 334 The V.me transaction is in an invalid state. 339 Use x_method to specify method or send only x_call_id or card/account information. Use x_method to specify method or send only x_call_id or card information. 340 V.me by Visa does not support voids on captured or credit transactions. Please allow the transaction to settle, then process a refund for the captured transaction. 341 The x_discount value is invalid. The x_discount value is invalid. 342 The x_giftwrap value is invalid. The x_giftwrap value is invalid. 343 The x_subtotal value is invalid. The x_subtotal value is invalid. 344 The x_misc value is invalid. The x_misc value is invalid. 350 Country must be a valid two or three-character value if specified. 351 Employee ID must be 1 to %x characters in length. 355 An error occurred while parsing the EMV data. 356 EMV-based transactions are not currently supported for this processor and card type. 357 Opaque Descriptor is required. 358 EMV data is not supported with this transaction type. 359 EMV data is not supported with this market type. 360 An error occurred while decrypting the EMV data. 361 The EMV version is invalid. 362 The EMV version is required. 363 The POS Entry Mode value is invalid. 370 Signature data is too large. 371 Signature must be PNG formatted data. 375 Terminal/lane number must be numeric. 380 KSN is duplicated. 901 This transaction cannot be accepted at this time due to system maintenance. Please try again later. 2000 Need payer consent. The value of the secureAcceptanceURL field, provided in Authorization Only or Authorization and Capture service calls, is required for the follow-on calls such as Authorization Only, Continued and Authorization and Capture, Continued. 2001 PayPal transactions are not accepted by this merchant. 2002 PayPal transactions require x_version of at least 3.1. PayPal transactions require that the field x_version be set to 3.1 2003 Request completed successfully 2004 Success URL is required. PayPal transactions require valid URL for success_url 2005 Cancel URL is required. PayPal transactions require valid URL for cancel_url 2006 Payer ID is required. 2007 This processor does not accept zero dollar authorizations. 2008 The referenced transaction does not meet the criteria for issuing a Continued Authorization. 2009 The referenced transaction does not meet the criteria for issuing a Continued Authorization w/ Auto Capture. 2100 PayPal transactions require valid URL for success_url PayPal transactions require valid URL for success_url 2101 PayPal transactions require valid URL for cancel_url PayPal transactions require valid URL for cancel_url 2102 Payment not authorized. Payment has not been authorized by the user. 2103 This transaction has already been authorized. 2104 The totals of the cart item amounts do not match order amounts. Be sure the total of the payment detail item parameters add up to the order total. 2105 PayPal has rejected the transaction.Invalid Payer ID. 2106 PayPal has already captured this transaction. 2107 PayPal has rejected the transaction. This Payer ID belongs to a different customer. 2108 PayPal has rejected the transaction. x_paypal_hdrimg exceeds maximum allowable length. The field x_paypal_hdrimg exceeds maximum allowable length. 2109 PayPal has rejected the transaction. x_paypal_payflowcolor must be a 6 character hexadecimal value. The field x_paypal_payflowcolor must be a 6 character hexadecimal value.