Transaction monitoring settings

Transaction monitoring settings

OneView needs one institution base currency before it can accept transactions. The setting provides a stable reference for foreign-currency classification across transaction history and rule evaluation.

Open Transaction Monitoring → Settings. Viewing the page requires Read transaction settings. Saving the currency requires Manage transaction settings.

Configure the currency

Enter the three-letter ISO 4217 currency code used as the institution's primary operating currency, then select Save currency. For example, a Nigerian institution whose base currency is Naira enters NGN.

The value is permanent after the first save. OneView permits an identical repeat request, but rejects an attempt to replace the configured currency. This protects historical rules and transaction classifications from changing meaning after data has been recorded.

Transaction ingestion returns 409 TRANSACTION_MONITORING_NOT_CONFIGURED until this step is complete.

How OneView uses it

For every accepted transaction, OneView compares the submitted transaction currency with the configured base currency:

• The same currency records isForeignCurrency: false.
• A different currency records isForeignCurrency: true.

OneView does not derive isCrossBorder from this comparison. The source system must submit that required boolean because currency and national-border movement describe different facts.

For non-USD foreign-currency or cross-border transactions, the source system must also submit usdExchangeRate. OneView uses it to calculate the stored USD equivalent. See Submitting transactions for the exact request contract and exchange-rate convention.

Automatic AI investigation

After base currency is configured, the page also shows Automatic AI investigation. Viewing it requires transaction_settings:read; enabling or disabling it requires transaction_settings:manage.

The control can be enabled only when the installed release supports AI investigation, the current license includes the AI Module, and an active default provider/model has passed its connection test. When enabled, new transactions with a FLAG, HOLD, or BLOCK decision are investigated asynchronously and the Markdown result is retained with the transaction. PASS and NOT_EVALUATED decisions do not trigger automatic investigation.

Disabling the control affects future eligible transactions and does not delete existing results. See AI transaction investigations for manual access, evidence minimisation, reuse, retry, and Review card behavior.

Changing a mistaken setting

The dashboard and API do not provide an edit operation after initial configuration. If the wrong currency was saved before production ingestion began, stop transaction submission and contact OneView support. Do not attempt to change the database directly because transaction history and rule evidence must remain internally consistent.