Credit card decline codes (Paysafe Payments)

Was this article helpful?
4 out of 4 found this helpful
Follow
If you've ever received an error or declined code when using Paysafe Payments and wished you had more detailed information, this article is for you. Below, you'll find explanations of decline codes you may have encountered, and also potential solutions and resolutions to the issue at hand.
 
Declines are made by the card-issuing bank, not your software. If your client does not believe their card should have declined, please advise them to call the 1-800 on the back of the card for more information. 

If you receive a decline that is not listed on this page you can see an exhaustive list of codes here.

 

Decline 1007

An internal error occurred. Please retry the transaction.

Cause

After the transaction was sent to the processor, no response was received. This probably occurred because the processor’s gateway is temporarily down.

Resolution

Connectivity problems, if they do occur, are usually short lived. You can retry  the transaction and it should process successfully. If the problem persists, contact Paysafe Payments.

 

Decline 3004

Zip/postal code must be provided for AVS Check request. 

Cause

This decline code will appear if Paysafe has applied additional AVS authentication.

Resolution

Only way to remove this setting is to email customersupport@paysafe.com and request the feature turned off. Cannot be done via phone.

 


Decline 3005

You submitted an incorrect value for the cvd parameter with your request. Please verify this parameter and retry the transaction.

Cause

This error occurs when an invalid value is included for the cvd parameter for a transaction request. Valid values must be 3 or 4 digits only. If alphabetical characters are submitted for this parameter or if it is left empty, then this error is returned.

Resolution

Verify that the correct value is supplied with the transaction, and retry it.

 


Decline 3006

You submitted an expired credit card number with your request. Please verify this parameter and retry the request.

Cause

This error occurs when you have attempted a transaction using an expired credit card.

Resolution

Verify that the card number is entered correctly. Or, your customer may have inadvertently used an expired credit card. If so, request a different credit card number. Otherwise, there is no resolution for this error.

 


Decline 3007

Your request has failed the AVS check. Note that the amount has still been reserved on the customer’s card and will be released in 3–5 business days. Please ensure the billing address is accurate before retrying the transaction.

Cause

This error occurs when AVS fails on a transaction, but the transaction would otherwise have been successful.

When error 3007 occurs, the transaction amount is reserved on the credit card (i.e., it is now considered unavailable for any other transaction), even though the transaction itself fails. Typically, the issuing bank reserves that amount for 3–5 days. If, for example, you retried a $100 transaction five times despite receiving error 3007, the cardholder would have $500 reserved on their credit card, even though none of the transactions were successful. It is important when receiving this error for the first time, to ensure that the address information entered for the transaction is the same information as the cardholder’s mailing address before retrying.

Resolution

Ensure that the zip code entered for the transaction is the same zip code that the issuing bank has in the mailing address of the cardholder. Retry the transaction.

 


Decline 3008

You submitted a card type for which the merchant account is not configured.

Cause

The transaction request was sent with a credit card type for which the account is not configured. For example, you may be set up to process Visa and MasterCard, and you submitted a transaction for American Express.

Resolution

Validate the transaction request, ensuring that an acceptable card type is included in it. Contact your account manager if you want to add new card types to your account.

 


Decline 3009

Your request has been declined by the issuing bank.

Cause

The issuing bank refused authorization on this transaction for one of the following reasons:

  1. There is a bank policy regarding online transactions. For example, some banks regard Internet transactions as “high risk” and may have a policy against them.
  2. There is a bank security policy that has declined the transaction based on a preset anti-fraud algorithm.

Resolution

Do not retry the transaction. Due to one or more of the causes mentioned above, this transaction was declined. This is not an error or failure on the part of the transaction processor, but rather a bank policy issue that has declined the transaction. There is no action to take on your part.

 


Decline 3012

Your request has been declined by the issuing bank because the credit card expiry date submitted is invalid.

Cause

This response code is returned when an invalid credit card expiry date is used for the transaction. The expiry date was included and formatted correctly, but the bank has determined that it is invalid for the card number submitted.

Resolution

Verify that the credit card and expiry date used are included and are valid. Then retry the transaction.

 


Decline 3013

Your request has been declined by the issuing bank due to problems with the credit card account.

Cause

Your customer attempted a transaction using a card to which no account is linked.

Resolution

The customer should contact the card issuer to determine what is wrong with the card. The situation must be corrected before retrying the transaction.

 


Decline 3015

The bank has requested that you process the transaction manually by calling the cardholder’s credit card company.

Cause

The authorization for this transaction failed because the bank requested that you process this transaction manually by calling your customer’s credit card company.

Resolution

Do not retry the transaction. If you want to process this transaction, contact your customer’s credit card company for further investigation.

 


Decline 3016

The bank has requested that you retrieve the card from the cardholder – it may be a lost or stolen card.

Cause

The authorization for this transaction failed because the card used may be lost or stolen and the bank has requested that you retrieve it.

Resolution

Do not retry the transaction. There is no resolution for this error.

 


Decline 3017

You submitted an invalid credit card number with your request. Please verify this parameter and retry the transaction.

Cause

This response code is returned when an invalid card is used for the transaction. The card parameter was included and formatted correctly, but the bank has determined that the card number is invalid.

Resolution

The card number may have been entered incorrectly. Verify the card number and retry the transaction.

 


Decline 3019

Your request has failed the CVD check. Please note that the amount has still been reserved on the customer’s card and will be released in 3–5 business days. Please ensure the CVD value is accurate before retrying the transaction.

Cause

The CVD value is the 3- or 4-digit security code that appears on the card following the card number. This code does not appear on imprints. The authorization for this transaction failed because the CVD check failed.

Resolution

Note that if the cvdIndicator parameter was included in the request, the cvd parameter is mandatory. Verify the value entered for the cvd parameter and retry the request. If the error reoccurs, contact Paysafe Payments.

 

 

Decline 3022

The card has been declined due to insufficient funds.

Cause

The issuing bank refused authorization on this transaction because the credit card has insufficient funds available to cover the transaction requested.

Resolution

Do not retry the transaction. This is not an error or failure on the part of the transaction processor and there is no action to take on your part.

 


Decline 3023

Your request has been declined by the issuing bank due to its proprietary card activity regulations.

Cause

The issuing bank is declining the transaction due to its Risk Management systems. We have no more information on this due to the confidential nature of the error code.

Resolution

There is no resolution for this error.

 


Decline 3024

Your request has been declined because the issuing bank does not permit the transaction for this card.

Cause

The issuing bank is stating that the card in question can not make a purchase on this specific merchant account. This may be due to the industry of the merchant account or due to the fact it is an online transaction.

Resolution

There is no resolution for this error.

 


Decline 3203

The authorization is either fully settled or cancelled.

Cause

You attempted to settle an amount against an authorization that has already been fully settled or else has been cancelled.

Resolution

You should verify that the authorization you are trying to settle against is the correct one, and retry the transaction. If it was the correct authorization, no further action is possible, since either there is no money left to settle against it or it was cancelled and cannot be settled.

 


Decline 3402

The requested credit amount exceeds the remaining settlement amount.

Cause

You tried a credit transaction that exceeded the amount of funds available to credit (i.e., the amount settled for that credit card).

Resolution

Retry the transaction, with an amount equal to or less than the amount available to credit.

 

Decline 4001

The card number or email address associated with this transaction is in our negative database.

Cause

Paysafe has black listed this card due to the cardholder having too many chargebacks on their card against Paysafe processors

Resolution

The cardholder will have to fill out this Decline 4001 Negative Database Release Form to have their card unblocked at Paysafe . Once cardholder has completed the form, they can email it to the MINDBODY merchant attempting to process the card. Merchant will review the form for correctness and then send directly to technicalsupport@paysafe.com.

Decline 4002

The transaction was declined by our Risk Management department

Cause

Something about this transaction raised concern with Paysafe.

Resolution

Please reach out directly to technicalsupport@paysafe.com for details.


Decline 5017

The merchant account submitted with your request is not enabled. Do not retry the transaction. Contact Paysafe Payments for more information.

Cause

The account for which this transaction is being attempted either has not been enabled or has been disabled.

Resolution

Do not retry the transaction. Contact Paysafe Payments regarding the disabled status of your account.

 

Decline 5023

The request is unparsable.

Cause

The address line in the billing information section includes either too much information (long addresses) or information that the database doesn’t recognize (unusual spaces, commas, unusual special characters

Resolution

Retry the transaction with a simplified version of the address and eliminate special characters.


Decline 5040

Your merchant account is not configured for the transaction you attempted. Please contact Technical Support for more information.

Cause

When your merchant account was set up, it was not configured for the transaction type that is being attempted.

Resolution

Do not retry the transaction as is. You should verify that your account is set up for the transaction type that you are requesting. Contact your account manager if you wish to have a transaction type enabled.

 










0 Comments
Powered by Zendesk