#kstefanova_api
1 messages · Page 1 of 1 (latest)
👋 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/1295637266533842987
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there, is it about how to migrate sources to payment methods API?
Yeah, but sources that are created in connected accounts, the migration guide identified only SEPA DD sources in our main account.
Do we need to do something else for all card/SEPA DD (i think this is only on out test environment) sources in the connected accounts
Ok, so you are using direct charges with Sepa direct debits? Are your connected accounts of type standard?
Ok. Sources API is already deprecated, and I'll highly recommend you to transition to PaymentMethod API instead. https://docs.stripe.com/payments/payment-methods/transitioning
I'm not sure why your connected accounts weren't notified about the migration, did they check their SPAM folder?
Since the migration is related to non-card sources, and all sources in the connected account (but 2) are cards, should we migrate them as well?
Sources API is not compatible with SCA (Strong Customer authentication or 3DS), so if your connected account is in a region where SCA is required, then you should migrate
see the warning - While we don’t plan to remove support for card payments, we recommend replacing any use of the Sources API with the PaymentMethods API, which provides access to our latest features and payment method types.
Sorry I wasn't clear. I mean you should migrate from Sources API to PaymentIntents API, which support SCA and also card sources.