Select your billing provider below to investigate your decline code. Don’t see your billing provider in the list? We may not have added them to this documentation yet, please get in touch with them directly.
Paysafe Credit Card Decline Codes
Enter your decline code below for a description of why the payment was declined and how you may resolve this. Don’t see your code in the list? Reach out to paysafe directly for a resolution.
Decline 1007
An internal error occurred. Please retry the transaction.
| Reason: | No response was received after the transaction was sent to the processor. Most likely due to the processors gateway being temporarily unavailable. |
| Resolution: | Connectivity problems causing this error are usually short lived. Please retry the transaction. If you continue to have this issue, please contact Paysafe. |
Decline 3004
Zip/postal code must be provided for AVS Check request.
| Reason: | This code will occur if additional AVS authentication has been applied by Paysafe. |
| Resolution: | To remove this setting, please email customersupport@paysafe.com. |
Decline 3005
You submitted an incorrect value for the cvd parameter with your request. Please verify this parameter and retry the transaction.
| Reason: | An invalid value was included for the cvd parameter for your transaction request. A valid value can be only 3 or 4 digits, if this parameter was provided empty or with alphabetical characters this error will occur. |
| Resolution: | Ensure the correct value was provided with the transaction and try again. |
Decline 3006
You submitted an expired credit card number with your request. Please verify this parameter and retry the request.
| Reason: | The transaction was attempted with an expired credit card. |
| Resolution: | Ensure the card was entered correctly and that your customer’s card is current. If their card is expired, request they use another card to complete the transaction. |
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.
| Reason: |
AVS has failed on a transaction, but it would otherwise have been successful. When this error occurs the transaction value will now be considered reserved and will be unavailable for further
transaction. The bank will reserve this amount for a period of time, generally 3-5 days. When receiving this error it’s crucial to confirm the address information entered for the transaction is the same as the cardholders mailing address before trying again to avoid reserving additional funds. |
| Resolution: | Ensure the entered address information matches that of the cardholders records with their issuing bank and retry the transaction. |
Decline 3008
You submitted a card type for which the merchant account is not configured.
| Reason: | The transaction request was sent from a credit card type that your Paysafe account isn’t configured for. |
| Resolution: | Resolving this issue requires validation of the transaction request to ensure an acceptable card type is included. Adding new card types requires you to contact Paysafe and they will enable them for you. |
Decline 3012
Your request has been declined by the issuing bank because the credit card expiry date submitted is invalid.
| Reason: | An invalid credit card expiry date has been used for the transaction. The date was received by the bank and formatted correctly, but they deemed the date incorrect for the provided card number. |
| Resolution: | Ensure the card and its expiry date are valid before retrying the transaction. |
Decline 3013
Your request has been declined by the issuing bank due to problems with the credit card account.
| Reason: | The transaction was attempted using a card that has no account linked. |
| Resolution: | Ask the customer to contact their bank and determine the issue with their card before trying again. |
Decline 3014
Your request has been declined – the issuing bank has returned an unknown response. Contact the card holder’s credit card company for further investigation.
| Reason: | The bank has declined the transaction without providing an explanation. |
| Resolution: | Ask the customer to contact their bank to resolve this issue. |
Decline 3015
The bank has requested that you process the transaction manually by calling the cardholder’s credit card company.
| Reason: | The bank requires that this transaction is processed manually by calling the customer’s credit card company. |
| Resolution: | Contact the customer’s credit card provider to process the transaction. |
Decline 3016
The bank has requested that you retrieve the card from the cardholder – it may be a lost or stolen card.
| Reason: | The card used for this transaction has been marked by the bank as lost or stolen, the bank has requested you retrieve this from the cardholder. |
| Resolution: | Ask the cardholder for a different payment method or, if they believe there has been a mistake, to contact their card provider. |
Decline 3017
You submitted an invalid credit card number with your request. Please verify this parameter and retry the transaction.
| Reason: | The card has been determined to be invalid by the customer’s bank. The card parameter was included and correctly formatted. |
| Resolution: | Check the card number was entered correctly before retrying 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.
| Reason: | The entered CVD value has failed during the CVD check. The CVD value is a 3 or 4 digit security code which follows the credit card number. |
| Resolution: | Ensure the value entered for the CVD parameter was correct before retrying the request. If this reoccurs please contact Paysafe. |
Decline 3022
The card has been declined due to insufficient funds.
| Reason: | Authorization was refused by the issuing bank on this transaction as the credit card had insufficient funds available. |
| Resolution: | The customer needs to choose a payment method with the appropriate amount of available funds to complete the transaction. |
Decline 3023
Your request has been declined by the issuing bank due to its proprietary card activity regulations.
| Reason: | Due to the issuing banks risk management systems the transaction has been declined. |
| Resolution: | There is no resolution for this error, ask the customer for an alternative payment method or to contact their bank. |
Decline 3024
Your request has been declined because the issuing bank does not permit the transaction for this card.
| Reason: | The issuing bank has deemed the card unable to make a purchase on this specific merchant account. Potentially due to the transaction being carried out online or the industry which the merchant account is a part of. |
| Resolution: | There is no resolution for this error, ask the customer for an alternative payment method or to contact their bank. |
Decline 3040
Your request has been declined because the request type is not permitted on the card.
| Reason: | The bank has stated the card cannot make a purchase under this specific card type. Potentially due to the card being a debit card. |
| Resolution: | Ask the customer for an alternative payment method or you can contact Paysafe for more information. |
Decline 3203
The authorization is either fully settled or cancelled.
| Reason: | The authorization this settlement was attempted against has already been settled or otherwise been cancelled. |
| Resolution: | Please confirm the authorization being settled against is correct before retrying the transaction. If it was correct, no further action is possible since there’s either no money left or it was cancelled. |
Decline 3402
The requested credit amount exceeds the remaining settlement amount.
| Reason: | You attempted a transaction exceeding the amount of funds available to credit. |
| Resolution: | Retry the transaction, with an amount within the available credit limits. |
Decline 4001
The card number or email address associated with this transaction is in our negative database.
| Reason: | This card bas been blacklisted by Paysafe due to there being too many previous chargebacks on this card against Paysafe processors. |
| Resolution: |
Please contact paysafe with the following information: cardholder name, amount, date & time of transaction. Paysafe will investigate why they are listed in the negative database and your business may need to confirm it is happy to proceed with the transaction and accept liability of further chargebacks. |
Decline 4002
The transaction was declined by our Risk Management department
| Reason: | Paysafe has raised issue with something about this transaction. |
| Resolution: | Contact technicalsupport@paysafe.com for more information. |
Decline 5017
The merchant account submitted with your request is not enabled. Do not retry the transaction. Contact Paysafe Payments for more information.
| Reason: | The account attempting this transaction has either been disabled or wasn’t enabled. |
| Resolution: | Get in touch with Paysafe for information on why your account isn’t enabled. |
Decline 5023
The request is unparsable.
| Reason: | The address in the billing information section either has too much information or the information isn’t recognisable by the database. It may contain special characters which are not allowed. |
| Resolution: | Try again with a shorter version of the address and remove special characters. |
Decline 5040
Your merchant account is not configured for the transaction you attempted. Please contact Technical Support for more information.
| Reason: | When setting up your merchant account it wasn’t configured for the attempted transaction type. |
| Resolution: | Please ensure the account is set up for this transaction type, if it’s not you may contact your account manager to have the transaction type enabled. |
Ezidebit Credit Card Decline Codes
Enter your decline code below for a description of why the payment was declined and how you may resolve this. Don’t see your code in the list? Reach out to ezidebit directly for a resolution.
C4
Cancelled: Customer Deceased
| Description: | This customer has been reported as deceased to their bank, please reach out to your customer for more details. |
CB
Direct Debit Authority Cancelled by Bank
| Description: | Your ability to process direct debit transactions for this client has been shut off by the issuing bank. Please reach out to your client for more details. |
CC
Direct Debit Authority Cancelled by Customer
| Description: | Your ability to process direct debit transactions for this client has been shut off by your client. Please reach out to your client for more details. |
CP
Cancelled: Pick up Card
| Description: | The issuing bank is requesting you keep this card as there is a problem. Please call the 800 number on the back of the card to determine the issue. |
H2 Hold
Direct Debit Authority Cancelled by Customer
| Description: | Your ability to process direct debit transactions for this client has been shut off by your client. Please reach out to your client for more details. |
H3 Hold
Bank Account Closed
| Description: | The bank account has been closed. Please reach out to your client for updated billing information. |
H5 Hold
Incorrect BSB or Account Number
| Description: | You have entered the BSB or Account number incorrectly. Please reach out to your client to ensure you have the correct billing information on file.\ |
HE – Hold
Expired Credit Card or Incorrect Expiry Date
| Description: | The credit card has expired or the wrong expiration date has been entered. Please reach out to your client to ensure you have the correct billing information. |
HI – Hold
Invalid Credit Card Number
| Description: | The credit card number you have entered is invalid. Please reach out to your client to ensure you have the correct billing information. |
HL – Hold
Lost Credit Card
| Description: | The card has been reported lost or stolen. Please hold onto the card and call the 800 number on the back of the card to determine the issue. |
HQ – Hold
Cancelled Credit Card
| Description: | The credit card has been cancelled with the card issuing bank. Please reach out to your client for updated billing information. |
HU – Hold
Unsupported Card
| Description: | Your merchant account is not setup to accept this card type. Please contact Ezidebit to ensure you are setup to accept this card type and then contact Mindbody to ensure it is integrated with your software. |
Server was unable to process request – Unable to process update.
Add payment denied. This customer is on hold due to invalid credit card details and these card details have not been changed.
| Description: | A hold has been placed on this account. Please reach out to Ezidebit to clear the hold. |
Decline – 5
You must provide a value for the ‘lastname’ parameter
| Description: | This is a little different from a decline, this is an error code due to incorrect formatting. If the customer’s name in their billing information has any extra spaces before or after their name it will give you this decline code. In order to fix it just delete their name in the billing info on their Client Info and re-enter it without any extra spaces and save. Reprocess the transaction like normal. |
108
Invalid mobile phone number entered
| Description: | When the phone number is written under the Client Info all together as 1234567890, the merchant will see this decline code. Modify the phone number format to 4 digits, space, 3 digits space and 3 digits, which is standard Australian phone number format: 1234 567 890, and save it under the Client Info. If the phone number is missing a digit, you can also delete the phone number and save it under the Client Info and it will also work for the decline transaction. |
123
No response from Gateway
| Description: | We are not receiving a response from Ezidebit’s gateway. Please attempt the transaction again. If the problem persists, please contact Ezi Debit for more information. |
141
The First Name contains non standard characters which is not permitted.
| Description: | Ensure there are no spaces at the end of the Client Info name or other billing information and attempt the transactions again. If the problem persists, please contact Ezi Debit for more information. |
304
Add payment denied – only active customers can have payments added to their schedule.
| Description: | The merchant profile at Ezidebit cannot accept new payment schedules. Please contact Ezi Debit for more information and to rectify. |
Invalid Digital Key
| Description: | Your account is an existing Ezidebit account (prior to Mindbody) that you are trying to switch over to use with MBO. If you are fully ready for the switch, contact Ezidebit to turn over account to MBO. Any previously set up payments through the account will not run any longer, only MBO transactions. You will continue to get the decline, “invalid digital key” until you contact Ezidebit to make your account compatible with Mindbody. |
01
Refer to Card Issuer
| Description: | The card has been declined by the issuing bank. Please contact the 800 number on the back of the card for more details. |
02
Refer to Issuer’s Special Conditions
| Description: | The card has been declined by the issuing bank. Please contact the 800 number on the back of the card for more details. |
03
Invalid Merchant
| Description: | The merchant account is inactive. Please reach out to Ezidebit for more information. |
04
Pick Up Card
| Description: | The issuing bank is requesting you pick up this card. Please contact the 800 number on the back of the card for more information. |
05
Do Not Honour
| Description: | This is a generic decline from the card issuer. Please contact the 800 number on the back of the card for more information. |
06
Error
| Description: | There was an error processing this payment. Please attempt the transaction again; if the issue persists, contact Ezidebit for more information. |
07
Pick Up Card, Special Conditions
| Description: | The issuing bank is requesting you pick up this card. Please contact the 800 number on the back of the card for more information. |
12
Invalid Transaction
| Description: | This is a generic decline from the card issuer. Please contact the 800 number on the back of the card for more information. |
13
Invalid Amount
| Description: | This is a generic decline from the card issuer. Please contact the 800 number on the back of the card for more information. |
14
Invalid Card Number
| Description: | The card number you have entered is invalid. Please reach out to your client for more information. |
15
No Such Issuer
| Description: | The card number you have entered is invalid. Please reach out to your client for more information. |
17
Customer Cancellation
| Description: | The client has cancelled this transaction. Please reach out to your client for more information. |
18
Customer Dispute
| Description: | The customer has filed a dispute for this transaction. Please reach out to your client for more information. |
19
Re-enter Transaction
| Description: | There was an error processing this payment. Please attempt the transaction again; if the issue persists, contact Ezidebit for more information. |
25
Unable to Locate Record on File
| Description: | This client has not been added into the Ezidebit system. You will need to create a new account in the Mindbody software for this client to re-attempt the transaction. |
26
Duplicate File Update Record
| Description: | Ezidebit is seeing this as a duplicate transaction for this client. Please reach out to Ezidebit for more information. |
33
Expired Card—Pick Up
| Description: | This credit card has expired. Please reach out to your client for updated billing information. |
34
Suspected Fraud—Pick Up
| Description: | The issuing bank is requesting you pick up this card. Please contact the 800 number on the back of the card for more information. |
35
Contact Acquirer—Pick Up
| Description: | The issuing bank is requesting you pick up this card. Please contact the 800 number on the back of the card for more information. |
36
Restricted Card—Pick Up
| Description: | There are restrictions on this card that are not allowing the transaction to be processed. Please reach out to your client for updated billing information. |
37
Call Acquirer Security—Pick Up
| Description: | The issuing bank is requesting you pick up this card. Please contact the 800 number on the back of the card for more information. |
41
Lost Card—Pick Up
| Description: | The issuing bank is requesting you pick up this card. Please contact the 800 number on the back of the card for more information. |
43
Stolen Card—Pick Up
| Description: | The issuing bank is requesting you pick up this card. Please contact the 800 number on the back of the card for more information. |
51
Insufficient Funds
| Description: | This client does not have sufficient funds to process this transaction. Please reach out to your client for updated billing information. |
54
Expired Card
| Description: | This card has expired. Please reach out to your client for updated billing information. |
57
Trans. not Permitted to Cardholder
| Description: | There are restrictions on this card that will not allow this transaction to process. Your client will need to contact the 800 number on the back of their card for more information. |
58
Transaction not Permitted to Terminal
| Description: | There are restrictions on your Ezidebit account that will not allow this transaction to process. Please contact Ezidebit for more information. |
59
Suspected Fraud
| Description: | The issuing bank is requesting you pick up this card. Please contact the 800 number on the back of the card for more information. |
62
Restricted Card
| Description: | There are restrictions on this card that will not allow this transaction to process. Your client will need to contact the 800 number on the back of their card for more information. |
91
Declined
| Description: | There may be a credit card chargeback filed against your business by this cardholder and this will probably only be displayed for Autopays which Ezidebit considers a scheduled payment. Contact Ezidebit for the exact reason for this code and remedy as they suggest. |
108
Invalid mobile phone number entered
| Description: | When the phone number is written under the Client Info all together as 1234567890, the merchant will see this decline code. Modify the phone number format to 4 digits, space, 3 digits space and 3 digits, which is standard Australian phone number format: 1234 567 890, and save it under the Client Info. If the phone number is missing a digit, you can also delete the phone number and save it under the Client Info and it will also work for the decline transaction. |
900
Add payment denied – You have multiple Client/Upload Ref combinations, you have exceeded the Max Purchases Per Client Per Day: 2.
| Description: | You will need to try tomorrow to process this payment. |
900
Add payment denied – This customer is on hold due to invalid credit card details and these card details have not been changed.
| Description: |
The cardholder may have asked their bank to block Ezidebit from charging their card. Cardholder should contact their bank to allow the charge. |
900
Add payment denied – This customer’s status of ‘CP: Cancelled: Pick up Card’ does not allow new payments to be added.
| Description: | Please reach out to Ezidebit as there is a hold on your customer’s account. Ezidebit has the ability to release this hold per your request. |
900
Add payment denied – This customer’s status of ‘CB: Direct Debit authority cancelled by bank’ does not allow new payments to be added.
| Description: |
CardConnect Credit Card Decline Codes
Enter your decline code below for a description of why the payment was declined and how you may resolve this. Don’t see your code in the list? Reach out to cardconnect directly for a resolution.
000
| Description: | Approve |
002
| Description: | Approve for partial amount. |
003
| Description: | Approve VIP |
100
| Description: | Do not honor |
101
| Description: | Expired card |
104
| Description: | Restricted card |
105
| Description: | Call acquirer’s security department |
106
| Description: | Allowable PIN tries exceeded |
107
| Description: | Call for authorization |
108
| Description: | Refer to issuer’s special conditions |
109
| Description: | Invalid merchant. The merchant is not in the merchant database or the merchant is not permitted to use this particular card. |
110
| Description: | Invalid amount |
116
| Description: | Not sufficient funds |
117
| Description: | Incorrect PIN |
118
| Description: | No card record |
119
| Description: | Transaction not permitted to cardholder |
120
| Description: | Transaction not permitted to terminal |
121
| Description: | Exceeds withdrawal amount limit |
123
| Description: | Exceeds withdrawal frequency limit |
124
| Description: | Violation of law |
130
| Description: | Invalid terminal |
131
| Description: | Invalid account number |
132
| Description: | Unmatched card expiry date |
208
| Description: | Lost card |
209
| Description: | Stolen card |
302
| Description: | Account closed. The account was closed, probably because the account balance was $0.00. |
303
| Description: | Unknown account. The account could not be located in the account table. |
304
| Description: | Inactive account. The account has not been activated by an approved location. |
308
| Description: | Already active. The card is already active and does not need to be reactivated |
311
| Description: | Not lost or stolen |
315
| Description: | Bad mag stripe. The mag stripe could not be parsed for account information |
316
| Description: | Incorrect location. There was a problem with the merchant location. |
317
| Description: | Max balance exceeded. The transaction, if completed, would cause the account balance to be exceeded by the max_balance as specified in the promotion. Some merchants set the max_balance to a value twice the max transaction amount. |
318
| Description: | Invalid amount. There was a problem with the amount field in the transaction format – more or less than min/max amounts specified in the promotion for that transaction. |
319
| Description: | Invalid clerk. The clerk field was either missing, when required, or the content did not match the requirements |
320
| Description: | Invalid password |
321
| Description: | Invalid new password. The new password does not meet the minimum security criteria |
322
| Description: | Exceeded account reloads. The clerk/user/location was only permitted to reload some number of accounts. That number was exceeded. (See your Business Manager in order to extend this limit.) |
323
| Description: | Password retry exceeded. The user account has been frozen because the user attempted access and was denied. Seek management assistance. |
326
| Description: | Incorrect transaction version or format number for POS transactions |
327
| Description: | Request not permitted by this account |
328
| Description: | Request not permitted by this merchant location |
329
| Description: | Bad_repay_date |
330
| Description: | Bad checksum. The checksum provided is incorrect. |
331
| Description: | Balance not available (denial). Due to an internal First Data Closed Loop Gift Card (CLGC) issue, information from this account could not be retrieved. |
332
| Description: | Account locked |
333
| Description: | No previous transaction. The void or reversal transaction could not be matched to a previous (original) transaction. In the case of a pre-auth redemption, the corresponding locking transaction could not be identified. |
334
| Description: | Already reversed |
336
| Description: | Bad authorization code. The authorization code test failed. |
337
| Description: | Too many transactions requested |
338
| Description: | No transactions available/no more transactions available. There are no transactions for this account or there are no transactions as determined by the specified first transaction number. |
339
| Description: | Transaction history not available |
340
| Description: | New password required |
341
| Description: | Invalid status change. The status change requested (e.g. lost/stolen, freeze active card) cannot be performed. |
342
| Description: | Void of activation after account activity |
343
| Description: | No phone service. Attempted a calling card transaction on an account which is not configured for calling card activity. |
344
| Description: | Internet access disabled |
345
| Description: | Invalid EAN. The EAN is not correct for the provided account number. |
346
| Description: | Invalid merchant key. The merchant key block provided is invalid. (e.g. The working key provided in an Assign Merchant Working Key transaction). |
347
| Description: | Promotions for Internet virtual and physical cards do not match. When enabling a physical card to a virtual card, both must be from the same promotion. Cards for bulk activation request must be from the same promotion |
348
| Description: | Invalid transaction source. The provided source (field EA) is not valid for this transaction. |
349
| Description: | Account already linked. (e.g. Response when enabling a physical card, when the two provided accounts have already been linked together.) |
350
| Description: | Account not in inactive state. (e.g. Response when enabling a physical card, when the physical card in not in an inactive state.) |
351
| Description: | First Data Voice Services returns this response on Internet transactions where the interface input parameter is not valid. |
352
| Description: | First Data Voice Services returns this response on Internet transactions where they did not receive a response from CLGC. |
353
| Description: | First Data Voice Services returns this response on Internet transactions where the client certificate is invalid. |
354
| Description: | Merchant not configured as International although the account requires it. (e.g. The account allows currency conversion but the merchant is not configured for International.) |
355
| Description: | Invalid currency. The provided currency is invalid. |
356
| Description: | Request not International. Merchant configured to require currency information for each financial transaction, however none was sent. |
357
| Description: | Currency conversion error. Internal CLGC system error. |
359
| Description: | The terminal transaction number did not match (on a void or reversal). |
360
| Description: | First Data Voice Services added a layer of validation that checks the data they receive from CLGC to make sure it is HTML friendly (i.e. no binary data). First Data Voice Services will return this response on Internet transactions if the check fails (the data is not HTML friendly). |
367
| Description: | Target embossed card entered and Transaction count entered do not match |
368
| Description: | No account link |
369
| Description: | Invalid time zone |
370
| Description: | Account on hold |
372
| Description: | Promo location restricted |
373
| Description: | Invalid Card Account |
374
| Description: | Product code(s) restricted |
375
| Description: | Bad Post Date. The Post Date is not a valid date. |
376
| Description: | Account status is void lock |
377
| Description: | Already active and reloadable |
378
| Description: | Account is Purged. The Account record was purged from the database. |
380
| Description: | Bulk activation error |
381
| Description: | Bulk activation un-attempted error |
382
| Description: | Bulk activation package amount error |
383
| Description: | Store location zero not allowed |
384
| Description: | Account row locked |
385
| Description: | Accepted but not yet processed |
402
| Description: | TransArmor Service Unavailable |
403
| Description: | TransArmor Invalid Token or Account Number |
404
| Description: | TransArmor Key Error |
500
| Description: | Decline |
501
| Description: | Date of Birth Error for Check Processing |
502
| Description: | Invalid State Code |
503
| Description: | New Account Information |
504
| Description: | Do not try again |
505
| Description: | Please retry |
506
| Description: | Invalid Checking Account Number |
507
| Description: | New Account Information available |
508
| Description: | Try again later – Declined: Association‘s payment cancellation advice code provided. Applies to recurring authorizations only. These are examples of what may have occurred: the account is over the credit limit try again in 72 hours. |
509
| Description: | Do not try again – Applies to recurring authorizations only. The card has expired |
510
| Description: | New Account Information – Applies to recurring authorizations only. The card has expired |
511
| Description: | Try again later – Applies to recurring authorizations only. The card has expired. Get the new expiration date and try again. |
512
| Description: | Service not allowed |
513
| Description: | Decline. Transaction not permitted to acquirer or terminal |
514
| Description: | Do not try again – Applies to recurring authorizations only. There was security violation. |
515
| Description: | Declined. No term record on First Data system |
516
| Description: | Please retry – Reasons for this error are one of the following: Format Error, Unable to route transaction, Switch or issuer unavailable, System Busy, Timeout |
517
| Description: | CVV2 Declined |
518
| Description: | Invalid account/date or sales date in future |
519
| Description: | Invalid Effective Date |
520
| Description: | Reversal Rejected. Do not try again. |
521
| Description: | Enter lesser amount |
522
| Description: | Cash Back greater than total Transaction amount |
523
| Description: | Crypto box is offline |
524
| Description: | Debit Switch unavailable Timeout Retry – Communications link to debit/EBT network gateway is down or responded with a “System Malfunction (96)” message |
525
| Description: | Debit/EBT network gateway cannot get through to the ISSUER. |
526
| Description: | Undefined Card – Debit/EBT network gateway cannot route card based on Merchant Entitlement |
527
| Description: | Network Response indicates that Merchant ID / SE is invalid |
528
| Description: | Debit/EBT transaction count exceeds pre-determined limit in specified time/ Withdrawal limit exceeded. |
529
| Description: | Resubmission of transaction violates debit/EBT network frequency |
530
| Description: | The authorizing network has a problem decrypting the cryptogram in the request |
532
| Description: | The DUKPT Base Derivation key is missing or incorrect in the PIN pad, or PIN key synchronization error. |
540
| Description: | Edit Honor |
541
| Description: | No Savings Account |
542
| Description: | DUKPT: An error while processing the PIN block that is not related to the point- ofsale equipment. Contact the Help Desk for assistance. |
701
| Description: | Approved EMV Key Load |
702
| Description: | EMV Key Download Error |
703
| Description: | Approved EMV Key Load, more key load data pending |
704
| Description: | Pick Up Card |
708
| Description: | Honor With Authentication |
726
| Description: | Unable to Locate Record On File |
727
| Description: | Refer – Call Authorization (Checks only) |
728
| Description: | Referred – Skip Trace Info |
729
| Description: | Hard Negative Info On File |
740
| Description: | Totals Unavailable |
767
| Description: | Hard Capture; Pick Up |
771
| Description: | Amount Too Large |
772
| Description: | Duplicate Return |
773
| Description: | Unsuccessful |
774
| Description: | Duplicate Reversal |
775
| Description: | Subsystem Unavailable |
776
| Description: | Duplicate Completion |
782
| Description: | Count Exceeds Limit |
785
| Description: | No reason to decline. |
790
| Description: | Not approved. Used only in Visa bill/recurring payment. Merchant must not resubmit same transaction but may continue billing process in subsequent billing period. |
791
| Description: | Not approved. Used only in Visa bill/recurring payment. Merchant must stop recurring payment requests. |
902
| Description: | Invalid transaction. This card or terminal is not permitted to perform this transaction, or the transaction type is invalid, or First Data is unable to route a refund request to the network. 904 Format error. |
906
| Description: | System Error. There is a problem with the host processing system. Call your helpdesk or operations support. |
908
| Description: | Transaction destination not found for routing. |
909
| Description: | System malfunction. |
911
| Description: | Card issuer timed out. |
913
| Description: | Duplicate transaction. |
914
| Description: | Void/Full Reversal requests in which the Original Authorization was not found. |
940
| Description: | Error. |
941
| Description: | No such issuer. |
954
| Description: | CCV failed. |
Doc Type WEB not allowed
| Description: | Configuration issue to do with handling ACH payments. Please contact the billing provider support team. |
Stripe Credit Card Decline Codes
Enter your decline code below for a description of why the payment was declined and how you may resolve this. Don’t see your code in the list? Reach out to stripe directly for a resolution.
account_already_exists
| Description: | The email address provided for the creation of a deferred account already has an account associated with it. Use the OAuth flow to connect the existing account to your platform. |
account_country_invalid_address
| Description: | The country of the business address provided does not match the country of the account. Businesses must be located in the same country as the account. |
account_invalid
| Description: | The account ID provided as a value for the Stripe-Account header is invalid. Check that your requests are specifying a valid account ID. |
account_number_invalid
| Description: | The bank account number provided is invalid (e.g., missing digits). Bank account information varies from country to country. We recommend creating validations in your entry forms based on the bank account formats we provide. |
alipay_upgrade_required
| Description: | This method for creating Alipay payments is not supported anymore. Please upgrade your integration to use Sources instead. |
amount_too_large
| Description: | The specified amount is greater than the maximum amount allowed. Use a lower amount and try again. |
amount_too_small
| Description: | The specified amount is less than the minimum amount allowed. Use a higher amount and try again. |
api_key_expired
| Description: | The API key provided has expired. Obtain your current API keys from the Dashboard and update your integration to use them. |
authentication_required
| Description: | The payment requires authentication to proceed. If your customer is off session, notify your customer to return to your application and complete the payment. If you provided the error_on_requires_action parameter, then your customer should try another card that does not require authentication. |
balance_insufficient
| Description: | The transfer or payout could not be completed because the associated account does not have a sufficient balance available. Create a new transfer or payout using an amount less than or equal to the account’s available balance. |
bank_account_declined
| Description: | The bank account provided can not be used to charge, either because it is not verified yet or it is not supported. |
bank_account_exists
| Description: | The bank account provided already exists on the specified Customer object. If the bank account should also be attached to a different customer, include the correct customer ID when making the request again. |
bank_account_unusable
| Description: | The bank account provided cannot be used for payouts. A different bank account must be used. |
bank_account_unverified
| Description: | Your Connect platform is attempting to share an unverified bank account with a connected account. |
bank_account_verification_failed
| Description: | The bank account cannot be verified, either because the microdeposit amounts provided do not match the actual amounts, or because verification has failed too many times. |
bitcoin_upgrade_required
| Description: | This method for creating Bitcoin payments is not supported anymore. Please upgrade your integration to use Sources instead. |
card_decline_rate_limit_exceeded
| Description: | This card has been declined too many times. You can try to charge this card again after 24 hours. We suggest reaching out to your customer to make sure they have entered all of their information correctly and that there are no issues with their card. |
card_declined
| Description: | The card has been declined. When a card is declined, the error returned also includes the decline_code attribute with the reason why the card was declined. Refer to our decline codes documentation to learn more. |
charge_already_captured
| Description: | The charge you’re attempting to capture has already been captured. Update the request with an uncaptured charge ID. |
charge_already_refunded
| Description: | The charge you’re attempting to refund has already been refunded. Update the request to use the ID of a charge that has not been refunded. |
charge_disputed
| Description: | The charge you’re attempting to refund has been charged back. Check the disputes documentation to learn how to respond to the dispute. |
charge_exceeds_source_limit
| Description: | This charge would cause you to exceed your rolling-window processing limit for this source type. Please retry the charge later, or contact us to request a higher processing limit. |
charge_expired_for_capture
| Description: | The charge cannot be captured as the authorization has expired. Auth and capture charges must be captured within seven days. |
charge_invalid_parameter
| Description: | One or more provided parameters was not allowed for the given operation on the Charge. Check our API reference or the returned error message to see which values were not correct for that Charge. |
clearing_code_unsupported
| Description: | The clearing code provided is not supported. |
country_code_invalid
| Description: | The country code provided was invalid. |
country_unsupported
| Description: | Your platform attempted to create a custom account in a country that is not yet supported. Make sure that users can only sign up in countries supported by custom accounts. |
coupon_expired
| Description: | The coupon provided for a subscription or order has expired. Either create a new coupon, or use an existing one that is valid. |
customer_max_payment_methods
| Description: | The maximum number of PaymentMethods for this Customer has been reached. Either detach some PaymentMethods from this Customer or proceed with a different Customer. |
customer_max_subscriptions
| Description: | The maximum number of subscriptions for a customer has been reached. Contact us if you are receiving this error. |
email_invalid
| Description: | The email address is invalid (e.g., not properly formatted). Check that the email address is properly formatted and only includes allowed characters. |
expired_card
| Description: | The card has expired. Check the expiration date or use a different card. |
idempotency_key_in_use
| Description: | The idempotency key provided is currently being used in another request. This occurs if your integration is making duplicate requests simultaneously. |
incorrect_address
| Description: | The card’s address is incorrect. Check the card’s address or use a different card. |
incorrect_cvc
| Description: | The card’s security code is incorrect. Check the card’s security code or use a different card. |
incorrect_number
| Description: | The card number is incorrect. Check the card’s number or use a different card. |
incorrect_zip
| Description: | The card’s postal code is incorrect. Check the card’s postal code or use a different card. |
instant_payouts_unsupported
| Description: | This card is not eligible for Instant Payouts. Try a debit card from a supported bank. |
intent_invalid_state
| Description: | Intent is not the state that is rquired to perform the operation. |
intent_verification_method_missing
| Description: | Intent does not have verification method specified in its PaymentMethodOptions object. |
invalid_card_type
| Description: | The card provided as an external account is not supported for payouts. Provide a non-prepaid debit card instead. |
invalid_characters
| Description: | This value provided to the field contains characters that are unsupported by the field. |
invalid_charge_amount
| Description: | The specified amount is invalid. The charge amount must be a positive integer in the smallest currency unit, and not exceed the minimum or maximum amount. |
| Description: |
invalid_cvc
| Description: | The card’s security code is invalid. Check the card’s security code or use a different card. |
invalid_expiry_month
| Description: | The card’s expiration month is incorrect. Check the expiration date or use a different card. |
invalid_expiry_year
| Description: | The card’s expiration year is incorrect. Check the expiration date or use a different card. |
invalid_number
| Description: | The card number is invalid. Check the card details or use a different card. |
invalid_source_usage
| Description: | The source cannot be used because it is not in the correct state (e.g., a charge request is trying to use a source with a pending, failed, or consumed source). Check the status of the source you are attempting to use. |
invoice_no_customer_line_items
| Description: | An invoice cannot be generated for the specified customer as there are no pending invoice items. Check that the correct customer is being specified or create any necessary invoice items first. |
invoice_no_payment_method_types
| Description: | An invoice cannot be finalized because there are no payment method types available to process the payment. Your invoice template settings or the invoice’s payment_settings might be restricting which payment methods are available, or you might need to activate more payment methods in the Dashboard. |
invoice_no_subscription_line_items
| Description: | An invoice cannot be generated for the specified subscription as there are no pending invoice items. Check that the correct subscription is being specified or create any necessary invoice items first. |
invoice_not_editable
| Description: | The specified invoice can no longer be edited. Instead, consider creating additional invoice items that will be applied to the next invoice. You can either manually generate the next invoice or wait for it to be automatically generated at the end of the billing cycle. |
invoice_payment_intent_requires_action
| Description: | This payment requires additional user action before it can be completed successfully. Payment can be completed using the PaymentIntent associated with the invoice. See this page for more details. |
invoice_upcoming_none
| Description: | There is no upcoming invoice on the specified customer to preview. Only customers with active subscriptions or pending invoice items have invoices that can be previewed. |
livemode_mismatch
| Description: | Test and live mode API keys, requests, and objects are only available within the mode they are in. |
lock_timeout
| Description: | This object cannot be accessed right now because another API request or Stripe process is currently accessing it. If you see this error intermittently, retry the request. If you see this error frequently and are making multiple concurrent requests to a single object, make your requests serially or at a lower rate. See the rate limit documentation for more details. |
missing
| Description: | Both a customer and source ID have been provided, but the source has not been saved to the customer. To create a charge for a customer with a specified source, you must first save the card details. |
not_allowed_on_standard_account
| Description: | Transfers and payouts on behalf of a Standard connected account are not allowed. |
order_creation_failed
| Description: | The order could not be created. Check the order details and then try again. |
order_required_settings
| Description: | The order could not be processed as it is missing required information. Check the information provided and try again. |
order_status_invalid
| Description: | The order cannot be updated because the status provided is either invalid or does not follow the order lifecycle (e.g., an order cannot transition from created to fulfilled without first transitioning to paid). |
order_upstream_timeout
| Description: | The request timed out. Try again later. |
out_of_inventory
| Description: | The SKU is out of stock. If more stock is available, update the SKU’s inventory quantity and try again. |
parameter_invalid_empty
| Description: | One or more required values were not provided. Make sure requests include all required parameters. |
parameter_invalid_integer
| Description: | One or more of the parameters requires an integer, but the values provided were a different type. Make sure that only supported values are provided for each attribute. Refer to our API documentation to look up the type of data each attribute supports. |
parameter_invalid_string_blank
| Description: | One or more values provided only included whitespace. Check the values in your request and update any that contain only whitespace. |
parameter_invalid_string_empty
| Description: | One or more required string values is empty. Make sure that string values contain at least one character. |
parameter_missing
| Description: | One or more required values are missing. Check our API documentation to see which values are required to create or modify the specified resource. |
parameter_unknown
| Description: | The request contains one or more unexpected parameters. Remove these and try again. |
parameters_exclusive
| Description: | Two or more mutually exclusive parameters were provided. Check our API documentation or the returned error message to see which values are permitted when creating or modifying the specified resource. |
payment_intent_action_required
| Description: | The provided payment method requires customer actions to complete, but error_on_requires_action was set. If you’d like to add this payment method to your integration, we recommend that you first upgrade your integration to handle actions. |
payment_intent_authentication_failure
| Description: | The provided payment method has failed authentication. Provide a new payment method to attempt to fulfill this PaymentIntent again. |
payment_intent_incompatible_payment_method
| Description: | The PaymentIntent expected a payment method with different properties than what was provided. |
payment_intent_invalid_parameter
| Description: | One or more provided parameters was not allowed for the given operation on the PaymentIntent. Check our API reference or the returned error message to see which values were not correct for that PaymentIntent. |
payment_intent_payment_attempt_failed
| Description: | The latest payment attempt for the PaymentIntent has failed. Check the last_payment_error property on the PaymentIntent for more details, and provide a new payment method to attempt to fulfill this PaymentIntent again. |
payment_intent_unexpected_state
| Description: | The PaymentIntent’s state was incompatible with the operation you were trying to perform. |
payment_method_invalid_parameter
| Description: | Invalid parameter was provided in the payment method object. Check our API documentation or the returned error message for more context. |
payment_method_provider_decline
| Description: | The payment was declined by the issuer or customer. Check the last_payment_error property on the PaymentIntent for more details, and provide a new payment method to attempt to fulfill this PaymentIntent again. |
payment_method_provider_timeout
| Description: | The payment method failed due to a timeout. Check the last_payment_error property on the PaymentIntent for more details, and provide a new payment method to attempt to fulfill this PaymentIntent again. |
payment_method_unactivated
| Description: | The operation cannot be performed as the payment method used has not been activated. Activate the payment method in the Dashboard, then try again. |
payment_method_unexpected_state
| Description: | The provided payment method’s state was incompatible with the operation you were trying to perform. Confirm that the payment method is in an allowed state for the given operation before attempting to perform it. |
payouts_not_allowed
| Description: | Payouts have been disabled on the connected account. Check the connected account’s status to see if any additional information needs to be provided, or if payouts have been disabled for another reason. |
platform_api_key_expired
| Description: | The API key provided by your Connect platform has expired. This occurs if your platform has either generated a new key or the connected account has been disconnected from the platform. Obtain your current API keys from the Dashboard and update your integration, or reach out to the user and reconnect the account. |
postal_code_invalid
| Description: | The postal code provided was incorrect. |
processing_error
| Description: | An error occurred while processing the card. Try again later or with a different payment method. |
product_inactive
| Description: | The product this SKU belongs to is no longer available for purchase. |
rate_limit
| Description: | Too many requests hit the API too quickly. We recommend an exponential backoff of your requests. |
resource_already_exists
| Description: | A resource with a user-specified ID (e.g., plan or coupon) already exists. Use a different, unique value for id and try again. |
resource_missing
| Description: | The ID provided is not valid. Either the resource does not exist, or an ID for a different resource has been provided. |
routing_number_invalid
| Description: | The bank routing number provided is invalid. |
secret_key_required
| Description: | The API key provided is a publishable key, but a secret key is required. Obtain your current API keys from the Dashboard and update your integration to use them. |
sepa_unsupported_account
| Description: | Your account does not support SEPA payments. |
setup_attempt_failed
| Description: | The latest setup attempt for the SetupIntent has failed. Check the last_setup_error property on the SetupIntent for more details, and provide a new payment method to attempt to set it up again. |
setup_intent_authentication_failure
| Description: | The provided payment method has failed authentication. Provide a new payment method to attempt to fulfill this SetupIntent again. |
setup_intent_invalid_parameter
| Description: | One or more provided parameters was not allowed for the given operation on the SetupIntent. Check our API reference or the returned error message to see which values were not correct for that SetupIntent. |
setup_intent_unexpected_state
| Description: | The SetupIntent’s state was incompatible with the operation you were trying to perform. |
shipping_calculation_failed
| Description: | Shipping calculation failed as the information provided was either incorrect or could not be verified. |
sku_inactive
| Description: | The SKU is inactive and no longer available for purchase. Use a different SKU, or make the current SKU active again. |
state_unsupported
| Description: | Occurs when providing the legal_entity information for a U.S. custom account, if the provided state is not supported. (This is mostly associated states and territories.) |
tax_id_invalid
| Description: | The tax ID number provided is invalid (e.g., missing digits). Tax ID information varies from country to country, but must be at least nine digits. |
taxes_calculation_failed
| Description: | Tax calculation for the order failed. |
terminal_location_country_unsupported
| Description: | Terminal is currently only available in some countries. Locations in your country cannot be created in livemode. |
testmode_charges_only
| Description: | Your account has not been activated and can only make test charges. Activate your account in the Dashboard to begin processing live charges. |
tls_version_unsupported
| Description: | Your integration is using an older version of TLS that is unsupported. You must be using TLS 1.2 or above. |
token_already_used
| Description: | The token provided has already been used. You must create a new token before you can retry this request. |
token_in_use
| Description: | The token provided is currently being used in another request. This occurs if your integration is making duplicate requests simultaneously. |
transfers_not_allowed
| Description: | The requested transfer cannot be created. Contact us if you are receiving this error. |
upstream_order_creation_failed
| Description: | The order could not be created. Check the order details and then try again. |
url_invalid
| Description: | The URL provided is invalid. |
Membership Management
Online Booking
Go Mobile
Automation