Insights / E-commerce and marketplaces
Milestone payments in a marketplace: what to model
Marketplaces that connect clients with contractors often hold payment until agreed work is done. It protects both sides, but only if the system models the money flow precisely. Screens are the easy part.
Define the states a milestone can be in
A milestone might be agreed, funded, in progress, submitted, approved, released, or disputed. Write each state down and list which actions are allowed in it, and who may take them.
Decide what releases the money
Is it the client's approval, an automatic release after a number of days, or a decision by an administrator? Each choice changes the risk for each side, so make it explicit in the product and in the terms.
Plan for disputes early
- How a dispute is opened, and by whom.
- What evidence each side can submit.
- Who decides, and what outcomes are possible: full release, refund or split.
Keep an audit trail
Every state change should record who did it, when and why. When something goes wrong, the trail is how you explain it to both parties.
Treat payment providers as unreliable
Payments can time out, be reversed or arrive late. Design for these cases, and reconcile your records with the provider regularly.
Getting these rules right before development saves expensive rework later, and it is what makes a marketplace trustworthy.
More from Insights
Practical notes from our project work.
Designing an offline-first point of sale
A point of sale that stops working when the connection drops costs a shop real sales. These are the design decisions that keep a till running offline and in agreement with the server afterwards.
How to scope a software project before you ask for quotes
Vague briefs produce vague quotes. A short, honest scope helps you compare studios fairly and avoids surprises once work starts.