Gig work and servicesMobileWebAdminPayments

Escrow Marketplace

The platform holds the payment and releases it to the worker only after the job is accepted

What it gave the business

Escrow removes the one thing that keeps a two-sided platform from taking off — distrust. Until the platform holds the money, the client will not pay upfront and the worker will not show up.

The problem

On a gig platform both sides fear each other: the client fears paying for nothing, the worker fears working for nothing. The only way to remove that fear is money held by the platform.

My role

Mobile app, web build, admin panel, the payment flow with holds and payouts, plus native modules for iOS and Android.

What was built

  • Escrow: the payment is held by the platform, released to the worker after the job is confirmed, with the platform taking a commission
  • Registration with verification, a catalogue of categories and specialisations, job posting and applications
  • Chat with stories and media, geolocation and maps, reviews, complaints and push notifications
  • The product ships in three parts: a mobile app, a web build as a PWA, and an admin panel
  • Native Kotlin and Swift modules where the cross-platform layer fell short
Client paysHeld by platformfunds frozenJob confirmedPayout to workerminus platform fee

The engineering core

Full escrow on real acquiring: holding, worker payout and platform commission run as separate cloud functions, each operation isolated and traceable. 110k lines, 347 files, some 30 routes — all of it live on iOS, Android and on the web as a PWA.

Stack

FlutterFlutterFlowKotlinSwiftFirebaseCloud Functions

Integrations

Google MapsFCMRemote Config

Tell me about your project

I will tell you how long it takes and what it costs before any work starts. If it is not my kind of task, I will say so right away and point you elsewhere if I can.

Message on Telegram
Next case
Creator App
→