sirbuland-atlas_api | Stripe Developers | Page 1

nimble plinthBOT Jul 16, 2025, 10:22 AM

#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1394987642780913785

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

sirbuland-atlas_api, 19 minutes ago, 5 messages

#

fierce ruin Jul 16, 2025, 10:25 AM

#

You don't really need to migrate existing Source objects to PM objects, they're interoperable for the most part (e.g. you can pass src_xxx objects to payment_method params)

#

What is deprecated and not recommended is the creation of new Source objects. So you should ensure your integration only uses Payment Method objects for new payments/customers

#

https://docs.stripe.com/payments/payment-methods/transitioning#compatibility

Migrate to the Payment Intents and Payment Methods APIs

Learn how to transition from the Sources and Tokens APIs to the Payment Methods API.

uncut viper Jul 16, 2025, 10:33 AM

#

Thanks for the feedback, but the issue is i am upgrading to latest APIs and versions. Which does not support my previous code related to sources and cards. So, I want to move existing thousands of my customer siurces(multiple cards) to attach customer as paymentMethods. Please suggest the solution

fierce ruin Jul 16, 2025, 10:36 AM

#

Which code is not supported?

#

The creation of Sources?

uncut viper Jul 16, 2025, 10:40 AM

#

I was previously doing like this
customer.sources.create(source: card_token)
or
customer.sources.data

these will be not working for latest API versions. So I want to migrate all attached cards as sources to paymentMethods. Because in new APIs cards are worked as paymentMethods

fierce ruin Jul 16, 2025, 10:40 AM

#

Yeah, like I said you can't create new Sources but you can still use the existing Sources for payments. There's no need to migrate all those Sources immediately

#

In any case, you can't really do that automatically. The only way is to ask the customer(s) to provide new payment information and then you set up a Payment Method object

uncut viper Jul 16, 2025, 10:51 AM

#

I don't want to use sources for payments and for fetching the sources and tokens, I am getting rid of all old APIs.
Now just moving to PaymentIntents and paymentMethods, so I want all customers attached sources(multiple cards) can be migrated and attached to customer paymentMethods. Is there any possible way instead of asking customer to add card information again. Even if I have thousands of customers attached sources(multiple cards)

fierce ruin Jul 16, 2025, 10:52 AM

#

There is not, no

#

As I said, there's no hard requirement for you to migrate all thoese existing Sources. If you want to do that, then there'll be a lot of manual work for you:

Update all your integration code
New customers will checkout using new APIs
Require existing customers without a Payment Method object to provide new payment details when they try to checkout

#

Adds a lot of friction to your checkout flow, which is mostly unncessary as I've explained. My recommendation would be to slowly migrate them over, rather than ripping the cord like that

nimble plinthBOT Jul 16, 2025, 10:59 AM

#

uncut viper Jul 16, 2025, 11:00 AM

#

I am setting up the automatic tax collection, and remittance through stripe. tax functionality is not supported to the old charges and sources APIs and old API versions. SO I am changing my whole project codebase to latest API versions and will be using the PaymentIntents and paymentMethods.
I already check the feasibility but Tax functionality is not supported in Old versions and New version not worked for sources. Then I plan to upgrade all codebase accordingly but concern is there only for the already attached thousands of customers cards that are attached as a source. I want to attached them as a paymentMethod now so I don't require to ask every user to enter again their cards information. I just want if there is any way of migrating through API or through dashboard that all cards information copied and attached to paymentMethods

green pecan Jul 16, 2025, 11:01 AM

#

hi! I'm taking over this thread.

uncut viper Jul 16, 2025, 11:01 AM

#

sure please read all above messages to understand the context

green pecan Jul 16, 2025, 11:08 AM

#

SO I am changing my whole project codebase to latest API versions and will be using the PaymentIntents and paymentMethods.
sounds good
I just want if there is any way of migrating through API or through dashboard that all cards information copied and attached to paymentMethods
looking into this

#

no you can't directly migrate a Source to a PaymentMethod. but a Source is compatible with PaymentMethod.
for example, when creating a PaymentIntent, you can set payment_method: src_xxx and it will work.

#sirbuland-atlas_api