## Confirm a Setup Intent *`confirmSetupIntent` has been deprecated. Going forward, if you wish to confirm on the client without handling next actions, simply pass `{handleActions: false}` as a third argument to [confirmCardSetup](#stripe_confirm_card_setup). While we have no plans to ever remove support for `confirmSetupIntent`, we think that explicitly opting out of next action handling is easier to understand and will better convey what the method is doing.* Use `stripe.confirmSetupIntent(clientSecret, data)` to confirm the `SetupIntent` when you are not gathering payment information from an `Element`. Call this variation when you have already attached a payment method to this `SetupIntent`, or if you want to attach an existing card, token, or `PaymentMethod` to it. Only use this method if you want to handle next actions yourself. Otherwise, use `stripe.handleCardSetup`. > Note that `stripe.confirmSetupIntent` may take several seconds to complete. > During that time, you should disable your form from being resubmitted and show a waiting indicator like a spinner. > If you receive an error result, you should be sure to show that error to the customer, re-enable the form, and hide the waiting indicator. A Promise which resolves with a `result` object. The object will have either: * `result.setupIntent`: the successful [SetupIntent](/api/setup_intents). * `result.error`: An error. Refer to the [API reference](/api/errors) for all possible errors. **Syntax:** `stripe.confirmSetupIntent(...)` - `clientSecret` (string) **required** The [client secret](/api/setup_intents/object.md#setup_intent_object-client_secret) of the `SetupIntent` to confirm. - `data` (object) Data to be sent with the request. It can contain the following parameters - `return_url` (string) If you are [handling next actions yourself](/payments/payment-intents/verifying-status.md#next-actions), pass in a `return_url`. If the subsequent action is `redirect_to_url`, this URL will be used on the return path for the redirect. - `payment_method` (string) Use `payment_method` to specify an existing [PaymentMethod](/api/payment_methods.md) to use for this payment. Only one of `payment_method_data` and `payment_method` is required. - `payment_method_data` (object) Use this parameter to supply additional data relevant to the payment method, such as billing details. - `billing_details` (object) The [billing details](/api/payment_methods/create.md#create_payment_method-billing_details) associated with the card. - `card[token]` (string) Converts the provided token into a `PaymentMethod` to use for the payment. ### Confirm a SetupIntent ```js stripe .confirmSetupIntent('{SETUP_INTENT_CLIENT_SECRET}', { payment_method: '{PAYMENT_METHOD_ID}', return_url: 'https://example.com/return_url', }) .then(function(result) { // Handle result.error or result.setupIntent }); ``` ```es_next const {setupIntent, error} = await stripe.confirmSetupIntent( '{SETUP_INTENT_CLIENT_SECRET}', { payment_method: '{PAYMENT_METHOD_ID}', return_url: 'https://example.com/return_url' } ); ```