#lewibs_webhooks
runic warrenBOT
void rockBOT
Hello! We'll be with you shortly. 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.
- lewibs_api, 12 hours ago, 34 messages
runic warrenBOT
đ Welcome to your new thread!
âąď¸ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime!
đ 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/1212408971672035399
đ Have more to share? You can add more detail below, including code, screenshots, videos, etc.
â˛ď¸ 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!
void rockBOT
scarlet pagoda
How are you integrated with Stripe?
Are you using Stripe Checkout or something else?
hard python
i asked this earlier but it got closed so i was not able to follow up
#dev-help message
hard python
How are you integrated with Stripe?
Are you using Stripe Checkout or something ...
im using the payment link
scarlet pagoda
Gotcha. One thing you could do is pass your internal user ID as a URL parameter client_reference_id
https://docs.stripe.com/payment-links/url-parameters#streamline-reconciliation-with-a-url-parameter
That way your internal ID will be sent with the checkout.session.completed webhook event which then you can use to link payments to a customer on your end
hard python
so my confusion with that, is that when the webhook is going, you have no promise of the order that events will occur, meaning the only id that you have access to throuout the process is the customer id and you need to link it only when checkout session completed occurs. Am i correct in assuming this would result in many documents with many different customer ids all linked to the same userid when they make more then one payment?
scarlet pagoda
What other events are you listening to aside from checkout.session.completed ?
hard python
customer.subscription.deleted
customer.subscription.updated
customer.subscription.created
scarlet pagoda
Ah okay.. hmm thinking..
void rockBOT
scarlet pagoda
There's no way to use an existing customer with the PaymentLinks today.
The other option you'd have is to prefill the email of the customer in the checkout page.
Unless the customer manually changes the email on the checkout page, it would stay consistent
let me know if that clarifies @hard python