#ayesha-shaikh_api
jovial brookBOT
👋 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/1493136136703578272
📝 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.
- ayesha-shaikh_api, 3 days ago, 13 messages
mortal remnant
Looking..
final cipher
I had asked this before when we received the email
the other conversation I had recently contradicts this, I am left confused whether we need any changes on our end. Can you please confirm?
mortal remnant
Yes I am looking. Gimme sometime. When exactly did you receive the email? Could you screenshot (make sure to mask sensitive info)
final cipher
okay
mortal remnant
When exactly did you receive the email? Could you screenshot (make sure to mask sensitive info)
Can you elaborate on this part?
final cipher
From: Stripe notifications@stripe.com Sent: Wednesday, November 19, 2025 11:37 AM
Subject: [EXTERNAL] [Action required] Upgrade your Stripe integration to continue supporting ACH payments
screenshot
final cipher
this is the email we got
mortal remnant
Yes I see, looking...
Okie I found an example. Look at https://dashboard.stripe.com/acct_1InFxgGXlQ7PG1un/logs/req_1LKr93SiCai8MY
This is using the /v1/tokens API which is the legacy path
final cipher
so this is not correct? and we do need to migrate to newer APIs
we are sources api for cards as well - that needs to be migrated too?
since we are tight with timeline here I need to ideantify the changes we need to do before 15 May
mortal remnant
Yes, apologize for the inconsistency. Yes you will need to migrate. Both card and ACH
final cipher
but the email never mentioned about cards or sources or token APIs
that caused a big confusion 😐
mortal remnant
Yes the email is about ACH migration, and its deadline is May 15. Card in Source API is not bounded by that deadline, but I would say it could be flagged soon
So my suggestion is migrating ACH first, then card
we are sources api for cards as well
Btw I haven't looked closely on this yet, trusting your message. Do you have sample transactions to review?
jovial brookBOT
final cipher
req_IVjfcidV16UfzX
slow star
Hey! Taking over for my colleague. Let me catch up.
final cipher
since we are tight with timeline here I need to ideantify the changes we need to do before 15 May
final cipher
https://discord.com/channels/841573134531821608/1458051480396496959/145805543638...
this
slow star
req_IVjfcidV16UfzX
This request is still using the legacy sources API yes. You should update it to use PaymentIntent API
final cipher
can you help me understand which of the following will work/ wont work after May 15 2026, if not what needs to be updated
- existing card which were created using source/token apis - will it continue to work if I update subscriptions & invoices with default method as respective card id instead of default source -- and no other change is required?
- existing bank acc which were created using source/token apis - will they continue to work if I update subscriptions & invoices with default method as respective bank id instead of deafult source -- and no other change is required?
- new card payment method created using source/token API
- new bank account created using sources token API
we are using Stripe subscriptions & one off invoices
slow star
existing card which were created using source/token apis - will it continue to work if I update subscriptions & invoices with default method as respective card id instead of default source -- and no other change is required?
This should continue working yes
existing bank acc which were created using source/token apis - will they continue to work if I update subscriptions & invoices with default method as respective bank id instead of deafult source -- and no other change is required?
These no, all ACH payments with charge/source API will stop working after the deadline
new card payment method created using source/token API
These will continue to work
new bank account created using sources token API
You won't be able to do this because they'll fail after the deadline
final cipher
so everything card will work & no other change other than all subcsriptions/invoices to have default payment sources => default payment method is required?
and new & existing ACH payments with sources/token will stop working after the deadline
slow star
yes
But ideally you should migrate all the API to use the new PaymentIntent, as it's been a while that sources and tokens API are deprecated
final cipher
also that means sources API can still be used to list source etc.?
final cipher
But ideally you should migrate all the API to use the new PaymentIntent, as it's...
yes, we need to plan this
for now I want to figure out what needs to be done before may 15 deadline
jovial brookBOT