Deep Context: Automating Authorized booking user creation, pause & deletion • Memberships are managed through stripe subscriptions. • Becoming an Authorized user in Descope for booking needs to require an active subscription Why it matters: ‘Automate’ Principal | • We seek not to use people where software can be more reliable and efficient even if handling automation now generates more short-term expense. ‘Simple’ Principal | • We need to keep business operations simple and not rely on humans to be timely or accurate in keeping user authentication systems up-to-date with a member’s current status. • We understand that an accumulation of mixed human and system processes creates operational and technical debt; we are ‘frugal’ with our focus and do not want it defused by maintaining overly complex operations or troubleshooting fragile mixed solutions that can hurt our customers when they fail. Mission: Explore options for linking our stripe membership management with Descope user creation and authorization. End State: • When a new subscription starts with Stripe, a new authorized user is created and set to active in the Descope [obscure_booking_production] project. • When a subscription is paused, the user in Descope is set to disabled • When a subscription is canceled, the user in descope is seto deleted Documentation • Stripe Subscriptions | https://stripe.com/docs/api/subscriptions • Descope API Documentation | https://docs.descope.com/manage/

Create, update, resume, cancel

Looks like there is not a clear pause call

I’ve found it, I’ll have to look closely at our Stripe configuration

We are using their default customer facing experiences, with no custom stuff of our own