Middleman
I lead technology and software development at Middleman, a product built around agreements between buyers and sellers. Its public surface connects escrow, chat and payouts with a defined transaction flow.
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.
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.
- 01
Agreement to release: the public site outlines agreement creation, funding, confirmation, dispute handling and fund release, alongside escrow, real-time chat and payouts.
- 02
Transparent transaction terms: the site describes a percentage service fee disclosed before confirmation.
- 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.
- 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.
- 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.
What it turned on.
Hold funds in escrow until the outcome is confirmed.
Buyers and sellers who settle informally have no shared record and no safe way to hold money in between.
Custody brings obligations with it: the published policy covers identity verification and KYC/AML checks.
Disclose the service fee before confirmation, not after.
A percentage of the transaction value has to be visible while the agreement can still be declined.
Stated on the public product site.
Publish signed app-association files for both mobile platforms.
An agreement link should open the app for people who have it, and the website for everyone else.
iOS and Android association files and a midman:// scheme are in the public repository. That shows the configuration is in place, not that the apps are publicly downloadable.
The flow as described on Middleman's public product site.
Agreement
Buyer and seller set the terms in one place.
Funding
Funds are held in escrow rather than paid directly.
Confirmation
The outcome is confirmed before money moves.
Dispute
Contested transactions enter resolution.
Release
Funds are released and the service fee applied.
Public product site and privacy policy in the Divuzki/midman repository.
Public evidence
The product website, public repository and published policies support the descriptions above. The CTO role is first-person experience. Public app-store availability, device-level link verification and individual feature implementation are not asserted.
HAVE A SYSTEM TO BUILD?
Let’s make
it work.
Selected software contracts and business automation. Tell me what needs to work better.
↗