matt_achv1-deprecation | Stripe Developers | Page 1

void groveBOT Nov 21, 2025, 6:28 PM

#

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

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

#

frail sable Nov 21, 2025, 6:32 PM

#

matt_achv1-deprecation

#

👋 let me have a look. That email was... not as good as it could have been sadly as there are many different edge-cases but it focused more on the most common one where users used the /v1/charges API.

polar rock Nov 21, 2025, 6:33 PM

#

appreciate that!! thank you for your help... i think we've discontinued any use of the /v1/charges API but we had a pretty messy upgrade of the SEPA endpoints whenever that happened, so I just want to make sure well ahead of time what I need to do.

#

my guess is that those payment ids got flagged because of the "source" parameter use on the PaymentIntent creation call.

frail sable Nov 21, 2025, 6:35 PM

#

Yeah there's a lot of subtlety to this. It's basically any of those

/v1/charges with source: 'ba_123' or source: 'btok_123'
/v1/payment_intents with source: 'ba_123
Any Billing usage (Invoice/Subscription) where the Customer has default_source: 'ba_123 and no default_payment_method

#

Looking at our stats, the last time you got what we call internally an ACHv1 payment was back in May so you seem migrated already I think. But I would recommend chatting with either our support team or your Stripe point of contact(s) to confirm/track this down further.

What you need to make sure of is that your code relies on neither of the 3 things I mentioned above and the 3rd one is the hardest to debug (but you can use Sigma for this if you have Sigma)

polar rock Nov 21, 2025, 6:40 PM

#

3rd one is a non-issue since we don't use those currently. i'll double check /v1/charges usage, but that should be ok. the 2nd condition sounds like it's what the email was about, and with the changes already in place that should also be a non-issue.

#

thank you for pulling stats! that's very helpful.

#

i believe that coincides with the API upgrades that I mentioned we did to eliminate using that source parameter. so this all sounds like it makes sense and we are probably in good shape without any further changes to our integration.

frail sable Nov 21, 2025, 6:42 PM

#

yeah that makes sense. Basically many platforms from like 5/10 years ago used the source trick. We never documented it officially but that's how we made PaymentIntent work with legacy objects and so now we are trying to migrate everyone
I'm glad to hear you seem already fully migrated 🙂

polar rock Nov 21, 2025, 6:43 PM

#

me too! lowered my blood pressure by a few points. I think you've answered my question, so thank you for that! I appreciate you and your help very much; i hope you have a really great rest of your day!

#matt_achv1-deprecation