All data related to a credit card migration should be encrypted using industry standards. Recurly’s PGP key can be found at https://docs.recurly.com/docs/pgp-encryption. For security reasons, please note that Recurly cannot accept any data that is not encrypted.
Recurly prefers the credit card data to be provided in a column-separated document with a header line identifying each column. If alternate arrangements need to be made, this must be approved by Recurly. UTF-8 encoding preferred.
Your technical coordinator for all imports is Rachel Quick, Senior Director of Customer Support. For ease of communication, please use email@example.com for all import-related discussions
Credit card data will only be stored for short time periods in an encrypted format. Recurly will delete the records once the import is complete.
Recurly manages imports from providers like Authorize.net, Stripe, Braintree and Zuora on a frequent basis. A test import of data should not be required unless working with a different payment processor.
Merchants should test the process of importing their subscriptions to validate their scripts. These tests can be done on a sandbox site using test gateway credentials and card numbers. Recurly strongly encourages this test before moving into production mode import of data.
One of the most critical pieces of the credit card import is account code mapping. This is necessary since the only identifying information Recurly will receive from your gateway provider is their internal UUID. If you wish for accounts to be created inside of Recurly with a specific account code, please supply Recurly with a two-column CSV - one column identifying the payment provider’s UUID, the other column your ID, to be used as the Recurly account code. Please note that once created, a Recurly account code cannot be modified.