## Confirm a MB WAY payment

Use `stripe.confirmMbWayPayment` in the MB WAY payment method creation flow when the customer submits your payment form.
When you call the method, it confirms the [PaymentIntent](/api/payment_intents.md) with the `data` you provide, and sends a request to the customer to authorize the transaction.

When you confirm a `PaymentIntent`, it needs to have an attached [PaymentMethod](/api/payment_methods.md).
In addition to confirming the `PaymentIntent`, this method can automatically create and attach a new `PaymentMethod` for you.
If you've 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.confirmMbWayPayment` might take some time to complete while waiting for customers to authorize the payment.
> 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, show that error to the customer, re-enable the form, and hide the waiting indicator.

By default, `stripe.confirmMbWayPayment` will poll for updates to the `PaymentIntent`.
If there's an error, or when handling `next_action`s manually by using the `handleActions: false` option, it returns a `Promise` which resolves with a `result` object.
This object has either:
* `result.paymentIntent`: the successful [PaymentIntent](/api/payment_intents).
* `result.error`: an error.
  Refer to the [API reference](/api/errors) for all possible errors.

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

- `clientSecret` (string) **required**
  The [client secret](/api/payment_intents/object.md#payment_intent_object-client_secret) of the `PaymentIntent`.

- `data` (object)
  Data to be sent with the request.
Refer to the [Payment Intents API](/api/payment_intents/confirm.md) for a full list of parameters.

  - `payment_method` (string | object)
    Either the `id` of an existing [PaymentMethod](/api/payment_methods.md), or an object containing data to create a `PaymentMethod` with.
See the use case sections below for details.

- `options` (object)
  An options object to control the behavior of this method.

  - `handleActions` (boolean)
    Set this to `false` if you want to manually handle polling for PaymentIntent updates.
Default is `true`.

### Use case: without an existing payment method

If you haven't already created a `PaymentMethod`, you can pass payment method parameters, and the newly created `PaymentMethod` is used to confirm the `PaymentIntent`.

### Data argument properties

- `payment_method` (object) **required**
  Pass payment method billing details.

  - `billing_details` (object) **required**
    The [billing_details](/api/payment_methods/create.md#create_payment_method-billing_details) associated with the payment. A phone number is required for all MB WAY payments.

    - `phone` (string) **required**

### Confirm without existing payment method

```js
stripe.confirmMbWayPayment(
  '{PAYMENT_INTENT_CLIENT_SECRET}',
  {
    payment_method: {
      billing_details: {
        phone: '+351911111111'
      }
    }
  }
).then(function(result) {
  if (result.error) {
    // Inform the customer that there was an error.
  }
});
```

```es_next
const {paymentIntent, error} = await stripe.confirmMbWayPayment(
  '{PAYMENT_INTENT_CLIENT_SECRET}',
  {
    payment_method: {
      billing_details: {
        phone: '+351911111111'
      }
    }
  }
);
```

### Use case: with an existing payment method

If you've already created a `PaymentMethod`, you can pass its `id` to `payment_method`, which is used to confirm the `PaymentIntent`.

### Data argument properties

- `payment_method` (string) **required**
  The `id` of an existing `PaymentMethod`.

### Confirm with existing payment method

```js
stripe.confirmMbWayPayment(
  '{PAYMENT_INTENT_CLIENT_SECRET}',
  {
    payment_method: '{PAYMENT_METHOD_ID}'
  }
).then(function(result) {
  // Inform the customer that there was an error.
});
```

```es_next
const {paymentIntent, error} = await stripe.confirmMbWayPayment(
  '{PAYMENT_INTENT_CLIENT_SECRET}',
  {
    payment_method: '{PAYMENT_METHOD_ID}'
  }
);
```

### Use case: with an attached PaymentMethod

If you've already attached a `PaymentMethod` to this `PaymentIntent`, you can confirm it without passing in any additional data.

### Confirm with an attached PaymentMethod

```js
stripe
  .confirmMbWayPayment('{PAYMENT_INTENT_CLIENT_SECRET}')
  .then(function(result) {
    if (result.error) {
      // Inform the customer that there was an error.
    }
  });
```

```es_next
const {paymentIntent, error} = await stripe.confirmMbWayPayment('{PAYMENT_INTENT_CLIENT_SECRET}');
```

### Confirm a MB WAY payment

```js
stripe
  .confirmMbWayPayment('{PAYMENT_INTENT_CLIENT_SECRET}')
  .then(function(result) {
    if (result.error) {
      // Inform the customer that there was an error.
    }
  });
```

```es_next
const {paymentIntent, error} = await stripe.confirmMbWayPayment('{PAYMENT_INTENT_CLIENT_SECRET}');
```