Know what everyone's owed
before the money moves
One payment, several parties, and terms that differ per seller. Set yours below and watch the payment resolve — the same way Fynex resolves it on the real thing.
Model any split. See it settle.
Pick a split type, set your parties and their terms, and watch one payment divide across every one of them — checked and reconciled before it executes.
Your split rules
Each party takes a percentage of the order. The shares must total 100%.
The settlement
| Party | Amount | % of order | Paid in |
|---|---|---|---|
| Seller | £85.00 | 85.0% | GBP |
| Platform | £12.00 | 12.0% | GBP |
| Fynex | £3.00 | 3.0% | GBP |
| Buyer is charged | £100.00 |
Clean shares, and a total that closes. One £100.00 payment, 3 parties, and the lines add up to £100.00. Change anything above and that stays true: what the buyer is charged and what the lines come to are the same number, to the cent.
Illustrative, not a quote: Fynex's own share is agreed per case rather than published, and the 3% here is a placeholder so the arithmetic stays whole. Payment processing costs are not modelled.
The moment your terms stop being uniform, the money stops matching the rule
One seller negotiated a better cut. Another is on an introductory rate for ninety days. A third has a flat listing fee on top of the percentage. A single commission field can't hold any of that, so the arithmetic moves into a spreadsheet — rebuilt by hand, every settlement, by someone hoping nobody checks.
The failure is quiet rather than loud. A percentage gets applied to the gross instead of what actually settled, and you pay out money the payment never brought in. A mid-month change leaves two versions live at once. A refund lands and nobody can say whose share it came out of. None of it raises an error — it shows up as a slow leak, and as sellers who stop trusting your numbers.
From a slider to a rule that holds
What you just dragged is a split rule with three lines. Here's what it takes to run it on real money.
- 1
Write the rule once, per seller
A line per party who gets paid: a percentage, a flat amount, or both on the same payment. Each line carries its own priority, a floor it can't fall below and a ceiling it can't exceed. Payees are addressed by the IDs you already use in your own system.
- 2
Preview it before you trust it
Run any amount through the rule and see what each party receives — gross, cost and net, line by line, down to the remainder. The preview isn't a model of the engine. It is the engine, running the same code and the same rounding the money runs on.
- 3
Activate, and change it from the dashboard
Activating a version atomically retires the previous one, so two can never be live at once. Renegotiate a seller's terms and you edit a rule, not a release — and every past settlement can still be traced to the exact terms that produced it.
The arrangements a real rule can hold
The calculator keeps three percentage lines so it stays readable. These are the shapes the engine actually expresses.
Percentage shares
Held in basis points, so a 2.75% cut is exactly 2.75% and never a float that drifts over a million orders.
Flat amounts
A fixed listing or platform fee on the same payment as the percentages, protected by its own priority so it stays whole on a small order.
Different terms per seller
One rule per seller account, negotiated freely — an introductory rate, a loyalty tier, a partner cut — instead of one rate applied to everyone.
Multi-party allocation
As many payees as the arrangement has: seller, platform, referral partner, fulfilment contractor, all resolved against one payment.
Money held back
Hold a share until the condition you set is met — delivery confirmed, a job signed off, a retention period elapsed — then release it.
A declared over-allocation policy
Four behaviours for when the lines exceed the payment. You pick one up front, and it applies identically every time.
Versioned, effective-dated rules
Every change bumps a version with its own effective date, so the terms that produced a settlement are still on file.
A remainder that goes somewhere
Rounding leaves fractions of a cent. They are allocated by rule rather than lost, which is why the lines and the payment always agree.
What a commission field can't do
Most platforms give you one rate and a place to type it. A split rule is a different object.
Find what you're leaking, for free
Send us your setup. We run a free diagnostic and show you what your payment stack costs you today.
The trust layer most software can't offer
We can be your Merchant of Record and hold the funds. Most tools can't, because they don't hold the licence.
FCA-authorised EMI
An e-money institution via Fondy. We can hold and move your funds.
PCI DSS Level 1
The highest card-data security standard, on by default.
Audit logs
Every movement traceable and ready for review.
Built-in KYC / KYB
The switch that turns the business on.