code: '''HTTP status code summary200 - OKEverything worked as expected.400 - Bad RequestThe request was unacceptable, often due to missing a required
                    parameter.401 - UnauthorizedNo valid API key provided.402 - Request FailedThe parameters were valid but the request failed.403 - ForbiddenThe API key doesn't have permissions to perform the request.404 - Not FoundThe requested resource doesn't exist.409 - ConflictThe request conflicts with another request (perhaps due to
                    using the same idempotent key).429 - Too Many RequestsToo many requests hit the API too quickly. We recommend an
                    exponential backoff of your requests.500, 502, 503, 504 - Server ErrorsSomething went wrong on Stripe's end. (These are rare.)Error typesapi_errorAPI errors cover any other type of problem (e.g., a temporary
                    problem with Stripe's servers), and are extremely
                    uncommon.card_errorCard errors are the most common type of error you should
                    expect to handle. They result when the user enters a card that
                    can't be charged for some reason.idempotency_errorIdempotency errors occur when an Idempotency-Key
                    is re-used on a request that does not match the first request's
                    API endpoint and parameters.invalid_request_errorInvalid request errors arise when your request has invalid
                    parameters.
  '''
nl: ErrorsStripe uses conventional HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. Codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted, a charge failed, etc.). Codes in the 5xx range indicate an error with Stripe's servers (these are rare).Some 4xx errors that could be handled programmatically (e.g., a card is declined) include an error code that briefly explains the error reported.Attributes type string The type of error returned. One of api_error, card_error, idempotency_error, or invalid_request_error code string For some errors that could be handled programmatically, a short string indicating the error code reported. decline_code string 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. message string A human-readable message providing more details about the error. For card errors, these messages can be shown to your users. param string If the error is parameter-specific, the parameter related to the error. For example, you can use this to display a message near the correct form field. payment_intent hash The PaymentIntent object for errors returned on a request involving a PaymentIntent.Show child attributesMore attributesExpand all  charge string   doc_url string   payment_method hash   payment_method_type string   setup_intent hash   source hash