All Collections
Help Center
Manage Accounting
Migrating Credit Card Tokens Between Payment Processors
Migrating Credit Card Tokens Between Payment Processors

Requirement and procedure for customer card details

Derek Deng avatar
Written by Derek Deng
Updated over a week ago

What Are Credit Card Tokens?

While using ServiceBridge you may have opted to store a customer's credit card on file to use for recurring payments. In this case, ServiceBridge doesn't actually store the credit card data, but actually stores an encrypted token.

Credit Card tokens are encrypted files that contain your customers' credit card data. The original card data is typically stored by your credit card payment processor. This data can moved to a different payment processor by request when you switch payment processors. This is useful when you switch to a new payment processor that offers lower rates since you will be able to keep more of the recurring payment. The process of moving tokens between two payment processors is called token migration. 

Note: If you have less than 300 recurring payment credit cards on file, it is recommended that you do not migrate tokens.

There are three steps for a successful token migration:

  1. Requesting token from old payment processor

  2. Send tokens to new payment processor

  3. ServiceBridge support team maps tokens to your customer records



Before you can export tokens from, there are a few requirements that need to be met.


  • The person requesting the token export from must be the account owner on the account.

  • will let you extract tokens up to twice a year at no cost.

  • Automated Recurring Billing (ARB) or Customer Information Manager (CIM) must be enabled on the account.


  • Extractions take place every Wednesday and Friday

  • Files can take 2-4 weeks to be delivered

Other Considerations:

  • Only active ARB subscriptions will be provided, any inactive profiles will not be included in the extraction file

  • Files are delivered to you via Visa Secure email (Note: the files will expire in 7 days from the date of delivery for security reasons. If you do not download the files in time we can resend the email.)


Requesting Tokens from

1.) Reach out to Authorize.Net support and request a Token Migration. 

2.) Authorize.Net will assign a Data Migration specialist to assist with the process.

3.) You will need to create a PGP Encryption key. This key will be used to encrypt and protect the file. It is recommended that you use 4096 bit encryption.

4.) Copy and save the public key and private key text.

5.) Send the public key to the support rep working with you.

6.) will send you an encrypted export of your credit card tokens by email using a VISA Mail Express link.

7.) Send your tokens to CardConnect by following the steps below.


Send Tokens to CardConnect

1.) Send an email to and let them know you would like to send them an Authorize.Net token migration file. 

2.) CardConnect will review your account, confirm a few questions, and request the token file you received from Authorize.Net.

3.) Send encrypted file to CardConnect via email.

4.) Once they've confirmed they have imported the data successfully, you are all set. This process may take up to 5 days.

5.) Contact ServiceBridge support to map your migrated tokens to your customer records by following the steps below.


ServiceBridge activating tokens

1.) Contact ServiceBridge support and ask them to re-map your credit card tokens.

2.) If the file import from to CardConnect was successful, then ServiceBridge will automatically receive a copy of the file.

3.) If the ServiceBridge support team has a copy of your file, they will re-map your customer records from your old token to your new CardConnect token. This process may take up to 24 hours. The ServiceBridge support team will notify you when the token re-mapping is complete.

5.) Your customer recurring payments should now be flowing through CardConnect.


Did this answer your question?