Token migration from existing gateway to Chargebee Embedded Payments
You can securely transfer your customers' saved payment details (tokens) from your current payment processor to Chargebee Embedded Payments. This ensures your recurring subscriptions continue without interruption, while maintaining data security and compliance.
Prerequisites
This process is supported only in your Chargebee live site. It is not available in the test environment.
You must be onboarded to Chargebee Embedded Payments in your live site.
This migration involves you, your current payment processor, Chargebee, and our payment partner, Adyen.
Steps for migrating tokens
Follow these steps to migrate your customers' saved payment details from your current payment processor to Chargebee Embedded Payments:
Contact your current payment processor and request a migration of customer payment tokens to Adyen.
Notify Chargebee once the request is initiated. This helps Chargebee prepare and support the next steps.
Your payment processor will encrypt the token file using Adyen's public PGP key (Key ID: 2F5E0351) and send it securely to Adyen.
The Chargebee Embedded Payments team informs Adyen to expect the incoming data and shares your merchant details for accurate processing.
After your payment processor confirms the file is sent, update your Chargebee point of contact again.
Adyen processes the encrypted file and returns a new file to Chargebee containing the updated token IDs and required details.
Chargebee will then associate the new tokens with the correct customer profiles in your Chargebee account.
What happens next?
After the new payment methods are added to your Chargebee account, recurring transactions can be processed through Chargebee Embedded Payments using the updated token data. This reduces the need for customers to manually update their payment information and helps maintain continuity in your billing operations. Chargebee will notify you once the migration is complete and your account is ready.