Confirm a SetupIntent

Changed on

Confirm that your customer intends to set up the current or provided payment method. For example, you would confirm a SetupIntent when a customer hits the “Save” button on a payment method management page on your website.

If the selected payment method does not require any additional steps from the customer, the SetupIntent will transition to the succeeded status.

Otherwise, it will transition to the requires_action status and suggest additional actions via next_action. If setup fails, the SetupIntent will transition to the requires_payment_method status or the canceled status if the confirmation limit is reached.

post/v1/setup_intents/{intent}/confirm

Request

  • Base URL: https://api.stripe.com
  • URL: https://api.stripe.com/v1/setup_intents/{intent}/confirm
  • Auth: one of:
    • HTTP basic
    • HTTP bearer

Path parameters

intentstring required

Request body application/x-www-form-urlencoded

allowed_payment_method_typesstring[]

The list of payment method types to allow for this SetupIntent. Stripe will only use methods in this list when determining the payment methods to offer. A list of valid payment method types can be found here.

client_secretstring

The client secret of the SetupIntent.

confirmation_tokenstring

ID of the ConfirmationToken used to confirm this SetupIntent.

If the provided ConfirmationToken contains properties that are also being provided in this request, such as payment_method, then the values in this request will take precedence.

expandstring[]

Specifies which fields in the response should be expanded.

payment_methodstring

ID of the payment method (a PaymentMethod, Card, or saved Source object) to attach to this SetupIntent.

return_urlstring

The URL to redirect your customer back to after they authenticate on the payment method's app or site. If you'd prefer to redirect to a mobile application, you can alternatively supply an application URI scheme. This parameter is only used for cards and other redirect-based payment methods.

use_stripe_sdkboolean

Set to true when confirming server-side and using Stripe.js, iOS, or Android client-side SDKs to handle the next actions.

Response

Successful response.

allowed_payment_method_typesstring[] nullable

The list of payment method types to allow for this SetupIntent. Stripe will only use methods in this list when determining the payment methods to offer.

attach_to_selfboolean

If present, the SetupIntent's payment method will be attached to the in-context Stripe Account.

It can only be used for this Stripe Account’s own money movement flows like InboundTransfer and OutboundTransfers. It cannot be set to true when setting up a PaymentMethod for a Customer, and defaults to false when attaching a PaymentMethod to a Customer.

cancellation_reason'abandoned' | 'duplicate' | 'requested_by_customer' nullable

Reason for cancellation of this SetupIntent, one of abandoned, requested_by_customer, or duplicate.

client_secretstring nullable

The client secret of this SetupIntent. Used for client-side retrieval using a publishable key.

The client secret can be used to complete payment setup from your frontend. It should not be stored, logged, or exposed to anyone other than the customer. Make sure that you have TLS enabled on any page that includes the client secret.

createdinteger required

Time at which the object was created. Measured in seconds since the Unix epoch.

customer_accountstring nullable

ID of the Account this SetupIntent belongs to, if one exists.

If present, the SetupIntent's payment method will be attached to the Account on successful setup. Payment methods attached to other Accounts cannot be used with this SetupIntent.

descriptionstring nullable

An arbitrary string attached to the object. Often useful for displaying to users.

excluded_payment_method_typesstring[] nullable

Payment method types that are excluded from this SetupIntent.

flow_directionsstring[] nullable

Indicates the directions of money movement for which this payment method is intended to be used.

Include inbound if you intend to use the payment method as the origin to pull funds from. Include outbound if you intend to use the payment method as the destination to send funds to. You can include both if you intend to use the payment method for both purposes.

idstring required

Unique identifier for the object.

livemodeboolean required

If the object exists in live mode, the value is true. If the object exists in test mode, the value is false.

metadataobject nullable

Set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format.

object'setup_intent' required

String representing the object's type. Objects of the same type share the same value.

payment_method_typesstring[] required

The list of payment method types (e.g. card) that this SetupIntent is allowed to set up. A list of valid payment method types can be found here.

status'canceled' | 'processing' | 'requires_action' | 'requires_confirmation' | 'requires_payment_method' | 'succeeded' required

Status of this SetupIntent, one of requires_payment_method, requires_confirmation, requires_action, processing, canceled, or succeeded.

usagestring required

Indicates how the payment method is intended to be used in the future.

Use on_session if you intend to only reuse the payment method when the customer is in your checkout flow. Use off_session if your customer may or may not be in your checkout flow. If not provided, this value defaults to off_session.

Changes

  • c113b1939b8fRevision changes
    • info

      added the optional property ////// to the response with the status

  • 7b8f614372caRevision changes
    • info

      added the optional property ////////// to the response with the status

Some revisions have not been checked yet.