#stevez_link-auth-sesions
supple craterBOT
👋 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. Thank you for your patience!
⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime! If this thread is closed and you have another question you'll need to start a new thread.
🔗 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/1213190950390857738
📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.
queen dewBOT
quasi prairie
What actually happens: I get two auth messages, sorry for that typo
jade shell
Hi 👋
So you have implemented the Link Authentication Element.
https://docs.stripe.com/payments/elements/link-authentication-element
Do you have other Stripe Elements on the same page/form?
quasi prairie
We have the address and payment elements
jade shell
Okay. So basically this integration: https://docs.stripe.com/payments/elements/link-authentication-element#combine-elements
quasi prairie
right but we're using address for billing
jade shell
And where exactly are you seeing the two tokens show up?
jade shell
Okay, the issue I think is that the Payment Element also has Link authentication built into it. I'm testing this out myself
quasi prairie
So more context, we have an implementation that allows us to test the address element
I can turn it (and the link auth element) off
and then we have just the payment element and express checkout element
that also gives us 2 texts (actually just recently that was the only method that gave us the 2 texts aka using the address element didn't send 2 the last attempt I made)
and now I'm hitting the limit for number of authentication requests
jade shell
Sorry, I'm having trouble following. Reading those sentences sounds contradictory.
quasi prairie
We have a checkout that is being tested
jade shell
Can you provide some API request IDs that triggered these notifications?
quasi prairie
how do I get that?
jade shell
They will start with req_
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
quasi prairie
the checkout is being tested with one variation having the address element and the other without
I've seen the 2 texts for both variations
jade shell
When you say with and without the Address Element, does that mean you are including the Link Authentication element in both variations?
quasi prairie
no, only with the address element
when we don't have teh address we just use the payment element
so how would I filter events to find this event?
is there a specific type?
jade shell
How are you using the Payment Element? Are you confirming Payment Intents? Setup Intents?
jade shell
You would look for the request to the /confirm endpoint then
quasi prairie
I'm not seeing any requests with /confirm or /v1/confirm as teh endpoint
jade shell
Can you share the latest Subscription ID that this has been tested with?
quasi prairie
so this happens before a subscription is created
jade shell
Okay... so you are using the deferred intent flow?
quasi prairie
yes, I think its this one ^
so I think this triggers it:
/v1/consumers/sessions/lookup
jade shell
Okay. You mentioned seeing two auth tokens. Do you. have specific requests in the Networks tab you are seeing?
quasi prairie
Let me see if I can get one now (I'm hitting the rate limit while testing this)
so is it the lookup endpoint that you want?
This lookup request appears to have triggered it: req_hoZSD3hAbpbnWB
jade shell
Perfect! Thanks
jade shell
Wait... are you creating a Customer Session? Is that also part of your integration?
jade shell
when you say "start_verification" what are you referring to here?
quasi prairie
so I'm just looking at network requests
when the page loads we get a sessions, lookup and at least 2 start_verification requests (among others)
jade shell
Before the const {error: submitError} = await elements.submit(); function is called?
jade shell
Sorry, what is your page doing when it loads?
quasi prairie
when I load stripe with the payment element there are many stripe network requests that are made by stripe (not us)
for example "start_verification" is at "https://api.stripe.com/v1/consumers/sessions/start_verification"
jade shell
Of cousre, that's normal. But I have a working integration wit the Payment Element + Link Auth and Address Element and I'm not seeing these requests so I'm trying to undestand what is different
quasi prairie
on a page refresh?
here's the response from the start_verification when I hit the rate limit
here is the network tab
jade shell
Can you share the request_log_url value?
quasi prairie
what's that?
jade shell
In the response preview you shared, it's the URL
jade shell
No, the url in the message response. starting with https://dashboard
quasi prairie
I don't see the req there
jade shell
In the screenshot you shared, the first one
quasi prairie
oh
jade shell
The error payload is
{
code: ....
message: ....
request_log_url: this value here
type: ...
}
And these requests are fired before you submit the element?
Can you provide me the JavaScript your page calls when it loads?
quasi prairie
sry important phone call, here's a link to a similiar req: https://dashboard.stripe.com/logs/req_ppI7o9X3WkBjQC?t=1709319599
btw that doesn't show up in our dashboard
jade shell
Yes these are too low level, they aren't saved to the dashboard.
quasi prairie
our integration is producing 4 start_verification (https://api.stripe.com/v1/consumers/sessions/start_verification) requests
2 with type "sms"
jade shell
Okay I've been digging around and I think you will need to write in to Support since this will require more digging into the code than we can provide in Discord: https://support.stripe.com/contact.
I'm sorry
quasi prairie
req_J439hVpbQYh5e8, req_n4Px9aP4MQb88r, req_fBjIz4Q9W3sGrQ, req_x2r2wwvg3MhoW9
ok
thx
jade shell
Yes I can see that you are getting both SMS and WEBAUTHN type verification sessions triggered at the same second
quasi prairie
2 of each
jade shell
Yes. So, to help address this, I would ask that you provide the request ID's you just shared along with the javascript code that creates, mounts, and submits the Payment Element and other Stripe Elements.
We will likely need to reproduce your integration
quasi prairie
ok
queen dewBOT
stevez_link-auth-sesions