#connor_stripejs-metadata
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/1427791037891477655
đ 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.
- connor_workbench-event, 6 days ago, 10 messages
Continuation of 'What are you working on?'
When a user is presented with a 3DS modal (in our case, upon invoking confirmPayment), I would like to record some information about the user in a way that would be exposed on any webhook events that result from either the success or failure of 3DS
Ah drat, do any workarounds come to mind?
I saw that the confirmPayment SDK action appended a few promising values to the request:
"client_attribution_metadata": {
"client_session_id": "9cc35427-fc71-4177-95c2-03d80005f803",
"merchant_integration_source": "l1",
},
but I didn't see any way for me to control that data