## Confirm a MobilePay payment

`stripe.confirmMobilepayPayment(clientSecret: string, data?: object, options?: object)`

Use `stripe.confirmMobilepayPayment` in the [MobilePay Payments with Payment Methods](https://docs.stripe.com/payments/mobilepay.md) flow when the customer submits your payment form. When called, it will confirm the `PaymentIntent` with `data` you provide, and it will automatically redirect the customer to authorize the transaction. Once authorization is complete, the customer will be redirected back to your specified `return_url`.

When you confirm a `PaymentIntent`, it needs to have an attached [PaymentMethod](https://docs.stripe.com/api/payment_methods.md). In addition to confirming the `PaymentIntent`, this method can automatically create and attach a new `PaymentMethod` for you. If you have already attached a `PaymentMethod` you can call this method without needing to provide any additional data. These use cases are detailed in the sections that follow.

> Note that `stripe.confirmMobilepayPayment` 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.

* `clientSecret`
The [client secret](https://docs.stripe.com/api/payment_intents/object.md#payment_intent_object-client_secret) of the `PaymentIntent`.
* `data`
Data to be sent with the request. Refer to the [Payment Intents API](https://docs.stripe.com/api/payment_intents/confirm.md) for a full list of parameters.
* `payment_method`
Either the `id` of an existing [PaymentMethod](https://docs.stripe.com/api/payment_methods.md), or an object containing data to create a `PaymentMethod` with. See the use case sections below for details.
* `return_url`
The url your customer will be directed to after they complete authentication.
* `options`
An options object to control the behavior of this method.
* `handleActions`
Set this to `false` if you want to [manually handle the authorization redirect](https://docs.stripe.com/payments/ideal/accept-a-payment?platform=web.md#web-handle-redirect). Default is `true`.

### with an existing payment method

#### Data argument properties

* `payment_method`
The `id` of an existing `PaymentMethod`.
* `return_url`
The url your customer will be directed to after they complete authentication.

### Example

```javascript title=Confirm with an existing PaymentMethod
const stripe = await stripeLoad(); // stripe is the Stripe instance from loadStripe
const paymentIntent = { clientSecret: 'pi_...' }; // your PaymentIntent client_secret

const result = await stripe.confirmMobilepayPayment(
  paymentIntent.clientSecret,
  {
    payment_method: {
      payment_method: 'pm_...', // existing PaymentMethod ID
    },
    return_url: 'https://example.com/done',
  }
);

if (result.error) {
  // handle error
} else {
  // handle success
}
```

### with an attached PaymentMethod

### Example

```javascript title=Confirm with an attached PaymentMethod
const stripe = await stripeLoad(); // stripe is the Stripe instance from loadStripe
const paymentIntent = { clientSecret: 'pi_...' }; // your PaymentIntent client_secret

const result = await stripe.confirmMobilepayPayment(
  paymentIntent.clientSecret,
  {
    // no payment_method or payment_method_data needed
    return_url: 'https://example.com/done',
  }
);

if (result.error) {
  // handle error
} else {
  // handle success
}
```

### Example

```javascript title=Confirm a MobilePay payment
const stripe = await stripeLoad(); // stripe is the Stripe instance from loadStripe
const paymentIntent = { clientSecret: 'pi_...' }; // your PaymentIntent client_secret

const result = await stripe.confirmMobilepayPayment(
  paymentIntent.clientSecret,
  {
    return_url: 'https://example.com/done',
  }
);

if (result.error) {
  // handle error
} else {
  // handle success
}
```