Product architecture

How Servio orchestrates trust at scale

A high-level view of the data, decisions and services that power every booking — from discovery to settled payout — in a single mobile-first marketplace.

Core customer journey

Discover

search + filters

Vendor profile

services, reviews

Book slot

rules engine

Pay

held in escrow

Service

check-in / out

Review

reputation loop

Identity & roles

Single identity, three workspaces: Customer, Vendor, Admin. Permissions resolved server-side per request.

Listings & inventory

Vendors expose categorised services with pricing, duration and availability windows.

Rules engine

Composable rules: cancellation windows, no-show fees, commission, blackout dates, surge pricing.

Payments & escrow

Funds captured at booking, released on completion. Weekly payouts with auto-reconciliation.

Notifications

Email, SMS and push channels with templated, locale-aware messages.

Trust & safety

KYC, ID verification, fraud signals and review moderation pipelines.

Rules engine — booking lifecycle

State	Trigger	Rule applied	Outcome
Pending	Customer requests slot	Vendor SLA · 2h response	Auto-confirm or release hold
Confirmed	Vendor accepts	Payment capture	Funds held in escrow
In progress	Service started	Geo / time check-in	Timer + dispute window opens
Completed	Service ends	Auto-release T+24h	Payout queued, review requested
Cancelled <24h	Customer cancels	Cancellation policy	50% non-refundable charge
No-show	Vendor reports	No-show fee rule	Full charge, dispute period opens

System topology

Edge / CDN — static assets, SSR cache, image optimisation

API gateway — auth, rate limiting, schema validation

Services — Listings · Booking · Payments · Notifications · Trust

Data plane — Postgres (OLTP), Redis (cache), object store, event bus

Observability — metrics, traces, structured logs, alerting

Coverage

Countries

Cities