#foobarrio-radar-feature
nocturne spear
foobarrio-radar-feature
@grizzled pewter my guess is that you are trying to pass a parameter that is part of a beta/secret feature and that account doesn't have access to it. So you need to work with your point of contact at Stripe or our support team https://support.stripe.com/contact to ask for access
grizzled pewter
I appreciate the reply. I have no reference to radar_options in my entire code base though 🤔
It looks like a stripe-controlled call that is actually passing the param
nocturne spear
Ah okay so I might have misunderstood. Can you share a bit more details about what you are doing, what you see, etc.
grizzled pewter
Sure thing. So I have had a working sign up flow for a few days without issue. All of the sudden it stopped working about an hour and a half ago. No changes to my code base or anything.
nocturne spear
sorry that's just a picture
grizzled pewter
Yes I'm explaining sorry 1 sec
nocturne spear
What are you doing exactly, where is that call/network request coming from?
All good, will wait for the next message with the full end to end explanation
grizzled pewter
I am using the stripe-js SDK version 1.45.0 to create a subscription. I first start by creating a payment intent to generate the pay card element. The error comes after I press the "pay now" button, which then attaches the payment method to the payment intent. We are not manually making this post request - it seems to come from behind the scenes in the SDK. The other UUIDs you see there in the network tab are stripe SDK calls to an hcaptcha service. It looks like Stripe is automatically appending the radar_options param
nocturne spear
okay I'm sorry that's far from enough just yet
Can you give me an exact request id req_123
it's in your picture, I need the value to look at it
nocturne spear
perfect thank you. Can you share your client-side code?
grizzled pewter
Sure. So step 1 we use the Stripe SDK to update the payment intent
this.stripeClient.updatePaymentIntent({
elements: this.stripePaymentElement
}) as unknown as Observable<PaymentIntentResult | undefined>
and that's where the error occurs. The code after that does not process
nocturne spear
yeah okay so you are using a secret feature on your account right now
you likely have a "beta option" somewhere where you initialize Stripe.js right?
grizzled pewter
yea that's right
server_side_confirmation_beta_1
betas: ['server_side_confirmation_beta_1'],
apiVersion: '2018-08-23;server_side_confirmation_beta=v1'
})```yeah so it's a secret feature no one else uses
but I'm digging into it, I do think something is weird, will take me a bit of time (and I think you/someone at your company already escalated to support who is asking the same questions in parallel to my team)
grizzled pewter
Yes that's right. It's critically impacting the business, so we're exploring all channels. I appreciate your help
hard lanceBOT
nocturne spear
okay we found the root cause, we're working on a fix
grizzled pewter
Okay great, thank you for the update.
Can you please help me understand the root cause?
urban mulch
Hi @grizzled pewter This is Jack from Stripe, I'm taking over this thread.
The team is working on the fix, and we will send you an update through email.
grizzled pewter
I appreciate it, thank you.
nocturne spear
@grizzled pewter can you reload and see if it still errors? We deployed a fix
nocturne spear
Note that if an end customer loaded the page before we fixed it, it's still broken, they have to "reload the page"
grizzled pewter
Any details you can provide about the root cause will be very helpful as I inform stakeholders. Please feel free to email that
nocturne spear
Please ask the person you were working with on support for that, we can't really handle emails follow ups here but they can!