## Confirm a BECS Debit payment

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

Use `stripe.confirmAuBecsDebitPayment` in the [BECS Direct Debit Payments](https://docs.stripe.com/payments/au-becs-debit.md) with Payment Methods flow when the customer submits your payment form.
When called, it will confirm the [PaymentIntent](https://docs.stripe.com/api/payment_intents.md) with `data` you provide.
Note that there are some additional requirements to this flow that are not covered in this reference.
Refer to our [integration guide](https://docs.stripe.com/payments/au-becs-debit.md) for more details.

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.confirmAuBecsDebitPayment` 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`
      The `id` of an existing PaymentMethod or an object of collected data.
See use cases below for details.
    - `setup_future_usage`
      To set up the BECS Direct Debit account for reuse, set this
parameter to `off_session`. BECS Direct Debit only accepts an
`off_session` value for this parameter. If a `customer` is
provided on this [PaymentIntent](https://docs.stripe.com/api/payment_intents.md),
the [PaymentMethod](https://docs.stripe.com/api/payment_methods.md) will be attached
to the customer when the PaymentIntent transitions to
`processing`.

### with payment data from an Element

### Data argument properties

- `payment_method`
  Pass an `object` to confirm the payment using data collected by an `auBankAccount` [Element](https://docs.stripe.com/js/element.md).
    - `au_becs_debit`
      An `auBankAccount` Element.
    - `billing_details`
      The customer's [billing_details](https://docs.stripe.com/api/payment_methods/create.md#create_payment_method-billing_details).
`name` and `email` are required.
      - `name`
        The account holder's name.
      - `email`
        The customer's email.

### Example

```title
Confirm with an Element
```

### with self collected data

### Data argument properties

- `payment_method`
  Pass an object to confirm using data collected without an `Element`.
    - `au_becs_debit`
      - `bsb_number`
        A Bank State Branch (BSB) number.
      - `account_number`
        A bank account number.
    - `billing_details`
      The customer's [billing_details](https://docs.stripe.com/api/payment_methods/create.md#create_payment_method-billing_details).
`name` and `email` are required.
      - `name`
        The account holder's name.
      - `email`
        The customer's email.

### Example

```title
Confirm with self collected data
```

### with an existing payment method

### Data argument properties

- `payment_method`
  The `id` of an existing [PaymentMethod](https://docs.stripe.com/api/payment_methods.md).

### Example

```title
Confirm with existing payment method
```

### with an attached PaymentMethod

### Example

```title
Confirm with an attached PaymentMethod
```

### Example

```title
Confirm a BECS Debit payment
```