HomeAboutProjectsServicesCubieTecBlogContact
PAYMENTS

Building escrow that survives real disputes

Holding money is the easy part. Deciding who gets it when two people disagree is where the design work is.

Escrow sounds simple: hold the buyer's money until the seller delivers. The code for that is perhaps a day of work. Everything else is policy.

What counts as delivered? For a digital key, the moment it is revealed. For a subscription top-up, the moment the provider confirms. Each product type needed its own definition before a line of code made sense.

Disputes need a clock. Without deadlines a case sits open forever and the money sits with you, which is a liability. Ours auto-resolves in the buyer's favour after seven days of seller silence.

Every state change is written to an append-only ledger. When someone asks where their money went eight months later, you need an answer that does not depend on memory.

Fourteen months in: zero unresolved disputes and no manual ledger corrections.

Written by Mr Mehedi Work with me →
KEEP READING

More posts

All posts →
ENGINEERING

Why instant digital delivery is harder than it looks

An order that completes in two seconds needs a queue, a retry policy and a refund path. Here is the architecture that finally held under load.

Read post →
AI

Putting an AI assistant into a product people pay for

Where the API key lives, what each request really costs, and how to stop the model answering questions it has no business answering.

Read post →
DESIGN

Dark interfaces people can actually read

Pure black is a trap. Contrast ratios, glass surfaces, and the three mistakes I made before this site looked right.

Read post →
© 2026 Mr Mehedi. All rights reserved.