Migrate from another processor

The Direct Debit Authority is the mandate that the customer gives to authorize the debit of the customer’s account. Before you migrate, make sure that you retain a copy of the Direct Debit Authority for each customer that you plan to migrate. Stripe might require you to provide copies of the Authorities, and you must do so promptly. Keep in mind that you continue to be responsible for any disputes opened before the migration.

Migration notification

Inform your customers about the migration before it happens. You must include the following information:

• The name of your new processor: Stripe New Zealand Limited (direct debit authority code: 3143978)
• The date when the transfer occurs (that is, when the migration will complete and when Stripe will start processing the direct debit payments)
• Your customer support contact details

Tell your customers that no further action is required from them, unless they choose to cancel the mandate.

First Debit Notification

Inform your customers after you successfully process the first payment post-migration. You must send this notification in addition to the automatic notification that Stripe sends after successfully importing your customer bank account details.

Stripe notifications

Stripe automatically notifies your customers after successfully importing your customer bank account details. See mandate confirmation emails for more information.

In addition, Stripe also notifies your customers on each of the new payments post-migration. See pre-debit notification emails for more information.

If you’ve turned off automatic notifications by Stripe, you must notify your customers. Specific requirements apply for these requirements, see mandate confirmation emails and pre-debit notification emails for more information.

Manually migrate bank accounts from another payment processor

For each of your customers and bank accounts, create a SetupIntent:

1. Create a new Customer object or retrieve an existing one to associate with this bank account.

curl -X POST https://api.stripe.com/v1/customers \
  -u "
sk_test_BQokikJOvBiI2HlWgH4olfQ2
:"

1. Create and confirm a SetupIntent with your saved bank account details and the date of your customer’s original authorization to debit the account.

curl https://api.stripe.com/v1/setup_intents \
  -u "
sk_test_BQokikJOvBiI2HlWgH4olfQ2
:" \
  -H "Stripe-Version: 2025-04-30.basil; nz_bank_account_beta=v2" \
  -d customer={{CUSTOMER_ID}} \
  -d confirm=true \
  -d "payment_method_data[type]"=nz_bank_account \
  -d "payment_method_data[nz_bank_account][bank_code]"={{BANK_CODE}} \
  -d "payment_method_data[nz_bank_account][branch_code]"={{BRANCH_CODE}} \
  -d "payment_method_data[nz_bank_account][account_number]"={{ACCOUNT_NUMBER}} \
  -d "payment_method_data[nz_bank_account][suffix]"={{SUFFIX}} \
  -d "mandate_data[customer_acceptance][type]"=offline \
  -d "mandate_data[customer_acceptance][accepted_at]"=1692821946

1. Retrieve and store the PaymentMethod ID from the response to use for future payments. You can also retrieve it by listing all PaymentMethods for the customer.