A monthly payout run that cannot pay twice
Payout rules for an online marketplace, tested so no one is ever paid twice.
A working sample we built to show how we would solve a problem like this. It is not a delivered project.
In plain terms
A monthly payout run for an online print-on-demand marketplace: partners earn a share after production and shipping costs, refunds are taken back, and some earnings are held. This demo models those rules in code and proves that re-running a payout can never pay the same partner twice.
- Re-running a payout never pays anyone twice.
- Refunds and held earnings are handled by clear rules.
- The tests deliberately break the rules to prove they catch mistakes.
What this does not claim: A plain-code model with a pretend payment service. It is not a live Make.com scenario, and no real payouts were run.
Technical details
The payout rules (partner share after fulfilment and shipping, refund clawbacks, held earnings) modelled as code against a fake Stripe, with idempotent payout records and deliberate-break tests, before anything is built in Make.com.
- Python
- Make.com (logic modelled)
- Stripe Connect (simulated)
- Automated tests
Need something like this?
Tell us the problem in your own words. We reply with a plain, practical plan.
Discuss a project like this