#ayesha-shaikh_api

1 messages · Page 1 of 1 (latest)

frosty cipherBOT
#

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

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

summer star
#

The email
[Action Required] New requirement for ACH debits by March 20, 2026

Starting March 20, 2026, Nacha (the governing body for the ACH network) requires transactions to include the word "PURCHASE" in payment files sent to banks when consumers use ACH debits to purchase physical or digital goods online. This helps banks better identify and monitor certain ACH transactions.

grave kite
#

👋 As far as I know, you should be able to do this from Settings → Payment methods → ACH Direct Debit. But it's not something my team knows much about, you would probably be best contacting support who will know more of the details about these new requirements https://support.stripe.com/contact

frosty cipherBOT
summer star
#

any idea if we are using Stripe Subscription & Invoice with payment method/sources.
how do I classify at it transaction levels?

#

there is a new field in payment intent api, but I am not sure how this will work if we are using Stripe Subscription & Invoice with payment method/sources.

velvet echo
#

hey there 👋 it doesn't look like there's an equivalent field in the Subscriptions API for the new PaymentIntent API field - I'm just double checking to make sure

#

yeah I can confirm that the only way to classify transactions via the API is if you're using the PaymentIntents API for one-time payments

#

since you're using Subscriptions and Invoices, you'll need to configure this behaviour in your dashboard settings

#

as you noted, since you have developer level access your access to dashboard settings is restricted, so you'll need to ask someone with admin access to make any change in the account settings

summer star
#

thanks!
just to reiterate once
So transactions can be classified with API only if we are using payment intents API for one time payments (which we are not).
We need to use the dashboard settings to classify ACH transactions.

velvet echo
#

yes that's correct 🙂