Logic in declarative formats
What happens to a payment is described as data: short rules, each answering one question, read by the engine.
Read the articleRiver · demo stand
Configurable rules
Routing, fees, screening and capture are rules kept as data. AI drafts a new rule, a person accepts it, and it runs beside the old one.
Data views for every role
The same record read as tables for finance, operations and audit: cost by bank, reconciliation, exceptions.
A full audit trail
Every action inside the processing of a payment is recorded with its cause and never rewritten.
AI · sets up the rules
01 · Order
order accepted, invoice issued
02 · Screening
risk scored, rules passed
03 · Route and fee
Acquiring 1, on-us, fee priced
04 · Capture
captured after picking
05 · Shares
shares allocated, ledger balanced
06 · Bank settlement
the bank’s report reconciled
The trail of one payment · an example of the demo stand
Audited
every decision with its cause
Analysed
cost, reconciliation, exceptions
Extended
a new rule beside, not instead
AI reads and proposes · a person decides
§ 01
What happens to a payment is described as data: short rules, each answering one question, read by the engine.
Read the articleWhat must never happen, what each unit may do and how risk is handled. Every payment records the rule version that decided it.
Read the articleEach online card payment goes to the acquiring chosen by approval rate and expected fee, within limits the company sets.
Read the articleScreening is a stage of every payment: a score with its reasons, the unit’s rules, a hold for a person, alerts and onboarding checks.
Read the articleEach role sees the same payments in its own tables, and every figure traces back to its record.
Read the articleA person is given a role at one unit of the company’s tree and sees that unit with everything under it.
Read the articleA new bank, rule or instrument is added beside what works, checked first, and accepted by a person.
Read the articleEvery step of a payment is recorded with its cause, and the record is never rewritten.
Read the article§ 02
One record of every payment and rules stored as data: how the record is kept and read, and how a change is checked before it is used.
Read
Five records hold a payment: the order, the invoice, the attempt, the payment and the settlement.
Read
Orders from the order system, invoices adjusted after picking, corporate invoices on terms with reminders.
Read
Cards, wallets, pay by bank, QR and transfers, instalments and points: different first steps, then one path.
Read
The shares of each payment, set in advance and always adding up to the captured amount.
Read
Sales, the acquirer’s report and the bank credit, compared for every bank, unit and day.
Read
The company as a tree of units: policies apply downwards, flows are visible upwards.
Read
Agents read the views and propose with evidence; people decide, and every decision is recorded.
Read
§ 03
Yarmarok Retail Group
Payments manager: routing and costs
Routing strategy and threshold, on-us share, effective rates, the terminal banks of the regions.
Open the cabinet
Yarmarok Retail Group
Finance controller: reconciliation
Settlement batches reconciled three ways, the differences and the claims.
Open the cabinet
Yarmarok Retail Group
Risk and fraud
Screening rules, held payments and alerts.
Open the cabinet
West
Read-only view
One region, read only: card turnover and costs, settlements and payments.
Open the cabinet