Follow

List of Credit Card Result Codes

Below is a list of Result Codes you may see when trying to Process a payment in DASH and what the Code means.

             RESULT  RESPMSG and Explanation
 
                      0        Approved.
 
                      1        User authentication failed. Error is caused by one or more of the following:
Login information is incorrect. Verify that USER, VENDOR, PARTNER, and PASSWORD have been entered correctly. VENDOR is your merchant ID and USER is the same as VENDOR unless you created a Payflow Pro user. All fields are case sensitive. Invalid Processor information entered. Contact merchant bank to verify. "Allowed IP Address" security feature implemented. The transaction is coming from an unknown IP address. See PayPal Manager online help for details on how to use Manager to update the allowed IP addresses. You are using a test (not active) account to submit a transaction to the live PayPal servers. Change the host address from the test server URL to the live server URL.
                                  
                      2        Invalid tender type. Your merchant bank account does not support the following credit card type that was submitted.
                              
                      3        Invalid transaction type. Transaction type is not appropriate for this transaction. For example, you cannot credit an authorization-only transaction.
                              
                      4        Invalid amount format. Use the format: “#####.##” Do not include currency symbols or commas.
                      5        Invalid merchant information. Processor does not recognize your merchant account information. Contact your bank account acquirer to resolve this problem.
                              
                      6        Invalid or unsupported currency code
                      7        Field format error. Invalid information entered. See RESPMSG.
                      8        Not a transaction server
                      9        Too many parameters or invalid stream
                      10       Too many line items
                      11       Client time-out waiting for response
                      12       Declined. Check the credit card number, expiration date, and transaction information to make sure they were entered correctly. If this does not resolve the problem, have the customer call their card issuing bank to resolve.
                        
                      13       Referral. Transaction cannot be approved electronically but can be approved with a and submit a manual Voice Authorization transaction.
                                  
                      19       Original transaction ID not found. The transaction ID you entered for this
                               transaction is not valid. See RESPMSG.
                      20       Cannot find the customer reference number
      
              22         Invalid ABA number
              23         Invalid account number. Check credit card number and re-submit.
              24         Invalid expiration date. Check and re-submit.
              25         Invalid Host Mapping. Error is caused by one or more of the following:
You are trying to process a tender type such as Discover Card, but you are not set up with your merchant bank to accept this card type. You are trying to process an Express Checkout transaction when your account is not set up to do so. Contact your account holder to have Express Checkout added to your account.
                   
              26         Invalid vendor account. Login information is incorrect. Verify that USER, VENDOR, PARTNER, and PASSWORD have been entered correctly. VENDOR is your merchant ID and USER is the same as VENDOR unless you created a Payflow Pro user. All fields are case sensitive.
        
              27         Insufficient partner permissions
              28         Insufficient user permissions
              29         Invalid XML document. This could be caused by an unrecognized XML tag or a bad XML format that cannot be parsed by the system.
                        
              30         Duplicate transaction
              31         Error in adding the recurring profile
              32         Error in modifying the recurring profile
              33         Error in canceling the recurring profile
              34         Error in forcing the recurring profile
              35         Error in reactivating the recurring profile
              36         OLTP Transaction failed
              37         Invalid recurring profile ID
              50         Insufficient funds available in account
              51         Exceeds per transaction limit
              99         General error. See RESPMSG.
              100        Transaction type not supported by host
              101        Time-out value too small
              102        Processor not available
              103        Error reading response from host
                      104      Timeout waiting for processor response. Try your transaction again.
                      105      Credit error. Make sure you have not already credited this transaction, or that this transaction ID is for a creditable transaction. (For example, you cannot credit an authorization.)
                       
                      106      Host not available
                      107      Duplicate suppression time-out
                      108      Void error. See RESPMSG. Make sure the transaction ID entered has not already been voided. If not, then look at the Transaction Detail screen for this transaction to see if it has settled. (The Batch field is set to a number greater than zero if the transaction has been settled). If the transaction has already settled, your only recourse is a reversal (credit a payment or submit a payment for a credit).
                     
                      109      Time-out waiting for host response
                      110      Referenced auth (against order) Error
                      111      Capture error. Either an attempt to capture a transaction that is not an authorization transaction type, or an attempt to capture an authorization transaction that has already been captured.
                          
                    112      Failed AVS check. Address and ZIP code do not match. An authorization may still exist on the cardholder’s account.
                              
                      113      Merchant sale total will exceed the sales cap with current transaction. ACH transactions only.
                      114      Card Security Code (CSC) Mismatch. An authorization may still exist on the cardholder’s account.
                      115      System busy, try again later
                      116      PayPal internal error. Failed to lock terminal number
                      117      Failed merchant rule check. One or more of the following three failures occurred: An attempt was made to submit a transaction that failed to meet the security settings specified on the PayPal Manager Security Settings page. If the transaction exceeded the
 Maximum Amount security setting, then no values are returned for AVS or CSC.
AVS validation failed. The AVS return value should appear in the RESPMSG.
CSC validation failed. The CSC return value should appear in the RESPMSG.
                  
                      118      Invalid keywords found in string fields
                      120      Attempt to reference a failed transaction
                      121      Not enabled for feature
                      122      Merchant sale total will exceed the credit cap with current transaction. ACH transactions only.
              125        Fraud Protection Services Filter — Declined by filters
              126        Fraud Protection Services Filter — Flagged for review by filters
                         Important Note: Result code 126 indicates that a transaction triggered a fraud filter. This is not an error, but a notice that the transaction is in a review status. The
transaction has been authorized but requires you to review and to manually accept the transaction before it will be allowed to settle.
                         Result code 126 is intended to give you an idea of the kind of transaction that is
                         considered suspicious to enable you to evaluate whether you can benefit from using the Fraud Protection Services.
To eliminate result 126, turn the filters off.
                         For more information, see the Fraud Protection Services documentation for your
                         payments solution. It is available on the PayPal Manager Documentation page.
             
              127        Fraud Protection Services Filter — Not processed by filters
              128        Fraud Protection Services Filter — Declined by merchant after being flagged for review by filters
              132        Card has not been submitted for update
              133        Data mismatch in HTTP retry request
              150        Issuing bank timed out
              151        Issuing bank unavailable
              200        Reauth error
              201        Order error
              600        Cybercash Batch Error
              601        Cybercash Query Error
              1000       Generic host error. This is a generic message returned by your credit card processor. The RESPMSG will contain more information describing the error.
                        
              1001       Buyer Authentication Service unavailable
              1002       Buyer Authentication Service — Transaction timeout
              1003       Buyer Authentication Service — Invalid client version
              1004       Buyer Authentication Service — Invalid timeout value
              1011       Buyer Authentication Service unavailable
              1012       Buyer Authentication Service unavailable
              1013       Buyer Authentication Service unavailable
 
                      1014     Buyer Authentication Service — Merchant is not enrolled for Buyer Authentication Service (3-D Secure).
                      1016     Buyer Authentication Service — 3-D Secure error response received. Instead of receiving a PARes response to a Validate Authentication transaction, an error response was received.
                       
                      1017     Buyer Authentication Service — 3-D Secure error response is invalid. An error response is received and the response is not well formed for a Validate Authentication
     
                      1021     Buyer Authentication Service — Invalid card type
                      1022     Buyer Authentication Service — Invalid or missing currency code
                      1023     Buyer Authentication Service — merchant status for 3D secure is invalid
                      1041     Buyer Authentication Service — Validate Authentication failed: missing or
                               invalid PARES
                      1042     Buyer Authentication Service — Validate Authentication failed: PARES format is invalid
                              
                      1043     Buyer Authentication Service — Validate Authentication failed: Cannot find
                               successful Verify Enrollment
                      1044     Buyer Authentication Service — Validate Authentication failed: Signature
                               validation failed for PARES
                      1045     Buyer Authentication Service — Validate Authentication failed: Mismatched or invalid amount in PARES
                              
                      1046     Buyer Authentication Service — Validate Authentication failed: Mismatched or invalid acquirer in PARES
                              
                      1047     Buyer Authentication Service — Validate Authentication failed: Mismatched or invalid Merchant ID in PARES
                              
                      1048     Buyer Authentication Service — Validate Authentication failed: Mismatched or invalid card number in PARES
                              
                      1049     Buyer Authentication Service — Validate Authentication failed: Mismatched or invalid currency code in PARES
                              
                      1050     Buyer Authentication Service — Validate Authentication failed: Mismatched or invalid XID in PARES
                              
                      1051     Buyer Authentication Service — Validate Authentication failed: Mismatched or invalid order date in PARES
                      1052     Buyer Authentication Service — Validate Authentication failed: This PARES was already validated for a previous Validate Authentication transaction
                                                                                                                     
 
    RESULT Values for Communications Errors
 
            A RESULT value less than zero indicates that a communication error occurred. In this case, no transaction is attempted. A value of -1 or -2 usually indicates a configuration error caused by an incorrect URL or by configuration issues with your firewall. A value of -1 or -2 can also be possible if the PayPal servers are unavailable, or an incorrect server/socket pair has been specified. A value of -1 can also result when there are internet connectivity errors. Contact customer support regarding any other errors. For information on firewall configuration, see Chapter 2, “Downloading, Installing, and Activating.” Details of the response message may vary slightly from that shown in the table, depending on your SDK integration.
 
             TABLE 6.3        RESULT values for communications errors
 
               RESULT          Description
               -1              Failed to connect to host
               -2              Failed to resolve hostname
               -5              Failed to initialize SSL context
               -6              Parameter list format error: & in name
               -7              Parameter list format error: invalid [ ] name length clause
               -8              SSL failed to connect to host
               -9              SSL read failed
               -10             SSL write failed
               -11             Proxy authorization failed
               -12             Timeout waiting for response
               -13             Select failure
               -14             Too many connections
               -15             Failed to set socket options
               -20             Proxy read failed
                                                                                      
 
                                                Responses to Transaction Requests
                                                                                         
                                                       RESULT Values and RESPMSG Text
 
TABLE 6.3 RESULT values for communications errors(Continued)
 
 RESULT    Description
 -21       Proxy write failed
 -22       Failed to initialize SSL certificate
 -23       Host address not specified
 -24       Invalid transaction type
 -25       Failed to create a socket
 -26       Failed to initialize socket layer
 -27       Parameter list format error: invalid [ ] name length clause
 -28       Parameter list format error: name
 -29       Failed to initialize SSL connection
 -30       Invalid timeout value
 -31       The certificate chain did not validate, no local certificate found
 -32       The certificate chain did not validate, common name did not match URL
 - 40      Unexpected Request ID found in request.
 - 41      Required Request ID not found in request
 -99       Out of memory
 -100      Parameter list cannot be empty
 -103      Context initialization failed
 -104      Unexpected transaction state
 -105      Invalid name value pair request
 -106      Invalid response format
 -107      This XMLPay version is not supported
 -108      The server certificate chain did not validate
 -109      Unable to do logging
 -111      The following error occurred while initializing from message file: <Details of
           the error message>
 -113      Unable to round and truncate the currency value simultaneously

 

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk