Import PAN data for Tokenization
KA-04131
787
04/29/2025 23:50 PM
2.0
Migrating data to our systems requires three-steps:
- Integrate your site to our platform.
- Request your customer data be sent to our Migrations Team from your current provider.
- Update your systems to link your customer’s information to the new IDs we create in your Cybersource account.
Complete your site integration
We provide user-friendly APIs that let you process payments and keep your customer's payment information securely stored. Consult our Developer Reference Guide for further insights on how to utilize our services.
Take note: There are several necessary adjustments you should consider when migrating data from your previous provider:
- You must reconfigure your customer's records to correspond with the new Customer Token ID and Payment Instrument IDs that will be generated in your account.
- You're expected to manage all updates to your customer's Payment Information prior to the completion of the migration process.
Post-migration Record Adjustment
Upon the completion of your data migration, we will supply you with a mapping output file. This output file will contain the old Customer, Payment, and Shipping IDs from your previous provider, along with the corresponding new IDs that have been created within your account.
Changes During the Migration Process
There could be instances where customers update their payment information in the interim period, after you have requested your previous provider to transfer data but before we've received and imported the data. Any alterations made to the payment method via your former provider during this window would not be included in the data transfer and would consequently be lost. Changes can't be made on our platform either, as the data hasn't been imported yet and the new Token ID for the customer isn't available yet.
However, if required, we can perform a Delta import. This process enables importing new information that was generated after your first import.
Initiating Data Transfer from Your Current Provider to Our Migration Team
When you're ready to initiate the migration process, please contact your existing provider and ask them to commence the data export process. For the sake of data security, we mandate that the data comes directly from them and insist on it being PGP encrypted using our public key.
Here is a list of providers we often support for migration. However, this list isn't comprehensive as providers are regularly updating their processes:
| Adyen | Heartland | Spreedly |
| AZUL | IP Pay | Square |
| Bluefin | Keap | Stripe |
| Braintree/PayPal | MerchantE | Webconnnex |
| Chase Orbital | NMI | Wepay |
| Clearent | OpenEdge | WorldPay |
| FrontStream | PayTrace | |
| Global | Recurly | |
Please note that the success of the migration process also depends on various factors such as the complexity of the application, network infrastructure, and the selected migration strategy.
After your current provider has initiated the export process, please reach out to us and request Client Services to begin the import process for your account.
Please utilize the provided PGP public key for encrypting any sensitive data you send us. We cannot accept data that is unencrypted or encrypted using any method other than PGP.
- Key ID: 65708434
- Key Type: RSA-S
- Key Size: 4096
- Fingerprint: FCF3 F156 58C4 E125 FA5B 7D57 32FA 394B 6570 8434
- User ID: Authorize.Net Migration
Important Note: When initiating a data import with customer service, provide a contact email with your old provider. The data export may take several days to weeks depending upon any issues encountered with the files which will be addressed accordingly. Once the file is received from the Vendor, the data will be imported to your account within 3 - 5 business days.
Important Note: We are only able to import Customer Tokens with their Payment and Shipping details in a PGP encrypted .csv file format. During the import process we cannot import any subscription details. Once the import is completed, you can use our API to create a subscription from the token we create in your account.
Update your systems to link your customer’s information to the new IDs we create in your account
After the migration is complete, we will provide you with an output file in the following format that can be used to update your database:
| OldCustomerProfileId | TmsCustomerTokenId | OldPaymentProfileId | TmsPaymentInstrumentId |
|
OldShipmentProfileId | TmsShipmentInstrumentId | Remarks | |
| This will be the value assigned to your customer by your previous provider | This ID will be assigned to your customer in your account | This will be the value assigned to your customer’s payment information by your previous provider | This ID will be assigned to your customer’s payment information in your account | The instrument identifier token type represents the tokenized Primary Account Number (PAN) for card payments, or U.S. or Canadian bank account number and routing number, known as the Network Token. | This will be the value assigned to your customer’s shipping information by your previous provider | This ID will be assigned to your customer’s shipping information in your account | In the remarks field we will let you know if any row failed to import and the reason for the failure. |
Was this article helpful?