Skip to content
Banks, SACCOs and microfinance

Fraud controls your risk committee can sign off.

Sieve checks every payment before it is released. It keeps the evidence your examiner will ask for.

Deployment

Your data lives where you decide.

Every option runs the same product. Choose by where your data must live and who runs it.

SIEVE-MANAGEDTENANTYOUTENANTLIVE · TEST
01

Sieve Cloud

Multi-tenant and fully managed. The fastest way to go live.

  • Tenants logically isolated; live and test kept apart
  • We run upgrades and list updates
  • Suits fintechs and smaller institutions
YOUR NETWORKCOREYOUR REGIONPRIVATEDBKEYS
02

Dedicated cloud

Single-tenant, in the region you choose, Kenya included.

  • Your own database and encryption keys
  • Data residency in line with the Data Protection Act
  • Private link to your network
YOUR DATA CENTRE OR CLOUD ACCOUNTSIEVECONTAINERSPOSTGRESQLAI FEATURES · OPTIONAL
03

Private deployment

In your data centre or your own cloud account.

  • Containers on standard PostgreSQL
  • No customer data leaves your environment
  • AI features optional, enabled separately
Governance

Model risk questions, answered.

What audit and compliance will ask, and where to find each answer.

Audit log · hash-chainedsample entries
rule.updatedprev 61c8864f
hash 00000000
case.closedprev 00000000
hash 9e3779b1
decision.labelledprev 9e3779b1
hash 3c6ef362

Every decision, rule change and verdict is chained together. If anyone alters an entry, the chain shows it.

01

Can we explain any decision?

Each decision stores the rules and patterns that fired, a plain-language reason and the exact response sent.

Evidence Activity · decision detail
02

Can we reproduce it?

Each decision records its ruleset version. Same inputs, same verdict.

Evidence Decision record
03

How are changes controlled?

Each rule is Off, Watch or Enforce. Test changes on the last 30 days; each one is logged with its author.

Evidence Rules · Audit log
04

What does the AI decide?

Nothing. It summarises and suggests, and any pattern it proposes can only start in Watch mode. People close cases, confirm matches and change rules.

Evidence Agent run log
05

How do we know rules work?

Analyst verdicts give each rule a hit rate and precision. Sieve suggests tuning, with evidence, and flags unusual surges.

Evidence Rules · Learn from verdicts
06

Who can do what?

Owner, admin, analyst and viewer roles, with two-factor sign-in. Viewers see personal data masked, and sanctions matches need a second reviewer.

Evidence Settings · Team
Integration

Sits beside your core, not inside it.

Your payment switch or channel systems call Sieve before money moves. Your core banking system does not change.

Where Sieve sitsreference architecture
  1. ChannelsWhere customers actMobile & internet banking · USSD · agency · cards · M-Pesa & Airtel Money
  2. Your systemsChannel back-end, payment switch or ESBCalls Sieve before a payment is released
  3. SieveSynchronous decision APIJSON · idempotency keys · ISO 20022-aligned fields
  4. VerdictReturned in the same callAllowReviewBlock
Core banking No change requiredSigned webhooks Blocks, cases and sanctions matches → case tools, SIEM, email, Slack
01

Synchronous decision API

One call per payment, safe to retry. If Sieve is down, you set each channel to fail open or closed.

02

ISO 20022-aligned data model

Fields map straight from the pacs.008 and pacs.002 messages you already use.

03

Every channel

Mobile and internet banking, USSD, agency, cards, M-Pesa, Airtel Money, bank transfers and crypto withdrawals.

04

Out to your systems

Signed webhooks feed your SIEM and case tools. Alerts also go to email and Slack.

Procurement

Due diligence without the six-month wait.

What we provide for your vendor review.

  • Security questionnaire answered
  • Vendor risk assessment supported
  • Data protection impact assessment supported
  • Data processing agreement in every contract
  • Agreed service levels in every contract
  • Documented exit: all your data in open formats

From briefing to enforcement

Technical briefing

Architecture, controls and data protection, with your fraud, risk and IT teams.

Sandbox replay

See what Sieve would have caught in a sample of your past events.

Four-week pilot

Live traffic in alert-only mode. Nothing is blocked.

Staged enforcement

Rules move from alerting to blocking in stages.

Book a demo

Fraud, risk and IT, one briefing.

One hour, with a live demo on sample data.