#jarrett_api
vapid sleetBOT
👋 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/1395523619433611306
📝 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.
- jarrett_api, 46 minutes ago, 8 messages
trail kestrel
Hi there - what's your current question?
broken rover
how did this previously work
we have elements_enable_deferred_intent_beta_1 in our code
did this beta end or something?
broken rover
so how did this suddenly break our integration is what I'm confused about
trail kestrel
You were getting this error on frontend requests, right? Did you upgrade a Stripe.js version?
broken rover
no we haven't changed anything recently
i see defered intent mode in the URL
but not sure where elements is getting that from
also I gather we don't need elements_enable_deferred_intent_beta_1 in our code anymore?
trail kestrel
No, you can use that feature without a beta header. Though I would recommend referencing the guide since the GA version may be different than what you were using in beta
https://docs.stripe.com/payments/accept-a-payment-deferred#create-intent
but to be clear - I know you provided the failing element sessions request, but what is actually happening/not working in your integration that was working before? Where are the problems occuring?
broken rover
the error i shared
trail kestrel
Right but in the Customer experience, what is happening?
trail kestrel
and do you know roughly when this started? Was the request you shared the first instance?
broken rover
no idea, when it first started or if that's the first instance
it seems if the invoice has a payment intent that has ACSS Debit on it, then it breaks
but i don't know how anyone would pay ACSS Debit then
what needs to change about our integration to support that payment method
trail kestrel
you would need to create a PaymentIntent on the server and pass its client secret to the client before creating/rendering the Payment Element
broken rover
we are doing that tho
vapid sleetBOT
light bobcat
👋 Taking over this thread, catching up now
ACSS debit is not supported on the deferred intent flow.
https://docs.stripe.com/payments/accept-a-payment-deferred:
This integration path doesn’t support BLIK or pre-authorized debits that use the Automated Clearing Settlement System (ACSS).
If you add acss_debit to your integration recently, this will not work
broken rover
we didn't though
light bobcat
what is your question exactly? are you looking to find out why an invoice has ACSS debit, or how to get ACSS debit supported in your integration?
broken rover
the latter
light bobcat
If you use deferred intent flow (create Setup Intent / Payment Intent later), then ACSS debit can't be supported. You will have to use standard Setup Intent flow (i.e. create Setup Intent first) to collect the ACSS payment method: https://docs.stripe.com/payments/acss-debit/set-up-payment
Or you can save the ACSS payment method when the customer makes payment using Payment Intent: https://docs.stripe.com/payments/acss-debit/accept-a-payment
broken rover
the invoice was created and finalized and the payment intent is being passed in
i guess i have to dig deeper into how our integration is functioning
light bobcat
If you have an existing Payment Intent from invoice that has acss_debit as the supported payment method types, then you can pass its client secret to Payment Element to complete ACSS debit payment
broken rover
is there a way in the dashboard to see the history of a PMC so I can see when ACSS was enabled
light bobcat
Let me check if this is possible in the Dashboard
You can go to Security history page: https://dashboard.stripe.com/settings/security_history > filter by "A payment method setting changed"
However, this can't be further filtered by individual PMC
You can click into each of them to find out which PMC has been changed and its request to see when ACSS was enabled