Middleman

The problem.

A transaction involves more than a payment. Buyers and sellers need shared terms, a funding step, a way to confirm delivery and a route for handling disputes. Middleman's public product describes these stages together rather than leaving the agreement outside the transaction.

My part in it.

As CTO, I lead technology and software development for Middleman.

The shape of the challenge.

The public artifacts show the product surface and mobile-link configuration, while implementation details remain private. The policy documents describe identity verification and KYC/AML checks; they do not establish independent compliance certification. App association files identify configured iOS and Android clients, but are not proof of a public app-store release or a successful device-verification test.

What went into it.

1. 01

   Agreement to release: the public site outlines agreement creation, funding, confirmation, dispute handling and fund release, alongside escrow, real-time chat and payouts.

2. 02

   Transparent transaction terms: the site describes a percentage service fee disclosed before confirmation.

3. 03

   Mobile entry points: the public repository includes iOS Universal Link and Android App Link association configurations for app.midman.middleman, plus midman:// links into the application.

4. 04

   Product policies: Middleman Technologies Ltd is named in the published privacy policy, which covers wallets, escrow, challenges and identity verification for KYC/AML checks.

5. 05

   Separate API hostname: api.midman.app resolves independently from the website. This is evidence of a separate public endpoint, not a disclosure of its internal architecture.