A credit card import is a process managed by Recurly and your current payment provider to manage a secure transfer of credit card data, minimizing a merchant’s scope of PCI-compliance that might otherwise be incurred by handling the data themselves. Because of the strict regulations around credit card data storage, most providers will only migrate data between two PCI compliant vendors.
This process involves collecting the credit card data from the existing payment provider, and importing into Recurly. The end result is a series of accounts with stored billing information, allowing the merchant to then proceed with adding subscriptions or other details to the account.
Card numbers (typically provided by gateway):
Account and billing info (provided by the merchant)
Credit card imports are managed by Recurly for a professional services fee. Please contact your sales representative for a quote.
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.
Prep Work (gateway into, account mapping, merchant checklist)
File delivery (PGP key, security, data validation)
Import (account creation, billing info, skip-auth)
Post-Import (Sub, Coupon, Credit Create)
trial_ends_atdate to match the customer’s original bill cycle date.
unit_amount_in_centsvariable that will override pricing for that user. Alternatively, if the merchant wants to track contra-revenue, they can create (https://dev.recurly.com/docs/create-coupon) and redeem (https://dev.recurly.com/docs/redeem-a-coupon-before-or-after-a-subscription) before adding the subscription to the account at default pricing.
For auditing and technical reasons, Recurly cannot import historical data or backdate subscriptions. A CRM can be used to merge data from multiple systems for a full accounting profile.