#frida-shtise_webhooks

1 messages · Page 1 of 1 (latest)

sand mangoBOT
#

👋 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/1466089811306745868

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

honest locust
#

It's showing the correct context in the Stripe dashboard when I search for the event id (2nd screenshot), but in our system it seems to be received like the 1st screenshot, with context as the connected account id.

Screenshot_2026-01-28_at_16.15.16.png Screenshot_2026-01-28_at_16.18.22.png
plucky escarp
#

What is that first screenshot from? I see all our attempts to deliver that event to your endpoint failed. However, in each delivery attempt I see we correctly set context to the platform account in the request body to your endpoint

honest locust
#

It's Sentry.

I also have some logging in our tracking slack channel with "Could not retrieve Stripe event evt_1SuZ05C5pwlCACYlOK3EY2Wc with context acct_1SuYyNC5pwlCACYl/acct_1SuYyNC5pwlCACYl from Stripe" where the context is built from:
const stripeEvent = req.body as Stripe.Event; const stripeAccountId = stripeEvent.account!; const platformAccountId = stripeEvent.context!; // This is the platformAccountId const connectedAccountContextString = buildConnectedAccountContextString(platformAccountId, stripeAccountId);

export function buildConnectedAccountContextString(platformAccountId: string, connectedAccountId: string): string { return ${platformAccountId}/${connectedAccountId}; }

#

So I don't understand the issue, since the dashboard looks correct as you say..

plucky escarp
#

What version of stripe node is your webhook handler code on?

honest locust
#

I have updated everything to 2025-12-15.clover now. In our code, webhook endpoint and default version

plucky escarp
#

What version of stripe node though?

honest locust
#

"stripe": "20.2.0",

plucky escarp
#

I'm seeing a mix of node versions in your request logs for requests made today both 18.4.0 and 20.2.0. You're positive 20.2.0 is the one running on your webhook endpoint here?

honest locust
#

Yes

plucky escarp
#

Ok this is pretty weird. Internally I'm seeing a similar report and the team mentioned this is a dashboard bug and context should be the same as the account param

#

However that doesn't really make sense to me

#

I think we need to engage with this team to get more clarity on expected behavior here

#

I'm going to send you a link to open a case so that we can communicate there and provide updates

sand mangoBOT
#

Hello @honest locust, we have sent you a direct message, please check it at https://discord.com/channels/@me/1466101393596088360

  • 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
honest locust
plucky escarp
#

Yeah I'm not entirely sure the nuance there

#

If you create a ticket via that above link we'll be in touch and update you

honest locust
#

Would you say its an issue with the platform or connected account? When creating the case

plucky escarp
#

It doesn't really matter

honest locust
#

Oki thanks:)

plucky escarp
#

The case will get escalated to the developer queue

honest locust
#

done! thanks for the help:)

plucky escarp
#

No problem. You'll get a response on that acknowledging you wrote in within the next couple hours and then will get further updates as soon as we get them from the team