Native to Aquantiz Core. No mapping project.
Shield reads customers, accounts, GL products and transaction channels exactly as the core stores them. No data-mapping project, no vendor-only rule engine.
- 01TransactionCustomer transactions from Aquantiz Core enter Shield.
- 02Entity filtersQuick customer, account and product checks run first.
- 03Behaviour & networkDeeper pattern analysis runs only on what remains.
- 04VerdictHighest severity wins; other hits are kept as evidence.PROCEEDHOLDBLOCK
- 05Case → reportOne case per customer, officer approval, then the report.
Your rules. Your thresholds. Regulator-ready.
Drag attributes onto two lanes, Entity Filters and Detection Analytics, in the Rule Engine Studio. Each node holds one clear condition, and either branch can conclude with a verdict.
Live test bench
One rule, tuned per segment.
Numeric conditions become tunable thresholds. Set one Default and fine-tune it by peer group; a blank cell inherits Default. Move the record and watch the rule explain itself.
Illustrative values. Each alert records the exact cutoff used and the set it came from.
Inside the transaction
Real-time
Screens the payment as it happens and can hold it before it leaves the bank.
Seconds later
Near-real-time
Deeper behaviour and network analysis follows moments after posting.
On schedule
Batch sweeps
Periodic sweeps across the book on a separate workload pool.
Ready on day one: a standard scenario library.
Starting calibrations per bank type, tunable by the bank. Banks can also build new scenarios from scratch.
Screened at every door. Governed at every step.
Sanctions & banned-list screening
Exact, fuzzy and phonetic name matching, aliases and ID matching, each with a match score to cut false alarms. Cleared false positives are remembered.
- At onboarding. A confirmed match stops the account opening.
- On list updates. Existing customers are re-checked against changed entries only.
- On payments. Remitter and beneficiary names are checked inside the transaction.
Governed and auditable
- Maker-checker on rules, thresholds, suppressions and case decisions; no one approves their own change
- Versioned rules, with exactly one active version
- One case per customer with a complete evidence trail and customer clarifications
- Principal Officer approval before each suspicious transaction report
- Time-boxed suppressions that need a second approver
- Monthly compliance deadline alerts for open cases
Visual rule designer
Build, test and approve rules on a canvas. No code, no vendor tickets.
Segment-wise thresholds
One default, fine-tuned for retail, MSME, NRE or corporate customers.
Explainable alerts
Alerts show the condition that fired and the cutoff crossed.
No load on the core
A dedicated AML database fed with customer data only.
Enterprise scale
Scale-out detection for corporate banks.
AI fraud scoring
Models score transactions alongside the bank's rules, with reasons shown.
One Fusion. Explore the other dimensions.
See Aquantiz on your own data.
Tell us about your bank and what you would like to solve. We will get back to you to arrange a demo.