Product engine
Limits & Prefund
An engine for the rules that decide what each customer can spend and move, and for the prefund balances that back those movements. It evaluates limits and exposure against funds held, tracks prefund balances, computes a single available balance across the assets a customer holds, and routes changes through approval, all on the same ledger as the rest of the stack.
What it includes
- A limit rule engine that turns your policy into enforced caps and velocity windows.
- Prefund balance tracking, with thresholds you set for top-up.
- Available-balance computation across the assets a customer holds.
- Exposure controls, including overdraft rules you define.
- Approval workflows for changes to limits, headroom and prefund.
On one ledger with the rest of the stack
The available balance is derived from the same ledger of record, computed live across the assets a customer holds and netted of active holds and pending items. A limit is therefore checked against funds that actually exist at that moment, not a cached figure that can drift: the engine reads the live position, applies the cap and velocity window, and either clears the movement or declines it before money moves.
Exposure and overdraft are policy you version, not behaviour wired into code. Headroom by customer, segment and KYC tier, the size of any permitted overdraft, and the thresholds that trigger prefund top-up are all set as maker-checker governed policy, so you can tune what each customer may carry, and prove what was in force when any given decision was made, without changing the engine.