Context
Enrolling in a plan, keeping a subscription in good standing, and enabling a partner service are related steps with different states. ConfiaPlus supports individual, corporate, and negotiated plans, bringing together a catalog, checkout, administration, and applications with telemedicine integrations.
My contribution
I worked across the product experience and services, connecting web, mobile, billing, and provisioning. My work included activation and payment recovery flows, telemedicine provider integrations, and the native bridge required to offer their capabilities inside the application.
How it works
- The catalog presents plans and creates a checkout quote with protection against repeated enrollment.
- The subscription tracks its individual or business model, recurring billing, and payment recovery stages.
- Access entitlements guide partner provisioning, keeping service activation separate from the payment event.
- The application accesses integrated capabilities through a native bridge; support combines knowledge articles and a guided flow.
Technical decisions
Separate billing from access
Payment contributes to subscription state, while access also depends on plan rules and external provisioning. This separation supports reconciliation of pending activations and handling partner failures.
Respect application boundaries
Mobile integration requires coordinating JavaScript, Swift, and Kotlin with the lifecycle of partner capabilities. For support, article search and deterministic steps provide a predictable path for common questions.
What I learned
Subscription products require consistency between what was purchased, billed, and actually made available. I learned to model these transitions and treat native integration as part of the access flow, with the same care applied to the API.
Limits and next steps
- The support described uses article search and a deterministic guided flow; it is not presented as generative RAG.
- The image comes from the public website. No consultation, medical record, or beneficiary data is shown.
Credits
Developed at PuggyWare in collaboration with the team.