#pispros_api
brazen belfryBOT
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.
- pispros_subscription-events, 2 hours ago, 13 messages
glacial trailBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1255273651591319562
đ Have more to share? Add details, code, screenshots, videos, etc. below.
glacial orchid
Hi there
Can you share more details? Which webhook events in particular are you listening to?
glacial orchid
I'll need more information. How are you currently integrating with Stripe? What kind of process are you hoping to kick off after receiving events?
delicate fractal
I went to investigate on some private informations that are sent trougth webhooks. Informations used to make some validations checks on my side. I suspect data are not sent correctly
I want to process subscriptions auto renewals
glacial orchid
And how are you currently integrating with Stripe?
delicate fractal
using nodejs
glacial orchid
Are you using the PaymentElement, Checkout Sessions, or something else?
delicate fractal
Checkout Sessions
glacial orchid
If a customer pays via a Checkout Session, you can use checkout.session.completed to be alerted of this payment. If your goal is to store the email that these customers provide, you should create the Checkout Session with customer_creation: 'always' and listen for customer.created events
delicate fractal
Yes, already implemented and working very fine. Now what we want is after checkout.session.completed event, i should receive auto renewal events without the customer even doing anything, is it always 'checkout.session.completed' i get ? i had a problem with a customer auto renewal (the platform can loose his subscription due to that) thats why i want to see all webhooks events related to that customer. There are also some private informations in metadata i must dig in
glacial orchid
When working with Checkout Sessions in mode: subscription, you will only receive a single checkout.session.completed event. This event will be sent as part of the initial invoice/subscription sign up.
What metadata exactly? Where is metadata being added?
It'll help if you have an example request
Once the subscription is cycling, we recommend listening for invoice.paid events to know that a customer successfully paid for the next billing period: https://docs.stripe.com/billing/subscriptions/webhooks#events
delicate fractal
Okay, thanks, yes i need some metadata in subscription object. They are sent back with 'checkout.session.completed ' event. I'll need these informations when renewing the subscription too
glacial orchid
You can add metadata to a Subscription when you create the Checkout Session: https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-subscription_data-metadata
However, this metadata won't be included in checkout.session.completed. Since checkout.session.completed returns a Checkout Session object, the only metadata returned in this event will be any metadata you add to the Session object directly, not the Subscription object