Stripe Payment Processing Error Codes
This document provides a comprehensive reference for payment processing errors in the Convenient Checkout API. These errors can occur during get/payments and get/setup-payment-methods operations and help identify issues with payment processing.
Error Codes Summary
Error Code Summary
| Error Title Reference | Error Title | HTTP Status | Detail Message | Scenario | Resolution |
|---|---|---|---|---|---|
| Card Authentication Errors | NOT_ACCEPTABLE | 406 NOT ACCEPTABLE | This card requires an additional security step to be performed by the customer. Please have the customer enter the card via text or email; otherwise, have the customer provide a different payment method. | When card requires 3D Secure authentication in agent session | Guide the customer to complete the card entry via SMS or email where 3D Secure can be handled, or request an alternative payment method. |
| NOT_ACCEPTABLE | 406 NOT ACCEPTABLE | Payment method could not be authorized. This payment method requires authentication from a customer. | When card requires 3D Secure authentication in agent session | Guide the customer to complete the card entry via SMS or email where 3D Secure can be handled, or request an alternative payment method. | |
| Card Decline Errors | NOT_ACCEPTABLE | 406 NOT ACCEPTABLE | The card was declined for an unknown reason. Contact issuer for more information. | Card declined | Advise the customer to contact their card issuer to determine the reason for the decline, or use an alternative payment method. |
| NOT_ACCEPTABLE | 406 NOT ACCEPTABLE | An error occurred while processing the card, please try again. | Generic processing error | Attempt the transaction again. If the issue persists, request a different payment method from the customer. | |
| NOT_ACCEPTABLE | 406 NOT ACCEPTABLE | Payment method could not be authorized. Please try a different payment method. | General payment authorization failure | Request that the customer provide an alternative payment method. | |
| NOT_ACCEPTABLE | 406 NOT ACCEPTABLE | Payment method is canceled by a customer or expired by the financial partner | Card no longer valid | Ask the customer to update their card information or provide a new payment method. | |
| Card Validation Errors | NOT_ACCEPTABLE | 406 NOT ACCEPTABLE | The CVC number is incorrect. | Invalid CVC | Prompt the customer to re-enter the correct CVC for their card. |
| NOT_ACCEPTABLE | 406 NOT ACCEPTABLE | The card has expired. | Expired card | Request that the customer provide a card that has not expired. | |
| Financial Limit Errors | NOT_ACCEPTABLE | 406 NOT ACCEPTABLE | The customer's account has insufficient funds to complete the purchase. Please use an alternative payment method. | Insufficient funds error (specific to payments) | Advise the customer to use a different payment method or to fund their account before attempting the transaction again. |
| NOT_ACCEPTABLE | 406 NOT ACCEPTABLE | The customer has exceeded the balance, credit limit, or transaction amount limit available on their card. Contact issuer for more information. | Card limit exceeded (specific to payments) | Suggest that the customer contact their card issuer regarding their limits, or use a different payment method. | |
| Bank Account Errors | NOT_ACCEPTABLE | 406 NOT ACCEPTABLE | The customer's bank account has been closed. | Account closed | Inform the customer that the bank account has been closed and request an alternative payment method. |
| NOT_ACCEPTABLE | 406 NOT ACCEPTABLE | The customer's bank account could not be located. | Account not found | Verify the bank account details with the customer and correct any errors, or request an alternative payment method. | |
| Early Warning System Errors | NOT_ACCEPTABLE | 406 NOT ACCEPTABLE | earlyWarningMessage | Early warning system validation error | Review the specific early warning message and take appropriate action based on the warning type. This may require additional verification or an alternative payment method. |
Error Codes Details
Card Authentication Errors
3D Secure Authentication Required
Scenario: The card requires 3D Secure authentication which must be completed by the cardholder.
Sample Response:
{
"title": "NOT_ACCEPTABLE",
"status": 406,
"detail": "This card requires an additional security step to be performed by the customer. Please have the customer enter the card via text or email; otherwise, have the customer provide a different payment method."
}
Customer Authentication Required
Scenario: The payment method requires direct authentication from the customer.
Sample Response:
{
"title": "NOT_ACCEPTABLE",
"status": 406,
"detail": "Payment method could not be authorized. This payment method requires authentication from a customer."
}
Card Decline Errors
Card Declined
Scenario: The card was declined by the issuer.
Sample Response:
{
"title": "NOT_ACCEPTABLE",
"status": 406,
"detail": "The card was declined for an unknown reason. Contact issuer for more information."
}
Generic Processing Error
Scenario: An unspecified error occurred while processing the card payment.
Sample Response:
{
"title": "NOT_ACCEPTABLE",
"status": 406,
"detail": "An error occurred while processing the card, please try again."
}
General Authorization Failure
Scenario: The payment method could not be authorized.
Sample Response:
{
"title": "NOT_ACCEPTABLE",
"status": 406,
"detail": "Payment method could not be authorized. Please try a different payment method."
}
Invalid Card Status
Scenario: The card is no longer valid due to cancellation or expiration.
Sample Response:
{
"title": "NOT_ACCEPTABLE",
"status": 406,
"detail": "Payment method is canceled by a customer or expired by the financial partner"
}
Card Validation Errors
Invalid CVC
Scenario: The card verification code (CVC/CVV) provided is incorrect.
Sample Response:
{
"title": "NOT_ACCEPTABLE",
"status": 406,
"detail": "The CVC number is incorrect."
}
Expired Card
Scenario: The card has passed its expiration date.
Sample Response:
{
"title": "NOT_ACCEPTABLE",
"status": 406,
"detail": "The card has expired."
}
Financial Limit Errors
Insufficient Funds
Scenario: The customer's account lacks sufficient funds to complete the payment transaction.
Sample Response:
{
"title": "NOT_ACCEPTABLE",
"status": 406,
"detail": "The customer's account has insufficient funds to complete the purchase. Please use an alternative payment method."
}
Card Limit Exceeded
Scenario: The customer has exceeded their card's balance, credit limit, or transaction limit.
Sample Response:
{
"title": "NOT_ACCEPTABLE",
"status": 406,
"detail": "The customer has exceeded the balance, credit limit, or transaction amount limit available on their card. Contact issuer for more information."
}
Bank Account Errors
Account Closed
Scenario: The customer's bank account has been closed.
Sample Response:
{
"title": "NOT_ACCEPTABLE",
"status": 406,
"detail": "The customer's bank account has been closed."
}
Account Not Found
Scenario: The customer's bank account could not be located.
Sample Response:
{
"title": "NOT_ACCEPTABLE",
"status": 406,
"detail": "The customer's bank account could not be located."
}
Early Warning System Errors
Early Warning System Validation
Scenario: Early warning system detected a potential issue with the transaction.
Sample Response:
{
"title": "NOT_ACCEPTABLE",
"status": 406,
"detail": "earlyWarningMessage"
}