## Confirm a setup

Use `stripe.confirmSetup` to confirm a [SetupIntent](/api/setup_intents.md) using data collected
by the [Payment Element](/js/element/payment_element.md), or with manually provided data via `confirmParams`.
When called, `stripe.confirmSetup` will attempt to complete any [required actions](/payments/intents.md),
such as authenticating your user by displaying a 3DS dialog or redirecting them to a bank authorization page.
Your user will be redirected to the `return_url` you pass once the authorization is complete.

> The `stripe.confirmSetup` might take several seconds to complete.
> During that time, disable your form from being resubmitted and show a waiting indicator, such as a spinner. If you receive an error result, show this error to the user, re-enable the form, and hide the waiting indicator.

`stripe.confirmSetup` will return a `Promise`.
For payments that don't require a redirect, the `Promise` resolves to the updated Intent. After a successful authorization, Stripe redirects your user to the `return_url` you provided before the `Promise` resolves. For payments that don't require a redirect, the `Promise` resolves to the updated Intent.

If the authorization fails, the `Promise` resolves with an `{error}` object that describes the failure. If the [error type](/api/errors#errors-type) is either `card_error` or `validation_error`, directly display the error
message in `error.message` to your user. If the error type is `invalid_request_error, you might have an invalid request or 3DS authentication failures.

For some payment methods, such as iDEAL or Afterpay/Clearpay, Stripe first redirects your user to an intermediate page to authorize the payment.
If iDEAL or Afterpay/Clearpay fail to authorize the payment, Stripe redirects the user to your `return_url`, and the SetupIntent has a `status` of `requires_payment_method`.
In this case, attempt to recollect payment from the user.

**Syntax:** `stripe.confirmSetup(...)`

- `options` (object) **required**

  - `elements` (object) **required**
    The [Elements](#payment_element_create) instance used to create the Payment Element.

Required if you [collect payment details before creating an Intent](/payments/accept-a-payment-deferred.md?platform=web&type=setup). It's always required if you don't provide a `clientSecret`.

  - `clientSecret` (string) **required**
    The SetupIntent's client secret.

Required if you [collect payment details before creating an Intent](/payments/accept-a-payment-deferred.md?platform=web&type=setup). It's always required if you don't provide an `elements` instance containing a [client secret](/api/setup_intents/object.md#setup_intent_object-client_secret).

  - `confirmParams` (object)
    Parameters that will be passed on to the Stripe API. Refer to the [Setup Intents API](/api/setup_intents/confirm.md) for a full list of parameters.

    - `return_url` (string) **required**
      The URL that Stripe redirects your customer to after they complete authentication.

    - `confirmation_token` (string)
      If collected previously, the ID of the ConfirmationToken to use to confirm this SetupIntent. This is mutually exclusive with the `elements` parameter.

    - `payment_method_data` (object)
      When you call `stripe.confirmSetup`, payment details are collected from the Element and passed to the SetupIntents
[confirm endpoint](/api/setup_intents/confirm.md) as the [payment_method_data](/api/setup_intents/confirm.md#confirm_setup_intent-payment_method)
parameter. You can also include additional `payment_method_data` fields, which will be merged with the data collected from the Element.

      - `billing_details` (object)
        The customer's [billing_details](/api/payment_methods/create.md#create_payment_method-billing_details).
Details collected by Elements will override values passed here.
Billing fields that are omitted in the Payment Element via the `fields` option required.

      - `allow_redisplay` ('unspecified' | 'always' | 'limited')
        Indicates whether the payment method can be displayed to the customer in subsequent checkout flows. The value passed here will override the [allow_redisplay](docs/api/payment_methods/object#payment_method_object-allow_redisplay) determined by the provided `elements` parameter.

    - `expand` (array)
      An array of pass through [SetupIntent](/api/setup_intents/object.md) expansion parameters ([learn more](/api/expanding_objects.md)).

  - `redirect` ('always' | 'if_required')
    By default, `stripe.confirmSetup` will always redirect to your `return_url` after a successful confirmation.
If you set `redirect: "if_required"`, then `stripe.confirmSetup` will only redirect if your user chooses a redirect-based payment method.

**Note**: Setting `if_required` requires that you handle successful confirmations for redirect-based and non-redirect based payment methods separately.
When a non-redirect based payment method is successfully confirmed, `stripe.confirmSetup` will resolve with a `{setupIntent}` object.

### Confirm a setup intent

```js
stripe.confirmSetup({
  elements,
  confirmParams: {
    // Return URL where the customer should be redirected after the SetupIntent is confirmed.
    return_url: 'https://example.com',
  },
})
.then(function(result) {
  if (result.error) {
    // Inform the customer that there was an error.
  }
});
```

```es_next
const {error} = await stripe.confirmSetup(
  {
    elements,
    confirmParams: {
      // Return URL where the customer should be redirected after the SetupIntent is confirmed.
      return_url: 'https://example.com',
    },
  }
);
if (error) {
  // Inform the customer that there was an error.
}
```