Every deduction, with a reason attached
The settlement engine takes reconciled transactions, applies the fee structure that belongs to that merchant, holds what your risk policy says to hold, converts where it must, and produces both the payout instruction and the document that explains it.
A fee engine, not a percentage
Pricing lives in templates you define and assign, so a merchant on cost plus and a merchant on a blended rate are two configurations of the same engine rather than two code paths. Rates apply per merchant, per MID, per card brand and per currency, and the acquirer cost that reconciliation wrote back onto each transaction is what the calculation actually uses. That is the difference between showing a merchant an estimate and showing them what the transaction really cost.
Fee and terminal templatesReserve that releases itself
Set the percentage and the holding period per merchant and per currency, and every cycle holds and releases on schedule without anyone maintaining a calendar. Held funds are visible as their own balance rather than being quietly netted away, each release is an auditable event, and the merchant can see what is held, what is coming and when. The most common cause of a merchant dispute about reserve is not the policy; it is not being able to see it.
Rolling reserve reportsCurrencies that stay separate
Each currency settles as its own book with its own reserve policy, its own minimum payout threshold and its own wire fee. A balance under the threshold carries forward instead of triggering a payout that costs more than it moves. When a merchant wants everything in one currency the conversion happens at settlement with the FX fee shown as a line of its own, because a spread buried inside a rate is the fastest way to lose a merchant's trust.
Currency conversionIt refuses to pay what it cannot prove
Settlement will not quietly pay out money the platform has not reconciled. Depending on how the programme is set up it can be restricted to reconciliation-matched rows only, or it can stop entirely while funding movements are still outstanding and require a named operator to approve the exception before anything moves. Paying a merchant is the one step you cannot undo with a correcting entry, so it is the step that deserves a gate rather than a warning nobody reads.
How reconciliation feeds itA statement that answers the question
Every merchant asks the same thing: why is this month lower than last month. The statement is built to answer it. Volume, refunds and each dispute type carry their own line, so a representment is never buried inside chargebacks and a recovery is never mistaken for a sale. Behind the summary sits a cost appendix that breaks the total down by component and by dispute type. Statements generate as spreadsheets, appear in the merchant's own portal under your brand, and can be produced for every merchant on the platform in one action rather than one at a time.
Balance and statement rowsBank wireWire fee €25 on statement
BalanceMerchant draws down
From calculation to money out
A calculated settlement is an instruction, not a payment. It goes through approval, then out as a bank wire through your payout providers or as a credit to a balance the merchant draws on themselves, with the wire fee accounted for in the same statement that produced the figure. Because payouts and settlement share one system, a failed or returned wire comes back to the settlement it belongs to instead of becoming a separate mystery for the finance team to chase.
Payouts and balance requests
