Migrating legacy Stripe tokens to Payment Method IDs

Some merchants are receiving reminder emails from Stripe about legacy tokens that use the Source ID format (e.g., src_...). While Chargebee has already migrated away from the deprecated Sources API, a few merchants may still have these older tokens stored in their system.

This article explains why you're receiving these emails and what actions you need to take to stay compliant with Stripe's latest requirements.

Why am I receiving emails from Stripe about old tokens or Source IDs?

Stripe has deprecated the Sources API. All new payment methods are now created using Payment Method IDs (e.g., pm_...). However, older payment methods may still be stored in the Source ID format src_....

Stripe sends email reminders if it detects that your account still contains legacy tokens that need to be migrated.

What should I do to resolve this?

To address the issue and stop receiving these emails, follow these steps:

1. Identify legacy tokens

• Check if you have any payment methods saved in the src_... format.

2. Migrate old tokens to Payment Method IDs

• If such tokens exist, contact Stripe to request a migration from Source IDs to pm_... Payment Method IDs.
• Once migrated, update these tokens in Chargebee using the Payment Sources API to ensure your customer records are consistent and future-ready.

3. Collect updated payment details if needed

• In cases where Stripe is unable to migrate certain tokens, you must collect updated payment details from your customers.
• Use Chargebee's Request Payment Method feature to send secure update requests and gather new payment information.

Additional guidance

• Legacy tokens should be removed or replaced to ensure compliance with Stripe's current standards.
• This migration ensures continued compatibility with Chargebee's billing workflows and Stripe's APIs.

If you need assistance during this process, contact Chargebee Support or refer to Stripe's documentation on deprecating the Sources API.