Services marketplace with payouts
The client pays once, the commission is held at that second, and the contractor's share waits on a balance until the payout leaves with a document.
- Buildfrom $2,850
- Timeline3–5 weeks
- Supportfrom $570/mo
Who this suits: Platforms where the money runs through you and the work is done by somebody else, and the commission is worked out in a spreadsheet.
What is in the first version
- contractor balances
- commission held
- hold until acceptance
- payout requests
The figures above are the package this sits on: Payments and billing. Anything past its edges the calculator adds before the work starts, not after.
How the path goes
- 01
Money arrives whole, splits in ledger
One payment arrives, and the split into your commission and the contractor's share is recorded as entries at that second.
- 02
The contractor's share waits for acceptance
The amount sits on the balance as held, with a date tied to how long the client can still dispute.
- 03
A payout leaves in a batch
Each request carries a document and a key, and a refused payout returns to the balance with its reason.
What decides whether this works or annoys people
A balance is a sum
Entries are only appended, the balance is their sum, and every payout carries a key, so a retried request cannot pay twice.
A refund after the payout
The hold window and the provider's dispute window are different clocks, and the contract says in advance who carries the gap.
A person is not a company
Status, details and reporting differ, so all of it is gathered and checked before a first payout is possible at all.
What to measure once it is live
- payouts leaving without a hand
- time from acceptance to money
- gap between ledger and bank
- refunds arriving after a payout
Why this comes out faster
The shape of this one is known: the states, the edge cases and the things that usually go wrong have been decided before. Nothing here is a template, and the saving is not in your half of the work. It goes into your process, your content and the systems this has to talk to, which is the part nobody can have solved in advance.
A likely stack for this
Picked against the task when we scope it, not decided in advance. This is the shelf it usually comes off.
- Money and the ledgerTypeScriptNode.jsPostgreSQLPrisma
- Payments, payouts and their scheduleStripePaddleTemporalRedis
- Two sets of screens and reportingNext.jsReactClickHouseDockerGrafana
Price it yourself, right here
Five steps, and you can see the number without leaving a contact. The estimate accounts for the kind of work, what you already have and what it will need inside.
These bills do not come from us
- provider fees on payments and payouts
- identity checks on recipients
- bank charges for batch payouts
- the accountant filing payout reports
Asked before the first call
- Who is the seller on the receipt: us or the contractor?
- Yours with your accountant, not ours. Platform as seller means one receipt to the client and a payout after; contractor as seller means the money is theirs and your commission is a separate service.
- Can payouts go automatically rather than by hand?
- Where the payment provider pays out to recipients in your country, end to end. Where it does not, the system assembles the batch file the bank expects and reads its answer back onto the balances.
- Can we change the commission ourselves?
- The percentage, the minimum and the rate by category are settings, and an edit never reaches deals in flight: the rate is fixed when a deal is created. A different shape of commission is code.