Operators and clients completing payment actions in Stripe's hosted portal now return directly to their originating context in Clientia — the specific organization, invoice, or subscription record they were working from.
Previously, completing a checkout or subscription management action in the Stripe portal would redirect back to the Clientia root, requiring operators to navigate back to the account they were working on. In high-volume sessions, this created a significant friction loop and led to operators losing track of which accounts had been actioned.
The fix encodes the originating record context into the redirect URL that Stripe returns to, so the landing page can restore the session to the correct organization or billing record. This works for both admin-initiated flows and client self-service portal sessions.
We also resolved an issue where failed or abandoned checkout attempts would occasionally redirect to a 404 when the originating session had expired. Failed flows now redirect to a recovery page with the relevant account context preserved.
What changed
- Post-checkout redirect returns to originating organization or billing record
- Works for both admin-initiated and client self-service flows
- Abandoned checkout recovery page with preserved account context
- No session state required — context is encoded in the redirect URL