Technology
How the live engine is built.
01
System architecture
Three sealed zones. Client identity never crosses into the decision zone.
CHANNEL ZONE
Customer / AI agent
- — Web, app or API session
- — Signed agent mandate
Bank gateway
- — Collects event log
- — Strips identity
DECISION ZONE
Live scoring engine
- — Behaviour features
- — Agent classifier
- — Under 100 ms
Mandate rules
- — Signature + expiry
- — Payee list + caps
- — Always override score
Analyst desk (AI model)
- — Deep review of hard cases
- — Never relaxes a rule
RECORD ZONE
Assessment store
- — Decision, score, reasons
- — Read by signed-in staff
Risk team console
- — Reviews holds
- — Audit export
02
Technology workflow
Seven ordered steps. Steps 2 to 6 finish inside the 100 ms budget.
1
Session starts
Customer, bot or AI agent opens a payment session
2
Events captured
Gateway streams timing, keystroke, API and click events
3
Features built
Timing-gap variation, input counts, automation flags
4
Agent classified
Human, scripted bot or LLM agent
5
Mandate checked
Signature, expiry, payee list, amount and daily caps
6
Decision issued
Allow, step-up, hold or block — stricter rule wins
7
Saved + reviewed
Result stored with reasons; risk team reviews holds
03
Basel IV aligned system architecture
Seven layers, sealed from the outside in. Each layer maps to a Basel IV / Swiss control. Designed for alignment — not a certification.