Getting transactions in

  • Apache Fineract

    A built-in transformer reads Fineract business events for savings deposits, withdrawals and transfers, and loan disbursals and repayments, and feeds them into screening. If you run Fineract, there is no export job to write.

  • Event stream

    Systems that already publish transactions to an event stream can send them straight to TXN-Monitor’s inbound topic. Messages are processed at least once, and malformed messages are set aside for inspection instead of blocking the queue.

  • REST API

    Any system can submit a transaction over HTTPS using a dedicated service-account token. The API accepts the transaction, rejects duplicates by reference, and screens it in the background.

    Example request body, with synthetic values
    {
      "reference": "TXN-2026-000184",
      "account_number": "2000000001",
      "amount": "250000.00",
      "currency": "NGN",
      "transaction_type": "NIP",
      "channel": "MOBILE",
      "transaction_date": "2026-11-09T09:41:26+01:00",
      "counterparty_account": "3000000002",
      "counterparty_name": "Example Trading Ltd",
      "counterparty_bank": "000000"
    }

Customer and reference data

  • Customer and KYC sync

    Customer profiles and KYC tiers can be synced, read-only, from your existing customer database, so rules see the same customer your front office does.

  • Sanctions lists

    OFAC and UN sanctions lists are downloaded and refreshed daily. Nigerian watchlists can be maintained locally.

Getting results out

  • Screening events

    Screened transactions, alerts, case events and reporting events are published as separate event streams that your data warehouse or other systems can consume.

  • Notifications

    Alerts can be sent by email, by SMS through Termii, and to Slack.

  • Reports

    STR and CTR drafts are produced as PDF and XML files for review and filing.