We're happy to import your customers and payment methods from any other processor. To start the process, you'll need to request a data export from your current or former processor and ask them to transfer the data to us via a secure connection.
This is our preferred data transfer process:
- We'll obtain your processor's PGP public key (if we don't already have the key, we will request it from you)
- We'll send your old processor an encrypted set of credentials they can use to log into our SFTP server
- Your old processor will encrypt your data with our public key, then load the data onto our SFTP server
- We'll pull the data down and perform the import
Once the import is complete, we will provide you with a logfile containing the customer IDs and payment method tokens that we created in your Braintree gateway. Each customer will be on its own row, and each card will be on its own row below the corresponding customer.
We can import PayPal Billing Agreements as a payment method in your Vault. If you'd like us to import your PayPal Billing Agreements, please provide us with a list of the Billing Agreement IDs and the associated customer email addresses.
We can import Apple Pay cards as a payment method in your Vault. If you'd like us to import your Apple Pay cards, your previous processor will need to provide a file of Apple Pay cards separately from your regular cards. The fields required to import Apple Pay cards are the same as the required credit card fields:
apple_pay_card.expiration. Any optional fields that can be applied to a credit card payment method, can also be applied to an Apple Pay payment method.
We prefer the data be sent to us in CSV format, with UTF-8 encoding. Data provided in any other format may cause importing delays.
There are two identifiers that we'll use to map your data to corresponding customers and payment methods in your vault: a customer ID and a payment method token. We can either generate new customer IDs and payment method tokens as part of the importing process, or we can use values provided by you or your former processor.
The minimum fields we need to import credit cards are:
|The credit card number
|The credit card's expiration month and year - month and year can be together in one field (MMYYYY), or in two separate fields (MM,YYYY)
|012021 (one field)
01,2021 (two fields)
We can import the following fields, though they are not required.
|An alphanumeric string that represents a customer in your Vault; 36 character maximum; must be unique within your Vault; valid characters are letters, numbers, -, and _
|The customer's first name
|The customer's last name
|The customer's company
|The customer's email address
|The customer's phone number; may contain dashes and/or an extension
|The customer's fax number; may contain dashes and/or an extension
|The customer's website
|An alphanumeric string that represents a payment method in your Vault - 36 character max
|The cardholder name associated with the credit card
|The first name associated with the credit card's billing address
|The last name associated with the credit card's billing address
|The company associated with the credit card's billing address
|The credit card's street address
|123 Fake St
|The credit card's extended address (also known as address 2)
|The credit card's locality (city)
|The credit card's region (state)
|The credit card's postal code
|The credit card's country name
|United States of America
|The credit card's ISO 3166-1 numeric country code
|The credit card's 2-letter ISO 3166-1 alpha-2 country code
|The credit card's 3-letter ISO 3166-1 alpha-3 country code
|The credit card's default status - If a customer only has one credit card, this field will be "yes"
|All custom fields associated with the customer in your Braintree Vault
We can map data to any custom fields you have in your Vault. Please let us know the name of your custom field, which is listed as the API name in the custom fields settings in your Control Panel.