Export Bacs data from Stripe
Learn how to export your Bacs data from Stripe to another payment processor.
You can migrate your data from your Stripe account to a new payment processor using the bulk change process. Stripe coordinates with other payment processors and Bacs sponsor banks to securely migrate your Bacs data. A Bacs export migration takes approximately 6-8 weeks to complete.
To import Bacs data from another payment processor to Stripe, see Import payment method data.
Submit your Bacs export migration request
Start the migration process by submitting a data migration request.
- Complete the Stripe Support for data migrations form. If you’re not signed in, select Sign in and enter the credentials of the account that you want to migrate your data from.
- Select Export data out of Stripe to a third party.
- Select Bacs as the data type you want to export.
- Complete the remaining fields and select Send email.
Our team reviews your request and assigns a specialist to guide you through the export process. We’ll contact you in an authenticated email thread connected to your form.
Gather essential information
To facilitate a smooth migration, gather the following information about your new payment processor before submitting the migration request:
| Required information | Description |
|---|---|
| New processor name | The payment service provider you’re migrating to |
| PGP encryption key | Your new processor’s public key for secure data transfer |
| New SUN | Your Service User Number with the new processor |
| New SUN display name | The business name that will appear on statements with the new processor |
| Number of mandates | Total count of mandates you plan to migrate |
This information is used throughout the migration process and is essential for coordinating with sponsor banks. We’ll request this in the email thread connected to your migration form.
Coordinate migration dates and prepare the bulk change deed
Your new payment processor is responsible for initiating the bulk change process with their Bacs sponsor bank. If you’re working with a bank directly, make sure to initiate the bulk change according to their guidelines.
Set a migration date
All parties need to coordinate the following dates:
- Date of Bacs export: The date when Stripe shares your data, typically a few business days before the bulk change date.
- Bulk change date: All bulk change documentation references this date. It’s the date that mandates are canceled with Stripe and the date new mandates are initiated with the new processor and sponsor bank.
These dates must allow sufficient time for data preparation, validation, and customer notification.
Bulk change deed
Stripe provides you with a signed bulk change deed, which is a formal document authorizing the transfer of your mandates from Stripe to the new processor or bank. You’ll need to work with your new processor to complete the remaining sections of the document, allowing them to initiate the bulk change request.
The following template highlights the required fields of a complete bulk change deed.
Caution
Sign in to download the bulk change deed.
Notify your customers
After the bulk change has received final approval from both sponsor banks, notify your customers about the upcoming bulk change.
The Letter to Payers explains why the migration is necessary, how it affects payers, and includes details about the Direct Debit Guarantee. You must send this communication at least 3 business days before the bulk change date. Failing to notify payers about the bulk change can result in failed payments and disputes.
Your new processor might provide a template for this communication. Work with them closely to complete this step.
Data export and mandate cancellation with Stripe
On the agreed export date, Stripe prepares a data file containing your customer and payment method data, encrypts it with your new processor’s PGP key, and uploads it to a secure SFTP server. Stripe then provides encrypted credentials that you must share with your new processor so they can access and retrieve the exported data.
Before the bulk change date, Stripe cancels all mandates included in the export, making them inactive on Stripe. At this point, your new processor becomes responsible for processing future payments, so make sure that any scheduled payments through Stripe are canceled or redirected accordingly. Your customers continue their Direct Debit payments through your new processor without needing to provide authorization again.