What was entered
The payment, the batch row, the onboarding request or the name — exactly as it arrived.
Every possible match becomes a case, worked on one screen whatever the channel. You design the road each case follows, and a second person approves every change.
WICS never moves money by itself. It holds, asks, and tells your systems the answer.
C-2041MT103
Wladimir Petrow
What was entered
WLADIMIR PETROW·250,000.00 USD
“Different date of birth and nationality.”
Release proposed
Payments, batch rows, onboarding requests and names land on the same screens. Waiting holds the work to do now. History keeps everything decided, clean screenings included.
Everything an officer needs sits on one page. Everything they do is written down.
The payment, the batch row, the onboarding request or the name — exactly as it arrived.
Each hit lines up the entered words with the list words and highlights what matched.
The full record behind the hit: names, aliases, dates, countries and the list it came from.
Only the decisions your workflow allows at this status, for the people allowed to take them.
A whitelisted good guy stays cleared when the list changes, and is flagged for a second look. Known false positives are suggested, per unit.
Every move, decision and comment, with who did it and when. Nothing is overwritten.
Each bank draws its own workflow: the statuses, the moves between them, the decisions allowed at each status and who may take them. One workflow per module: transaction, batch and name.
Status libraryA code locks once it is used
Changes
S. Haddad will check — the live workflow runs unchanged
Illustrative — invented names and figures.
Every setup change goes to a second person before it counts. The checker sees exactly what changed, and the maker can never approve it.
Edit a workflow, a rule, a channel, a list, a user or a unit.
The button stays off until something actually changed.
Before and after, line by line.
Approved, it goes live. Rejected, it returns to the maker.
Four eyes covers
Blocking a payment has its own permission.
Signed in as
Workflow · Payment cases
Sent by A. Karim · 09:42
AKYou made this change. Someone else must approve it.
WICS reads your sentence offline, with no AI, so nothing leaves the bank. It suggests words as you type, asks about words it does not know, then fills the guided steps for you to check.
Describe the rule in words
Hold payments to FATF grey-list countries above 10,000 USD
Read itExamples
What should this rule do?
Which payments?
Name, check, save
Grey-list payments above 10,000 USD
When a payment goes to a FATF grey-list country and is above 10,000 USD, hold it for review.
Exempt what you choose not to screen. Every exemption is recorded, never hidden.
Route alerts, answer a hit as a false positive signed by the rule, start the case in a given status, set a deadline.
When rules answered every hit, the payment can be released on its own, and the history names the rule.
A rule that errors holds the payment and names itself in the log.
The calling system sends the deadline. WICS warns before it, marks the case overdue after it, and counts only your opening hours.
Kestrel Marine Ltd
MT10312,900.00 USD
Blue Cedar Holdings
pacs.0083,480,000.00 AED
Lumen Pharma SA
MT1037,315.40 CHF
Past the deadline WICS keeps warning. It never releases or cancels a payment on its own.
Business calendar · Head office
Thu 14:00 + 4 opening hours = Fri 10:00
A report centre in every application: screening, lists, users and notifications. Dozens of ready reports, or build your own in numbered steps.
Build your report
1Show as
2Group by
—
3Count or total
Count of cases
4Only show
Last 30 days · decided
5Sort
Newest first
6Columns
5 of 14
Cases decided
TableEvery case decided in the last 30 days, newest first.
Illustrative — invented names and figures.
Table, summary, cross-table, bars, trend line, pie and heat map.
Big data stays fast: totals are counted where the data lives.
Export any report, or send it by e-mail on a schedule.
Cases by status, decision, unit and period — overdue ones too.