#tempest_ach-nacharule
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/1484256869630345408
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
hello! fyi the server is a little busy atm but i will be with you asap 🙂
ok coming back to this now (although i am juggling a few threads so my responses may be delayed) - just to clarify, are you asking about how to handle this from a compliance perspective, or are you asking how to update this via the API? if so i think the correct flow is to update the payment intent and pass in this field:
https://docs.stripe.com/api/payment_intents/update#update_payment_intent-payment_method_options-us_bank_account-transaction_purpose
This is a compliance issue. Are we able to update payment intent that is generated as part of a subscription invoice before it is finalized?
HI đź‘‹
I'm stepping in as my colleague has to go soon
How are your customers updating their defaulty Payment Method?
They are updating their payment method using our mobile app. Our system makes an api call to Stripe.
Okay so it's an API request from your server, that you control. Not through a Stripe surfce like a Customer Portal
And this isn't something you can apply globally? Through the Stripe Dashboard?
We will have automatic classification enabled but we want to ensure at the payment level it’s classified as “goods” for some transactions to avoid being out of compliance.
Our doc points out
This field is optional. If you don’t provide a value, Stripe uses your ACH classification setting in the Stripe
The one we care about is what is my question
If you don’t configure a Stripe Dashboard setting, Stripe classifies transactions automatically based on available signals such as business information and transaction details.
Yes but we want to classify existing subscriptions
The Subscription is not classified, the Payment Intents it generates are. I checked all the potential parameters you can pass to our Update API and we dont' currently support transaction_purpose for us_bank_account PMs. Let me do some digging internally to see if there are other ways to achieve this.
Right I understand. The payment intent is how we classify it but given the timing of when it is finalized I don’t know if I can rely on updating the payment intent quick enough before finalizing.
Invoices for recurring payments wait in a draft status for 1 hour before finalizing. The intent is to allow you to update those invoices prior to them charging the customer.
However, we recommend specifying the ACH Classification Settings in the Dashboard as the primary way to control this.