#florian_webhooks
frozen elmBOT
👋 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/1358719578271780954
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
glad galleon
hi there!
steady raft
Sorry, I've made a mistake for code URL: https://www.codebin.cc/code/cm96t0gmj0001kv030smlyfej:961EeddxopYLzW7ykDUQMBz6EP9BNgqfLmmfs4WD2s33
glad galleon
so you have an issue with the webhook signature verification error? have you read this guide that talk about this? https://docs.stripe.com/webhooks/signature
steady raft
Yes. I manage to receive events without any problems. But I can't verify my users when trying to access to a protected endpoint of my back-end. I try to replicate the code example here: https://github.com/stripe/stripe-apps/blob/dd253917643b9bd0d61f5adfe8f67f5c31f0aed6/examples/basic-auth/backend/src/index.ts#L58
I use this method in the Stripe App
async (uri: string, { headers, ...options }: RequestInit = {}) => {
const headersObject = new Headers(headers);
headersObject.append("stripe-user-id", userContext?.id ?? "");
headersObject.append("stripe-account-id", userContext?.account.id ?? "");
headersObject.append("stripe-signature", await fetchStripeSignature());
return await fetch(uri, {
...options,
headers: headersObject,
});
},
[userContext]
);```have you read the link I shared? have you tried everything that is mentioned there (double checking the secret, making sure you use the raw body, etc.)
steady raft
ok, let me read it again and try everything. I will keep you updated. Thanks 🙂