Save details for future payments with New Zealand BECS Direct Debits

Learn how to save payment method details for future New Zealand bank account debit payments.

You can use the Setup Intents API to collect payment method details in advance, with the final amount or payment date determined later. This is useful for:

Saving payment methods to a wallet to streamline future purchases
Collecting surcharges after fulfilling a service
Starting a free trial for a subscription

Set up Stripe
Server-side

First, you need a Stripe account. Register now.

Use our official libraries for access to the Stripe API from your application:

Create or retrieve a Customer
Server-side

To reuse a bank account for future payments, attach it to a Customer.

Create a Customer object when your customer creates an account with your business. Associating the ID of the Customer object with your own internal representation of a customer enables you to retrieve and use the stored payment method details later. If your customer hasn’t created an account, you can still create a Customer object now and associate it with your internal representation of the customer’s account later.

Create a new Customer or retrieve an existing Customer to associate with these payment details. Include the following code on your server to create a new Customer.

Create a SetupIntent
Server-side

A SetupIntent is an object that represents your intent to set up a customer’s payment method for future payments. The SetupIntent tracks the steps of this set-up process.

Create a SetupIntent on your server with payment_method_types set to nz_bank_account and specify the Customer’s id.

Retrieve the client secret

The SetupIntent includes a client secret that the client side uses to securely complete the payment process. You can use different approaches to pass the client secret to the client side.

Retrieve the client secret from an endpoint on your server, using the browser’s fetch function. This approach is best if your client side is a single-page application, particularly one built with a modern front-end framework such as React. Create the server endpoint that serves the client secret:

And then fetch the client secret with JavaScript on the client side:

(async () => {
  const response = await fetch('/secret');
  const {client_secret: clientSecret} = await response.json();
  // Render the form using the clientSecret
})();

Collect payment method details and mandate acknowledgement
Client-side

Set up Stripe Elements

Include the Stripe.js script on your checkout page by adding it to the head of your HTML file. Always load Stripe.js directly from js.stripe.com. Don’t include the script in a bundle or host a copy of it yourself.

checkout.html
<head>
  <title>Checkout</title>
  <script src="https://js.stripe.com/v3/"></script>
</head>

Create an instance of the Stripe object by providing your publishable API key as the first parameter, additionally passing the nz_bank_account_beta_2 beta flag to access the Elements:

checkout.js
// Set your publishable key: remember to change this to your live publishable key in production
// See your keys here: https://dashboard.stripe.com/apikeys
const stripe = Stripe('pk_test_TYooMQauvdEDq54NiTphI7jx'
, {
  betas: ['nz_bank_account_beta_2'],
  apiVersion: "2025-03-31.basil;nz_bank_account_beta=v2"
});

Add the Payment Element to your checkout page

On your checkout page, create an empty DOM node with a unique ID for the Payment Element to render into.

checkout.html
<form id="payment-form">
  <h3>Payment</h3>
  <div id="payment-element"></div>

  <button id="submit">Submit</button>
</form>

When the form above finishes loading, create a new Elements group, passing the client secret from the previous step as configuration. You can also pass in the appearance option, customising the Elements to match the design of your site.

Then, create an instance of the Payment Element and mount it to its corresponding DOM node:

checkout.js
// Customize the appearance of Elements using the Appearance API.
const appearance = { /* ... */ };

// Create an elements group from the Stripe instance, passing the clientSecret (obtained in step 2) and appearance (optional).
const elements = stripe.elements({clientSecret, appearance});

// Create Payment Element instance.
const paymentElement = elements.create("payment");

// Mount the Payment Element to its corresponding DOM node.
paymentElement.mount("#payment-element");

The Payment Element renders a dynamic form that allows your customer to pick a payment method type. The form automatically collects all necessary payments details for the payment method type that they select. For New Zealand BECS Diret Debit payments, that includes the customer’s name, email address, and bank account number.

Mandate acknowledgement

The Payment Element also displays the New Zealand BECS Direct Debit Service Terms and Conditions to your customer and collects their agreement with those terms. You’re not required to do anything else.

If you don’t use the Payment Element, you must separately display these terms and conditions to your customer and confirm their acceptance.

Note

By providing your bank account details and confirming this payment, you authorise Stripe New Zealand Limited (authorisation code 3143978), to debit your account with the amounts of direct debits payable to Rocket Rides (“we”, “us” or “Merchant”) in accordance with this authority.

You agree that this authority is subject to:

your bank’s terms and conditions that relate to your account, and
the Direct Debit Service Terms and Conditions

You certify that you are either the sole account holder on the bank account listed above or that you are an authorised signatory on, and have authority to operate, this bank account severally.

We will send you an email confirmation no later than 5 business days after your confirmation of this Direct Debit Authority.

If we request you to do so, you must promptly provide Stripe with a record of the mandates.

OptionalCustomize the appearance
Client-side

Submit the payment method details to Stripe
Client-side

Use stripe.confirmSetup to collect bank account details, create a PaymentMethod, and attach that PaymentMethod to the SetupIntent.

For some other payment method types, your customer might be first redirected to an intermediate site, like a bank authorisation page, before being redirected to the return_url. Provide a return_url to this function to indicate where Stripe should redirect the customer after they complete the payment.

Since New Zealand BECS Direct Debits don’t require a redirect, you can also set redirect to if_required in place of providing a return_url. A return_url will only be required if you add another redirect-based payment method later.

script.js
confirmationForm.addEventListener('submit', (ev) => {
  ev.preventDefault();
  stripe.confirmSetup({elements, redirect: "if_required"})
  .then(({setupIntent, error}) => {
    if (error) {
      console.error(error.message);
      // The confirmation failed for some reason.
    } else if (setupIntent.status === "requires_payment_method") {
      // Confirmation failed. Attempt again with a different payment method.
    } else if (setupIntent.status === "succeeded") {
      // Confirmation succeeded! The account is now saved.
      // Display a message to the customer.
    }
  });
});

If successful, Stripe returns a SetupIntent object with the status succeeded. The attached PaymentMethod is now ready to be used for future payments.

Customer notification emails

You must send an email confirmation of the mandate and collected bank account details to your customer after successfully confirming the SetupIntent.

In addition, for every payment collected, you must send your customer an email notification of the debit date and amount at latest on the day the debit takes place.

Stripe handles sending these emails for you by default, but you can choose to send custom notifications.

Accepting future payments
Server-side

When the SetupIntent succeeds, it creates a new PaymentMethod attached to a Customer. You can use these to initiate future payments without having to prompt the customer for their bank account a second time.

Test your integration

Test account numbers

In a sandbox, you can use the following parameters to simulate specific errors.

Test your form using bank code 11, branch code 0000 and one of the following account numbers.

Account Number	Description
`0000000010`	PaymentIntents confirmed with the resulting PaymentMethod transition from `processing` to `succeeded`. The mandate status remains `active`.
`2222222027`	PaymentIntents confirmed with the resulting PaymentMethod transition from `processing` to `requires_payment_method` with a `insufficient_funds` failure code. The mandate status remains `active`.
`8888888000`	PaymentIntents confirmed with the resulting PaymentMethod transition from `processing` to `requires_payment_method` with a `refer_to_customer` failure code. The mandate status remains `active`.
`1111111016`	PaymentIntents confirmed with the resulting PaymentMethod transition from `processing` to `requires_payment_method` with an `no_account` failure code. The mandate status becomes `inactive`.
`5555555059`	PaymentIntents confirmed with the resulting PaymentMethod transition from `processing` to `requires_payment_method` with a `debit_not_authorized` failure code. The mandate status becomes `inactive`.
`9999999000`	PaymentIntents confirmed with the resulting PaymentMethod transition to `processing` and remain there. To transition it further, use an API request as described below.