Beta Header Migration Guide
How to migrate off of the API beta header for New Zealand BECS Direct Debit.
New Zealand BECS Direct Debit is becoming generally available. We need beta users to stop passing the API beta header. This guide goes through the changes required to migrate.
Step 1 - Stripe.js - Changes coming on March 31 2025
On March 31 2025, Stripe will update the release cycle of stripe.js. Currently, we only have one version of stripe.js, which is v3
. This is changing, and instead stripe.js will follow a monthly release cycle, coordinated with the API release cycle.
Each monthly release of stripe.js is tied to the monthly API release that goes out at the same time. For example, version 2025-03-31.
of stripe.js uses version 2025-03-31.
of the API.
This also means that you will no longer be able to pass API beta headers when initializing stripe.js.
Required changes 
When using stripe.js v3
, you need to pass both the nz_
front-end beta flag, and the nz_
API beta header.
When upgrading to stripe.js version 2025-03-31.
, you need to stop passing both the front-end beta flag and the API beta header.
const stripe = Stripe('pk_test_TYooMQauvdEDq54NiTphI7jx', { betas: ['nz_bank_account_beta_2'], apiVersion: "2025-03-31.basil;nz_bank_account_beta=v2" });
Step 2 - API and SDK - Changes required by June 30 2025
On March 31 2025, in the 2025-03-31.
API version release, Stripe is releasing the nz_
payment method to general availability.
This means that passing the API beta header is no longer required to access the nz_
payment method.
Stripe needs beta users to stop passing the beta header by June 30 2025.
Required changes 
You need to stop passing the beta header in all requests to all endpoints - /v1/payment_
, /v1/setup_
, /v1/checkout/sessions
, /v1/customers
, and so on
curl https://api.stripe.com/v1/payment_intents \ -u sk_test_BQokikJOvBiI2HlWgH4olfQ2: \ -H "Stripe-Version: 2025-03-31.basil;nz_bank_account_beta=v2" -d amount=1099 \ -d currency=eur