Copy PAN data across Stripe accounts
Securely copy sensitive primary account number data within Stripe.
Stripe’s self-serve data copy service allows you to copy customer and payment data from one Stripe account to another Stripe account in the Dashboard.
A data copy involves two parties: the sender account and the recipient account.
- Sender account: The Stripe account currently storing the customer data. This is the account to copy the data from.
- Recipient account: The Stripe account where you want to store the customer data. This is the account to copy the data to.
Before beginning the copying process, the sender and the recipient must provide their account IDs to each other. If you’re the sender account, work with a user of the recipient account to share account IDs. If you’re the recipient account, work with a user of the sender account to share account IDs. Find your account ID by going to the User settings in the Dashboard while logged into your account.
Data copying considerations
Consider the following when copying data to a new account:
We can only copy data from one account to another. We can’t merge or move the data. After it’s complete, the copied data exists on both the destination and source accounts.
We only copy the raw Customer objects and associated payment data objects. The supported payment methods include:
- Cards stored as Card objects
- Cards stored as Source objects
- Cards stored as Payment method objects
- US ACH records stored as Bank account objects
We can’t copy Single Euro Payments Area (SEPA), BACs, or ACH records stored as payment method objects at this time.
We can’t copy individual Charges, PaymentIntents, Invoices, Plans, Subscriptions, Coupons, Events, Logs, Guest customers, or any other Stripe objects.
The copy operation doesn’t change customer IDs, resulting in the same IDs for customers in both the destination and source account data.
The copy process assigns new object IDs of the same payment type to payment data. For example, the process assigns a new card object ID to all card objects and new payment method object IDs to all payment method objects. After the copy process is complete, Stripe creates and uploads a CSV mapping file to the Documents section of the recipient’s Dashboard. The mapping file is available to the recipient only. The mapping file contains the following headers:
customer_
id_ old source_
id_ old customer_
id_ new source_
id_ new
Customer IDs don’t change during the copying process, so
customer_
andid_ old customer_
have the same value after the copy finishes.id_ new source_
is the old payment method ID from the sharing account, andid_ old source_
is the new payment method ID from the recipient account.id_ new Source account data remains intact. We recommend keeping the original source account as a backup for your data.
The recipient account must be an activated account. To activate the account, log in to the Dashboard and follow the prompts at the top-left of the home screen to activate payments.
You can’t copy deleted customers from the sharing account to the recipient account. After you delete a Customer, there’s no way to restore that customer.
If you delete a customer in the recipient account, a second copy doesn’t restore that customer.
During a second copy involving the same accounts and same customers, previously-copied Customer objects aren’t duplicated. The second copy copies over brand new Stripe Customer objects or new payment methods only for previously-copied Customer objects. If you delete a customer in the account, re-copying that customer from the sharing account doesn’t restore that customer.
The copy includes only Stripe Customer objects (
cus_
). We can’t copy Guest (xxx gcus_
) customers – see Guest customers to learn more. Sender accounts must have Customer objects stored to process a data copy.xxxx Accounts can perform up to 50 copies per day. Stripe limits copies to unauthorised accounts to one copy until the recipient account authorises the first copy request.
If any expired cards are included in the records that you copy over to the destination account, there’s the possibility that Card Account Updater (CAU), if turned on for the destination account, will communicate with the card networks to automatically update these cards. This can result in additional CAU fees for the destination account. To avoid the possibility of CAU fees related to a self-serve copy, the destination account team must work with the source account team to make sure that no expired cards are included in the copy data set.
Full or partial copy
You can perform a full or partial copy. A full copy sends all customers from the sender account. A partial copy sends a subset of customers from the sender account.
A partial copy entails sending a subset of customers from the sender account to the recipient account. There are two ways to complete a partial copy:
- Select customers in the Dashboard: Recommended for copies of less than 15 customers
- Upload a CSV file with a list of customer IDs: Recommended for copies of more than 15 customers
You need to complete three steps for a full data copy:
- The sender shares their customer data with the recipient.
- The recipient authorises and accepts the customer data from the sender.
- The copying process finishes.
Share customer data with the recipient
- The sender logs into their Stripe account and navigates to the Customers page.
- They click Copy customers.
- In the Copy Method field, they click Copy all customers.
- They enter the account ID (
acct_
) of the recipient account and click Continue. If they haven’t previously shared customers with this recipient account, they receive a message stating that the recipient needs to authorize your request before the copy occurs.xxxx - They click Confirm.
- After successfully sharing the data with the recipient, the sender can see the pending copy request at the top of their Customers page.
Authorise and accept customer data from the sender
The recipient logs into their Stripe account and navigates to the Customers page, where they see a banner at the top advising that the sender wants to share their data. The recipient clicks Authorise and Accept.
The copying process finishes
After the sender completes the previous steps, the copy begins processing. The sender and recipient can see the in-progress copy banner at the top of the Customers page in the Dashboard.
Most data copies finish within 72 hours, after the sender shares the customer data with the recipient and the recipient authorises and accepts the customer data from the sender. Copies of fewer than 10,000 customers typically complete within a couple of hours.
When the copying process is complete, the sender and recipient can see the completed copy banner at the top of the Customers page in the Dashboard. The recipient has the option to download the mapping file.
Copy into or out of a Connect account
If the sender account is a Connect account without access to the Stripe Dashboard, reach out to your contact at the Platform to let them know you need a data copy. The Platform account owner or Data Migration Specialist needs to follow these steps:
Partial copy with customer selection isn’t available for Connect accounts.
If the recipient account is a Connect account that doesn’t have access to the Stripe Dashboard, get in touch with your contact at the Platform to let them know you need a data copy.
The Platform account owner, Admin, or Data Migration Specialist need to authorise and accept customer data from the sender after the sender shares it.
To authorise the data, the recipient logs into the Platform Stripe account, navigates to the Connect page, locates the Connect account where the customers were shared, and clicks Authorise and Accept on the banner in the Customers section.
If your customers are stored in a Platform account that you don’t own, inform your contact at the Platform that you need a data copy. Direct them to follow the steps to share your customers with the recipient account. Platform accounts typically store customers for several unrelated Connected accounts. Make sure the Platform account shares only your customers, by following the steps to do a partial copy.
Status page
If you’re an account owner or data migration specialist, you can view in-progress and completed copies by going to the Customers page and selecting Copy customers then Status page. You can toggle between Shared data and Received data.
For all other roles, you can view in-progress and complete copies on the copy status page.
Shared
On the Shared tab, you can see copies where your account was the sender account, sharing your customers to other accounts.
In progress copies are copies that are currently processing or where the sender account has initiated the copy, but the recipient hasn’t authorised and accepted it. For Pending copies, the recipient needs to authorise and accept the copy to proceed. Most In progress copies finish within 72 hours. Copies of fewer than 10,000 customers typically complete within a couple of hours.
Previously shared copies are copies that were successful or cancelled from your account to another.
Received
On the Received tab, you can see copies where your account was the recipient account, receiving customers from other accounts.
In progress copies are copies that are currently processing or where the sender account has initiated the copy, but you as the recipient haven’t authorised and accepted it. For Pending copies, you need to authorise and accept the copy to proceed. Most In progress copies in this state finish within 72 hours. Copies of fewer than 10,000 customers typically complete within a couple of hours.
Previously shared with you copies are copies that were successful or cancelled from another account to your account.
Sharing permissions are the accounts that have previously shared their customers with you. For any future copies from these accounts to yours, the sender account still needs to share customer data with you, and you still need to accept the data. Authorised accounts see your business name when they enter your account ID during the sharing step.
View all navigates to the Authorised accounts page, which shows the accounts authorised to send you their data. You still need to accept the data copy requests from these accounts, but these accounts now have the ability to see your business name when they enter your account ID during the sharing step. You can revoke permission from any accounts in this list, which prevents them from seeing your business name during the sharing process. When revoked, future copy requests must be authorised and accepted. Only account owners, admins, and data migration specialists can add and revoke authorised accounts.
Permissions restrictions
Only the account owner or a Data Migration Specialist can perform actions from the sender account. Only the account owner, an account admin, or a Data Migration Specialist can perform actions from the recipient account and download the mapping file.
Learn how to add a team member as a Data Migration Specialist.
India account considerations
Data copies aren’t permitted between India Stripe accounts and accounts outside of India. There are regulations in India that require local storage of certain payments data. As part of our continued investment in India and to meet these requirements, we’re updating our systems and have reviewed the data migrations we offer to Stripe users. The data storage requirements prevent us from proceeding with the data copy you’ve requested. If you attempt to complete a copy between an India Stripe account and an account outside of India, you receive an error message that says copying isn’t permissible.
Note
Tokenised cards aren’t copied.
Get Stripe support
If you run into issues or have any questions when completing the data copy, contact the Data Migration Team with this intake form. You must be logged in to your Stripe account before clicking this link.
In the intake form, for migration type, select Tell us about your other data migration use case, and fill in the form accordingly. If you’ve already initiated a data copy, provide the migration request ID associated with the copy request. The migration request ID is in the pending banner or the status page.