WIXLIB

Reason Codes for the Simple Order API

2021. Cybersource Corporation. All rights reserved.Cybersource Corporation (Cybersource) furnishes this document and the software described in this document underthe applicable agreement between the reader of this document (You) and Cybersource (Agreement). You may use thisdocument and/or software only in accordance with the terms of the Agreement. Except as expressly set forth in theAgreement, the information contained in this document is subject to change without notice and therefore should not beinterpreted in any way as a guarantee or warranty by Cybersource. Cybersource assumes no responsibility or liabilityfor any errors that may appear in this document. The copyrighted software that accompanies this document is licensedto You for use only in strict accordance with the Agreement. You should read the Agreement carefully before using thesoftware. Except as permitted by the Agreement, You may not reproduce any part of this document, store this documentin a retrieval system, or transmit this document, in any form or by any means, electronic, mechanical, recording, orotherwise, without the prior written consent of Cybersource.For Government or defense agencies: Use, duplication, or disclosure by the Government or defense agencies is subject torestrictions as set forth the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and in similarclauses in the FAR and NASA FAR Supplement.For civilian agencies: Use, reproduction, or disclosure is subject to restrictions set forth in subparagraphs (a) through (d)of the Commercial Computer Software Restricted Rights clause at 52.227-19 and the limitations set forth in CybersourceCorporation's standard commercial agreement for this software. Unpublished rights reserved under the copyright laws ofthe United States.Authorize.Net, eCheck.Net, and The Power of Payment are registered trademarks of Cybersource Corporation.Cybersource, Cybersource Payment Manager, Cybersource Risk Manager, Cybersource Decision Manager, andCybersource Connect are trademarks and/or service marks of Cybersource Corporation. Visa, Visa International,Cybersource, the Visa logo, and the Cybersource logo are the registered trademarks of Visa International in the UnitedStates and other countries. All other trademarks, service marks, registered marks, or registered service marks are theproperty of their respective owners.Version: 21.02Reason Codes for the Simple Order API 2

ContentsReason Codes for the Simple Order API.4Reason Codes for the Simple Order API - Contents 3

Reason Codes for the Simple Order APIImportant: Response fields and reason codes can be added at any time. Therefore: You must parse the response data according to the names of the fields instead of the fieldorder in the response message. For more information about parsing response fields, see thedocumentation for your client. Your error handler must be able to process new reason codes without problems. Your error handler must use the decision field to determine the result if it receives a reasoncode that it does not recognize.The following table describes the reason codes that are returned by the Simple Order API.Table 1. Reason CodesReason CodeDescription100Transaction was successful.101Request is missing one or more required fields. Examine the responsefields missingField 0 through missingField N to identify whichfields are missing. Resend the request with all the required fields.102104105110AIBMS: If the ccAuthReply processorResponse value is 08,you can accept the transaction if the customer provides you withidentification.One or more fields in the request contain invalid data. Examine theresponse fields invalidField 0 through invalidField N to identifywhich fields are invalid. Resend the request with valid data.Merchant reference code for this authorization request matches themerchant reference code for another authorization request that yousent within the past 15 minutes. Resend this request with a uniquemerchant reference code.Merchant transaction identifier (MTI) sent with this request hasalready been used in the past 60 days. Resend this request with aunique MTI.Only a partial amount was approved.Reason Codes for the Simple Order API - Reason Codes for the Simple Order API 4

Table 1. Reason Codes (continued)Reason CodeDescription150System error. You must design your transaction management systemto include a way to correctly handle system errors. Depending onwhich payment processor is handling the transaction, the errormight indicate a valid Cybersource system error, or it might indicatea processor rejection because of invalid data. In either case, do notdesign your system to endlessly try to resend a transaction when asystem error occurs. See the documentation for the Cybersource client(SDK) that you are using for important information about how tohandle system errors and retries.151152153200201202203204Request was received but a server timeout occurred. This error doesnot include timeouts that occur between the client and the server.To avoid duplicating the transaction, do not resend the request untilyou have reviewed the transaction status in the Business Center. Seethe documentation for your Cybersource client for information abouthandling retries in the case of system errors.Request was received, but a service did not finish running in time.To avoid duplicating the transaction, do not resend the request untilyou have reviewed the transaction status in the Business Center. Seethe documentation for your Cybersource client for information abouthandling retries in the case of system errors.Your account is not enabled for the OCT service. Contact customersupport to have your account enabled for this service.Authorization request was approved by the issuing bank but declinedbecause the address verification system (AVS) could not verify it. Youcan capture the authorization, but consider reviewing the order forpossible fraud.Issuing bank has questions about the request.Authorization: You cannot receive an authorization codeprogrammatically, but you might receive one verbally by callingthe processor. Call your processor to possibly receive a verbalauthorization. For contact phone numbers, refer to your merchantbank information.Card is expired. You might also receive this value if the expiration datethat you provided does not match the date that the issuing bank hason file. Request a different card or other form of payment.Card was declined. No other information was provided by the issuingbank. Request a different card or other form of payment.Account does not contain sufficient funds. Request a different card orother form of payment.Reason Codes for the Simple Order API - Reason Codes for the Simple Order API 5

Table 1. Reason Codes (continued)Reason CodeDescription205Card is lost or stolen. Review this transaction manually to ensure thatyou submitted the correct information.208Card-Not-Present Transaction: Card is inactive or not authorized forcard-not-present transactions. Request a different card or other formof g bank is unavailable. Wait a few minutes and resend therequest.Card-Present Transaction: Card is inactive, or the PIN is missing orincorrect. Ask the customer to re-enter the PIN or provide a differentform of payment.CVN did not match. Request a different card or other form of payment.Account reached the credit limit, or the transaction amount exceedsthe approved limit. Request a different card or other form of payment.CVN is invalid. Re-enter the CVN or request a different form ofpayment.EMV transaction was rejected. Resubmit the request with chip andPIN.Account is in fraud watch status.Customer's name matched an entry on the processor’s negative file.Review the order and contact the payment processor.Authorization request was approved by the issuing bank but declinedbecause CVN could not be verified. You can capture the authorization,but consider reviewing the order for possible fraud.Account number is invalid. Request a different card or other form ofpayment.Payment processor does not accept the card type. Contact yourmerchant bank to confirm that your account is set up to receive thecard type.Processor declined the card. For more information about the decline,search for the transaction in the Business Center and view thetransaction details. Request a different card or other form of payment.Information in your account is incorrect. Do not resend the request.Contact customer support to correct the information in your account.Reason Codes for the Simple Order API - Reason Codes for the Simple Order API 6

Table 1. Reason Codes (continued)Reason CodeDescription235Capture: The requested capture amount exceeds the authorizedamount. Send a new authorization and capture request for the newamount.236237238239240241242243244246247PIN Debit Purchase: Transaction amount exceeds the approved limit.Send a new PIN-debit purchase request for a lower amount.Processor failed. Wait a few minutes and resend the request.Transaction was already captured.Transaction was already reversed.Requested transaction amount does not match the previoustransaction amount. Correct the amount and resend the request.Card type is invalid or does not correlate with the payment cardnumber. Confirm that the card type correlates with the payment cardnumber specified in the request, then resend the request.PIN Debit: Processor declined the card. For more information aboutthe decline, search for the transaction in the Business Center and viewthe transaction details.Other Payment Method: Request ID is invalid. Request a newauthorization and, if successful, proceed with the capture.Capture: You requested a capture, but there is no corresponding,unused authorization. This situation occurs when there is nopreviously successful authorization request or when the previouslysuccessful authorization has already been captured. Request a newauthorization, and if successful, proceed with the capture.Reversal: You requested a reversal, but there is no correspondingtransaction or the transaction specified by the authorization code hasalready been settled.Transaction is already settled or reversed.Account number did not pass a verification check.One of the following: Capture or credit cannot be voided because the capture or creditinformation has already been submitted to your processor. You requested a void for a type of transaction that cannot bevoided.You requested a credit for a capture that was previously voided.Reason Codes for the Simple Order API - Reason Codes for the Simple Order API 7