#Charles_ - Customer Portal
fallen tapirBOT
keen cipher
Yes, the relevant events will still be emitted by actions on the no-code customer portal
For example, if a customer opted to cancel the subscription via the portal we'd emit a customer.subscription.deleted event for your to listen for and action in your handler
torn prawn
Thanks, just to be super clear; in this section of the documentation (https://stripe.com/docs/customer-management/integrate-customer-portal#redirect) it's outlined that the portal session requires the client to be authenticated on my side before redirecting to the portal.
But if I understand correctly, clients do not need to be authenticated on my app in order for the webhooks to be called and subscriptions to be processed (sending emails with relevant information)?
keen cipher
That's the API integration flow
You're looking at the wrong documentation, we were previously discussing the no-code flow: https://stripe.com/docs/customer-management/activate-no-code-customer-portal
If you use the API directly to create sessions, then yes you'd need to handle authentication to map the related Stripe Customer object to your user sessions
torn prawn
I see, do you mind pointing me to the webhook documentation for the no-code customer portal?
keen cipher
There's nothing specific for that, it functions exactly the same as the API integration in that context. Here: https://stripe.com/docs/customer-management/integrate-customer-portal#webhooks
frail bronze
Charles_ - Customer Portal
keen cipher
The only difference is how your customers get access to the portal:
- Either you create a session for them and redirect (e.g. via the API).
- You enable the no-code flow and we email them a short-lived URL for direct access.
torn prawn
Got it, and in both cases the webhooks will work as expected (even if customers aren't authenticated on my website)?
keen cipher
The functionality and behaviour of the portal outside of the entry method difference is exactly the same
torn prawn
Awesome, thanks again!
keen cipher
np