Token Migration
If you are moving to a different payment processor or gateway, TranSafe can assist with migrating your tokenized credit card data to your new platform.
Credit card data can only be released to PCI-validated entities that will process transactions. A current PCI Attestation of Compliance (AOC) must be obtained by TranSafe from your new processor before a card data migration can be authorized. We will also need the processor's PGP public encryption key (4096 bits or greater), which will allow us to securely transmit your credit card data. The key must be publicly available from an HTTPS-hosted website associated with the processor. We cannot accept a PGP key emailed to us or from a file sharing service.
Once we have received this information from your new processor, we will generate an encrypted file containing your customers' stored credit card data and deliver it directly to your new processor. They will be able to decrypt this file and use it to import the data into their system.
Token migration data only includes payment account details. Customer information and recurring payment schedules can be retrieved directly from the TranSafe Portal or API. Token export does not affect our standard customer data retention policy.
The encrypted token export file will contain CSV data with the following headers:
token, create_ts, update_ts, flags, status, cardtype, abaroute, account, expdate, cardholdername, descr, clientref, customer_id, street, zip, descmerch, descloc
The definitions of those fields are as follows:
| Field Name | Field Description |
|---|---|
token |
TranSafe token ID |
created_ts | Unix timestamp the token was created |
update_ts | Unix timestamp the token was last updated |
flags | PROC_TOKEN, ACCT_BUSINESS, ACCT_SAVINGS |
status | ENABLED, DISABLED, AU_DISABLED |
cardtype | Card type |
abaroute | routing number for ACH |
account | Account number |
expdate | Expiration date |
cardholdername | Card holder or bank account holder name |
descr | Description |
clientref | Client reference number |
customer_id | TranSafe ID of a linked customer |
street | Street address |
zip | Zip code |
descmerch | Soft descriptor of merchant name |
descloc | Soft descriptor of merchant location |
Our own public key (for migrating to TranSafe from another processor) is available here.