What does an error code on stripe mean?
See the idempotency documentation if you need to familiarize yourself with this concept and to see how the Stripe API applies it. Content errors are the result of the contents of an API request being invalid and return an HTTP response with a 4xx error code.
Why is stripe should retry not set in response?
Stripe-Should-Retry not set in the response indicates that the API can’t determine whether or not it can retry the request. Clients should fall back to other properties of the response (like the status code) to make a decision. The retry mechanisms built into Stripe’s client libraries respect Stripe-Should-Retry automatically.
Why do I get a 4xx error code on stripe?
Content errors are the result of the contents of an API request being invalid and return an HTTP response with a 4xx error code. For example, the API servers might return a 401 if an invalid API key was provided, or a 400 if a required parameter was missing. Integrations should correct the original request, and try again.
What happens if there is a 500 error on stripe?
The exact nature of any retroactive changes in the system depends heavily on the type of request. For example, if creating a charge returns a 500 error but we detect that the information has gone out a payment network, we’ll try to roll it forward. If not, we’ll try to roll it back.
What does it mean when a stripe card is declined?
For card errors resulting from a card issuer decline, a short string indicating the card issuer’s reason for the decline if they provide one. A human-readable message providing more details about the error.
What should I do if my stripe request is 500 s?
Stripe engineers examine failed requests and try to appropriately reconcile the results of any mutations that result in 500 s. While the idempotency-cached response to those requests won’t change, we’ll try to fire webhooks for any new objects created as part of Stripe’s reconciliation.