In general, there are three status code ranges you can expect:
2xxsuccess status codes confirm that your request worked as expected
4xxerror status codes indicate an error because of the information provided (e.g., a required parameter was omitted)
5xxerror status codes are rare and indicate an error with Stripe’s servers
4xx errors that could be handled programmatically (e.g., a card is declined) include an error code—a short string with a brief explanation—as a value for
code. Below is a list of possible error codes that can be returned, along with additional information about how to resolve them. For your convenience, these types of errors also include the
doc_url attribute with a direct link to the specific error code it corresponds to.
- 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.
- 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.
- The account ID provided as a value for the
Stripe-Accountheader is invalid. Check that your requests are specifying a valid account ID.
- 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.
- This method for creating Alipay payments is not supported anymore. Please upgrade your integration to use Sources instead.
- The specified amount is greater than the maximum amount allowed. Use a lower amount and try again.
- The specified amount is less than the minimum amount allowed. Use a higher amount and try again.
- The API key provided has expired. Obtain your current API keys from the Dashboard and update your integration to use them.
- The payment requires authentication to proceed. Notify your customer to return to your application and complete the payment. See our guide to off-session payments for more information.
- 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.
- The bank account provided can not be used to charge, either because it is not verified yet or it is not supported.
- 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.
- The bank account provided cannot be used for payouts. A different bank account must be used.
- Your Connect platform is attempting to share an unverified bank account with a connected account.
- 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.
- This method for creating Bitcoin payments is not supported anymore. Please upgrade your integration to use Sources instead.
- 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.
- The card has been declined. When a card is declined, the error returned also includes the
decline_codeattribute with the reason why the card was declined. Refer to our decline codes documentation to learn more.
- The charge you’re attempting to capture has already been captured. Update the request with an uncaptured charge ID.
- 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.
- The charge you’re attempting to refund has been charged back. Check the disputes documentation to learn how to respond to the dispute.
- 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.
- The charge cannot be captured as the authorization has expired. Auth and capture charges must be captured within seven days.
- 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.
- 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.
- The coupon provided for a subscription or order has expired. Either create a new coupon, or use an existing one that is valid.
- The maximum number of subscriptions for a customer has been reached. Contact us if you are receiving this error.
- The email address is invalid (e.g., not properly formatted). Check that the email address is properly formatted and only includes allowed characters.
- The card has expired. Check the expiration date or use a different card.
- The idempotency key provided is currently being used in another request. This occurs if your integration is making duplicate requests simultaneously.
- The card’s address is incorrect. Check the card’s address or use a different card.
- The card’s security code is incorrect. Check the card’s security code or use a different card.
- The card number is incorrect. Check the card’s number or use a different card.
- The card’s ZIP code is incorrect. Check the card’s ZIP code or use a different card.
- This card is not eligible for Instant Payouts. Try a debit card from a supported bank.
- The card provided as an external account is not supported for payouts. Provide a non-prepaid debit card instead.
- 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.
- The card’s security code is invalid. Check the card’s security code or use a different card.
- The card’s expiration month is incorrect. Check the expiration date or use a different card.
- The card’s expiration year is incorrect. Check the expiration date or use a different card.
- The card number is invalid. Check the card details or use a different card.
- 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
consumedsource). Check the status of the source you are attempting to use.
- 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.
- 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.
- 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.
- 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.
- 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.
- Test and live mode API keys, requests, and objects are only available within the mode they are in.
- 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.
- 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.
- Transfers and payouts on behalf of a Standard connected account are not allowed.
- The order could not be created. Check the order details and then try again.
- The order could not be processed as it is missing required information. Check the information provided and try again.
- 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
fulfilledwithout first transitioning to
- The request timed out. Try again later.
- The SKU is out of stock. If more stock is available, update the SKU’s inventory quantity and try again.
- One or more required values were not provided. Make sure requests include all required parameters.
- 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.
- One or more values provided only included whitespace. Check the values in your request and update any that contain only whitespace.
- One or more required string values is empty. Make sure that string values contain at least one character.
- One or more required values are missing. Check our API documentation to see which values are required to create or modify the specified resource.
- The request contains one or more unexpected parameters. Remove these and try again.
- 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.
- The provided payment method has failed authentication. Provide a new payment method to attempt to fulfill this PaymentIntent again.
- The PaymentIntent expected a payment method with different properties than what was provided.
- 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.
- The latest payment attempt for the PaymentIntent has failed. Check the
last_payment_errorproperty on the PaymentIntent for more details, and provide a new payment method to attempt to fulfill this PaymentIntent again.
- The PaymentIntent’s state was incompatible with the operation you were trying to perform.
- The charge cannot be created as the payment method used has not been activated. Activate the payment method in the Dashboard, then try again.
- 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 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.
- 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.
- The ZIP code provided was incorrect.
- An error occurred while processing the card. Check the card details are correct or use a different card.
- The product this SKU belongs to is no longer available for purchase.
- Too many requests hit the API too quickly. We recommend an exponential backoff of your requests.
- A resource with a user-specified ID (e.g., plan or coupon) already exists. Use a different, unique value for
idand try again.
- The ID provided is not valid. Either the resource does not exist, or an ID for a different resource has been provided.
- The bank routing number provided is invalid.
- 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.
- Your account does not support SEPA payments.
- The latest setup attempt for the SetupIntent has failed. Check the
last_setup_errorproperty on the SetupIntent for more details, and provide a new payment method to attempt to set it up again.
- The provided payment method has failed authentication. Provide a new payment method to attempt to fulfill this SetupIntent again.
- The SetupIntent’s state was incompatible with the operation you were trying to perform.
- Shipping calculation failed as the information provided was either incorrect or could not be verified.
- The SKU is inactive and no longer available for purchase. Use a different SKU, or make the current SKU active again.
- Occurs when providing the
legal_entityinformation for a U.S. custom account, if the provided state is not supported. (This is mostly associated states and territories.)
- 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.
- Tax calculation for the order failed.
- Your account has not been activated and can only make test charges. Activate your account in the Dashboard to begin processing live charges.
- Your integration is using an older version of TLS that is unsupported. You must be using TLS 1.2 or above.
- The token provided has already been used. You must create a new token before you can retry this request.
- The token provided is currently being used in another request. This occurs if your integration is making duplicate requests simultaneously.
- The requested transfer cannot be created. Contact us if you are receiving this error.
- The order could not be created. Check the order details and then try again.
- The URL provided is invalid.
Was this page helpful?