Migrating cards involve mapping card tokens from the new gateway to your customers in Chargebee.
Access your Chargebee app, click Settings > Import and Export data > Bring data into Chargebee.
Review the table and choose the applicable action based on your use case:
| Use Case | Currently Using | Moving To | Action Required |
|---|---|---|---|
| 1. | Stripe, Braintree, Adyen or Auth.Net | Spreedly gateways | Request that your current gateway move your customers' card details to the new gateway's vault. If you have an existing process for transferring secure data (like an SFTP server), Spreedly can use this for data transfer. Send the SFTP credentials to Spreedly, encrypted with Spreedly's key for accessing the server. If you do not have a secure transfer process in place, contact Spreedly. They can help you set up their own SFTP server. You need to provide Spreedly with your public key so they can create a new server and encrypt credentials for you. |
| 2. | Spreedly gateways | Stripe, Braintree, Adyen or Auth.Net | If you are using any of the Spreedly gateways and moving to Adyen, use the same SFTP server method mentioned in Use Case 2. If you want to move to other direct integration gateways, we can handle that using Spreedly APIs. |
| 3. | Spreedly gateways | Spreedly gateways | Our migration engineers can handle this using Spreedly APIs. |
Note:
Changes made in your Live site are irreversible. Hence, ensure careful review of all data before Live site import.
While mapping the payment details to the imported subscriptions, any unpaid invoices other than current-term invoices will not be created.
You can move cards from PayPal Express Checkout to Braintree only.
PayPal Payflow Pro and PayPal Payments Pro are supported in Chargebee via Spreedly and migration of card information from one Spreedly gateway to another is as highlighted in Use Case 2.
PayPal Express Checkout requires a Billing Agreement ID to migrate the payment methods from PayPal to a third-party tool such as Chargebee.
The Billing Agreement ID must be shared at the time of migration.
Payment method of customers with I-series tokens that are generated using PayPal internal billing cannot be used or migrated over to Chargebee.
When you are migrating into Chargebee and bringing in either existing tokens from Ebanx or moving cards from a different gateway to Ebanx, make sure to provide the Document ID and the Billing Address along with the permanent token in Chargebee, as these are required in many Latin American markets to process payments successfully. This needs to be sent as Additional Info. To learn more about the migration process, refer to a detailed document on Migrating Cards.
See also
API References
Was this article helpful?