A marketplace connecting clients with health and fitness professionals, where location-based discovery, scheduling, and payments needed to work as a single flow instead of three disconnected systems.
ProBuddy is a marketplace that connects clients with health and fitness professionals — trainers, studios, and practitioners — for bookable sessions. Discovery, scheduling, and payment all needed to work together as one product experience rather than as separate tools bolted together.
A health and fitness marketplace normally needs three systems that don't naturally talk to each other: location-based discovery (finding a provider near you), scheduling and booking, and recurring or per-session payment processing. Handling these as separate integrations creates friction at exactly the point where a client is deciding whether to book — and creates reconciliation work on the business side when bookings and payments don't stay in sync.
We integrated Mapbox for location-based discovery directly with the booking flow, so finding a nearby provider and reserving a session happen in one continuous flow instead of separate steps. Billing runs through Stripe and Chargebee for automated, recurring, and per-session payment handling, and the platform includes dashboards for engagement and activity tracking.
The system pairs two billing tools rather than one: Stripe handles payment processing, and Chargebee manages subscription and billing logic on top of it — a common pattern when a marketplace needs both one-off session payments and recurring subscription plans. Mapbox powers the location layer that feeds directly into the booking flow, so a user's search results and their ability to book are part of the same interaction rather than a separate step.
We've kept this section to what's confirmed — Stripe, Chargebee, Mapbox, and React. Backend stack, Apple Pay support, and whether any part of the flow is event-driven aren't confirmed in the material we have on file; see the TODO in the page source.
Running Stripe for payment processing alongside Chargebee for subscription/billing logic means keeping both systems in sync — a booking, a charge, and a subscription state all need to agree, or the business ends up reconciling by hand, which is exactly what the integration was meant to remove.
Location search (Mapbox) and booking are often built as separate features that get stitched together after the fact. Integrating them directly meant the map, availability, and the booking action needed to share state in real time rather than round-tripping through separate screens.
ProBuddy is a live marketplace processing bookings and subscription payments through its integrated Stripe/Chargebee billing today.
We don't have client-approved usage metrics on file for this project (bookings processed, active providers, transaction volume). If you can share verified numbers, we'll add them here.
Tell us what you're working on and we'll discuss the technical approach, scope, and next steps.
Discuss a Similar Project
A US-based software development agency with a distributed engineering team, helping startups and growing companies build SaaS products, AI features, and the systems behind them.