Ingest interbank transfers, USSD and VAS (value-added service) payments, and GL (general ledger) journals into a client-controlled intelligence layer designed for detection and regulatory reporting workflows.
When supplied by the source channel, network, device, location, and application signals remain attached to transaction activity, helping teams investigate account takeover, device reuse, proxy routing, and geographic inconsistencies.
IP address, network context, and VPN or proxy indicators when supplied.
Each address is resolved to its address version, network classification, autonomous system, and network organisation, so analysts can see whether activity came from a public network and which provider carried it.
Device identifiers and fingerprint hashes available for cross-transaction comparison.
Identifiers supplied by the originating channel stay attached to the transaction, so the same device can be compared across transactions and customers during review.
Latitude and longitude coordinates available for geographic review.
Origin country, state or region, and city are retained alongside coordinates, with the geolocation source named, so geographic context can be reviewed without leaving the transaction.
App version, user-agent, and channel context such as USSD, mobile, or branch when supplied.
The application version, user-agent, and channel the transaction came through are kept with the record, showing whether it originated from USSD, mobile, or a branch.
For a transaction that needs a closer look, AI drafts an investigation summary covering why it was flagged, the customer's history, the counterparty, device and location signals, and an overall risk assessment.
Analysts start from a structured write-up instead of piecing the evidence together by hand.
AI investigation is analysis of a stored transaction. It is not part of rule evaluation, so it cannot change the risk score or the outcome.
If the AI provider is unavailable, ingestion, the rule outcome, and your analysts' ability to review the transaction carry on unaffected.
Switch on automatic investigation in Transaction Monitoring settings and every newly evaluated Flag, Hold, or Block transaction is investigated for you. Anyone who can read transactions can also request one from the transaction page.
A completed investigation is stored with the transaction, with the provider and model that wrote it, and is reused rather than regenerated. Only bounded, non-identifying evidence is sent to your provider.
Every financial institution operates under unique risk tolerances. OneView gives compliance and risk teams an intuitive, no-code rule builder to review live core banking transactions, trigger automated safeguards, and prevent financial loss before settlement.
Create unlimited detection rules without writing a line of code. Target specific payment flows, account types, currencies, or channels, then combine conditions into precise logic with zero engineering dependencies.
Define exact operational responses for every trigger: dispatch instant analyst alerts, hold transactions for in-depth review, reject execution, or automatically apply a timed Post-No-Debit (PND) on the account.
Group rules under Reject, Review, or Alert categories. Automatically flag complex pattern behavior in real time, including rapid multi-account structuring, unusual high-frequency credits, and baseline deviations.
Configure a single hit action and OneView screens live transaction and customer activity against every blacklist entity type your bank maintains, from account numbers to device fingerprints.
Maintain blacklists across customers, accounts, VAS receivers, GL codes, devices, IP addresses, cards, countries, and bank codes, screened against every transaction and customer in real time.
Choose whether a blacklist match blocks the transaction outright or flags it for review, applied consistently across every screened entity type.
Blacklist hits are evaluated together with the rules engine's detection results, giving analysts one consolidated outcome per transaction instead of two separate checks to reconcile.
The same Politically Exposed Person (PEP) and Sanctions screening already available on the KYC module now runs against transactions themselves, available when both PEP & Sanctions screening and Transaction Monitoring are part of your license.
As a transaction is processed, OneView screens both the sender and the receiver against Politically Exposed Person (PEP) and Sanctions lists, the same screening already available on the KYC module, now applied to the movement of money itself.
Turn this screening on or off, choose what happens on a match (flag for review, hold, or block), and set how sensitive the match threshold is, all configurable to your bank's own policy.
Screening runs in real time as part of transaction processing. If a check doesn't finish in time, the transaction still completes and is marked for review, so a slow check never holds up processing indefinitely.
A confirmed PEP match on a transaction carries a clear PEP hit indicator on that transaction, with a one-click action to start its Politically Exposed Person Transaction Report, the monthly filing the NFIU requires for every confirmed match regardless of amount.
Customer risk classification doesn't stop at a label on a profile. Turn on enhanced monitoring and every customer currently classified High risk automatically gets closer-attention treatment, with no one needing to remember to flag them by hand.
Turn on a single enhanced monitoring profile and, whenever the account holder's current risk classification is High, an outcome that would normally just flag the transaction for review is instead held until an analyst releases it.
High risk customers' transactions are excluded from automated AI clearing, so a human reviewer always makes the final call instead of a transaction clearing itself.
Detection rules can be scoped to apply only to customers at a chosen risk classification, letting you write tighter rules for your highest-risk customers without changing anything for everyone else.
When AI clearance is switched on, the AI can close flagged and held transactions on its own. Sampling and review keep a person checking its work, without adding an alert for every decision.
When AI clearance is switched on, a configurable share of the held and flagged transactions the AI clears is drawn into an AI clearance review queue. Held decisions have their own sampling rate, separate from flagged ones, because a held transaction can move or block money.
A reviewer agrees with a sampled clearance or overrides it. An override always requires a written rationale, records the transaction as escalated, and opens it in the normal human review queue.
Choose how often the AI's clearance decisions are reviewed, see when the next review is due, confirm each review, and keep a review history. A reminder limit tells your team when sampled decisions are waiting.
CTR, FTR, SAR, STR, and PEP Transaction Report filings for Nigeria's financial intelligence regulator (NFIU), plus generation in its exact required file format, now live in a full Reporting module built for the team that owns the filing lifecycle end to end.
Every threshold-exceeding transaction detected here carries through into Reporting for readiness-checked preparation, transaction and party review, and filing in the exact format your regulator requires.
From a transaction's detail page, create a CTR, FTR, STR, SAR, or PEP report in a few clicks, with the transaction already attached to the draft. A confirmed PEP match offers a ready PEP report the same way.
Fill with AI drafts the narrative of the report and, for STR and SAR, the goAML indicators, so analysts start from a complete draft instead of a blank form. Content an analyst has already written is never replaced without confirmation, and nothing is submitted automatically.
Explore a client-controlled deployment for connected transaction records, analyst visibility, and bank-led detection and reporting workflows.
