Skip to content
Security & Governance

Control who sees what. Prove who did what.

Licences, profiles, per-list permissions and units decide what each person can see and do. Every sensitive change needs a second person, and every action lands in an audit log with the value before and after.

Illustrative — invented names and figures.

wics.your-bank.internal
WICSUser Management
AK

Profiles & permissions

Activev12
PermissionAnalystSupervisorAuditor
  • ALLOW_SCREEN_NAMEScreen a name
  • ALLOW_SCREEN_MESSAGEScreen a payment
  • ALLOW_MANAGE_SCREENING_RULESWrite screening rules
  • ALLOW_APPROVE_SCREENING_RULESApprove screening rules
  • UNLOCK_CASEUnlock a case
  • VIEW_AUDIT_LOGRead the audit log
SHSupervisor profileS. HaddadSend for approval
Layers of access
4
Licence, profile, list permission and unit
Kinds of change under four eyes
8
Users, profiles, units, workflows, rules, channels, lists, notification rules
Parts in the version vector
7
Stamped on every screening decision
Decision reproducibility
100%
Any past decision can be replayed
Access in four layers

Four layers decide what each person sees.

Each layer can only take away. What is left is exactly what that person may use — and nothing else appears on the screen.

Who is signing in?

wics.your-bank.internal/home
WICSAnalyst
AK

What this person sees

North branch

Everything WICS can do

Screening

  • Transactions
  • Batch files
  • Name screening
  • Onboarding

Lists

  • OFAC SDN
  • EU Consolidated
  • Staff watchlist
  • Private clients

Work

  • Open cases1,284
  • Reports

Administration

  • Users & profiles
  • Audit log
Four eyes

No change goes live on one person’s word.

A change to users, profiles, units, workflows, rules, channels, lists or notification rules waits for a second person. The person who made it cannot approve it.

  • Nobody approves their own change
  • The checker sees exactly what was added or removed
  • A button the server would refuse is not shown
  • “Send for approval” stays off until something really changed

Under four eyes

SHMakerS. Haddad’s screen

New user · J. Okafor

Waiting for approval

No Approve button here. Someone else must approve.

LMCheckerL. Moreau’s screen

New user · J. Okafor

  • +Profile: Analyst · Unit: North branch
RejectApprove
Units

Head office sees everything. Each branch sees its own.

Units split the work by branch or department. Each user works only the cases, channels and batches of their own units.

Head officeMain unit · Sees every unitLMAll units

Open cases

116

Latest case

C-0411· Corporate banking

North branch38
RAMT
  • C-0409MT103
  • C-0405Name
Harbour branch27
JOLC
  • C-0410pacs.008
  • C-0406Batch
Corporate banking51
SKDFPN
  • C-0411MT202 COV
  • C-0407Onboarding
Airport branchNew unit0
Waiting for approval
  • No cases yet

Head office sees all

The main unit sees every unit, including units added later.

Users belong to units

One or more units per user. Supervisors can tick “All units”.

Four eyes on every unit change

A unit with users can be deactivated, never deleted. Your licence sets how many units you can create.

Audit trail

Every action, with the value before and after.

Each application keeps its own audit log, behind its own permission: who did what, when, and what changed. And every screening decision can be replayed exactly.

wics.your-bank.internal
WICSAudit log
AK
This log needs its own permission: VIEW_AUDIT_LOGRecording
  • 10:14:25JOJ. Okafor · Edited a channelCore banking REST · IP allow-list10.20.0.0/16+ 10.30.0.0/16
  • 10:13:38AKA. Karim · Decided a caseC-0412 · StatusLevel 1 reviewReleased
  • 10:12:51LML. Moreau · Approved a rule changeGrey-list countries · StatusWaiting for approvalActive
  • 10:12:04SHS. Haddad · Changed a screening ruleGrey-list countries · Threshold10,000 USD25,000 USD

Decision D-118204

Held · score 0.91
  1. 1Input hashsha256:9f3a…c41e
  2. 2List version2026.09.14-02
  3. 3Engine version4.2.1
  4. 4Profile versionrt-payments@7
  5. 5Config versioncfg-118
  6. 6Rule versionrules-62
  7. 7Model versionfp-reducer@0.9.3
Sign-in & data protection

Strong sign-in. Sealed secrets. Separate data.

Multi-factor sign-in, encrypted secrets, data kept apart per company and API keys you control — on the infrastructure you choose.

Multi-factor sign-in

A code from an authenticator app on top of the password, set up once with a QR code. New users must change their password first.

Authenticator

WICS · a.karim

482 913

New code every 30 s

Set up once with a QR code

Sign in

Authenticator code

  • Password
  • Authenticator code
  • Permissions confirmed by User Management

New users change their password first

Secrets stay secret

Channel passwords and keys are encrypted. Once saved, they are never shown again — you can only replace them.

Channel · Core banking SFTP

Host
sftp.core.internal
User
wics-svc
Password
Save

An API key per channel

Each channel has its own key, with scopes, an IP allow-list and optional HMAC signatures.

Key · Core banking REST

wics_••••3f9a
Scopes
Screen payments
Read results
IP allow-list
10.20.0.0/16
HMAC signature
SHA-256 · Required
  • 10.20.8.3signed, on the allow-listAccepted
  • 10.20.4.17signature does not matchRefused
  • 10.20.4.17signed, on the allow-listAccepted

Each company’s data kept apart

Row-level security in the database separates every company. A query only ever returns its own rows.

One database · one table

Signed in to Company A
CompanyRecord
  • Company AC-0412
  • Company BC-7781
  • Company AC-0413
  • Company BC-7782
  • Company BC-7790
  • Company AC-0419

3 rows hidden by row-level security

Where it runs is your choice

Kubernetes on-prem, cloud SaaS or hybrid. On-prem, nothing leaves the bank.

Your data centre

  • Core & data
  • Screening engine
  • Audit store

Cloud

    Nothing leaves the bank.

    Built for every user

    Each person’s language. Each person’s look.

    The whole application in English, French and Arabic, right-to-left included. Each user keeps their own language, time zone and look.

    Three languages, one screen

    Change the language and the screen follows. Arabic reads right to left. Times show in each user’s own time zone.

    Show the screen in
    WICSCasesAK

    Case C-0412

    Level 1 review
    Party
    Northwind Trading LLC
    Possible match
    OFAC SDN · 0.91
    Deadline
    14:30
    ReleaseBlockEscalate

    Language: English · Time zone: Europe/London

    One deadline, shown in each user’s time zone14:30 London=15:30 Paris=17:30 Dubai

    Design studio

    Each user picks colour style, corners, density, text size, shadows, motion, hover and font. The look is saved to their account.

    Design studio

    Colour style

    Corners

    Density

    Text size

    Shadows

    Font