#canadev_api

1 messages · Page 1 of 1 (latest)

tropic runeBOT
#

👋 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/1235668532503511081

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

cyan perch
#

Which payment method types are you using, currently?

lapis lily
#

The payment_method

cyan perch
#

I can say more depending on the details, but the short answers to your questions are:
1/ Yes, you will need to make change to the way you attached payment methods to customers
2/ Yes, that event would no longer be relevant
3/ For compatibility yes that's still included (note that Card sources are out of scope for the deprecation)

lapis lily
#

But the older code still uses sources.

cyan perch
#

I mean, what kinds of payment types do you accept? Cards? Bank accounts? Sepa?

lapis lily
#

only cards

cyan perch
#

If you only use cards, then the Sources API will continue to work for you as it does now

#

We plan to turn off Sources API support for local payment methods. If you currently handle any local payment methods using the Sources API, you must migrate them to the Payment Methods API. We’ll send email communication with more information about this end of support.

While we don’t plan to turn off support for card payment methods, we still recommend that you migrate them to the Payment Methods and Payment Intents APIs.

#

So, you can still migrate, and we recommend doing so, but it is not required for Cards.

lapis lily
#

Oh, I misinterpreted!