Skip to content
Screening

Screen every payment, file, customer and name — with one engine.

Payments in flight, overnight batches, onboarding requests and an analyst’s search all run through the same matching engine, the same list versions and the same audit trail. Clean traffic closes at once; hits wait in a case.

SWIFT MT, ISO 20022 MX and ACH — over REST, SOAP, SFTP, IBM MQ or Kafka.

wics.your-bank.internal/screening/cases/TX-20481
WICSTransaction screening
3AK
Case TX-20481MT103
Level 1 review
Raw messageFIN · MT103
{1:F01XYZBAEADAXXX0000000000}
{2:I103QRSTDEFFXXXXN}{4:
:20:TRF-261013-0042
:23B:CRED
:32A:261013USD250000,00
:50K:/AE070331234567890123456
NORTHWIND TRADING LLC
DUBAI AE
:57A:QRSTDEFFXXX
:59:/DE89370400440532013000
WLADIMIR PETROW
BERLIN DE
:70:INV 7731 MACHINE PARTS
:71A:SHA
:72:/ACC/PAY ON VALUE DATE
-}

What was entered

Header

Reference
TRF-261013-0042
Type
MT103
Amount
250,000.00
Currency
USD
Value date
2026-10-13

Parties

  • 50KOrdering customerNorthwind Trading LLCDubai AE · AE07 0331 …
  • 59BeneficiaryWladimir PetrowBerlin DE · DE89 3704 …
  • 57ABeneficiary bankQRSTDEFFXXXFrankfurt DE

Free text

70INV 7731 MACHINE PARTS
72/ACC/PAY ON VALUE DATE

Possible match · PETROV, Vladimir

on OFAC SDN
0.91

Immediate answer sentHit pending184 ms

Due 14:30· 1 h 58 min left
  1. Received
  2. Read
  3. Screened
  4. Answered
  5. Case

Illustrative — invented names and figures.

p99 latency
<250ms
Real-time screening in the payment path
Records in 4 hours
3M+
Against 5M+ list entities, overnight
Ways in
4
API, folders and SFTP, queues, a screen
Decisions reproducible
100%
The same version vector on every channel

Message types and channels WICS screens

  • MT103
  • MT202
  • MT202 COV
  • pacs.008
  • pacs.009
  • pain.001
  • camt.056
  • ACH
  • REST
  • SOAP 1.1
  • SOAP 1.2
  • WSDL
  • SFTP
  • IBM MQ
  • Kafka
  • GetStatus
  • HMAC
  • NFKC
  • Damerau-Levenshtein
  • TreeSHAP
Four operational channels

One engine, one audit trail, four ways to screen.

Payments, batches, onboarding and investigations share the same matching engine, list versions and decision record. A name gets the same answer wherever it is screened.

p99 < 250 ms

Real-time transaction screening

Screen payments in flight, before funds move, without adding noticeable delay to the payment rail.

  • SWIFT MT103 and MT202, ISO 20022 pacs.008 and pacs.009
  • Card transaction screening in the authorization path
  • p99 under 250 ms, held as a service limit
3M+ · 4 h

High-throughput batch

Re-screen your whole customer and counterparty book overnight, finished before the business day starts.

  • 3M+ records against 5M+ list entities within 4 hours
  • Worker pods scale out on their own at peak
  • The same version vector as real-time decisions
REST · SOAP

Account onboarding & verification

Check new customers against Sanctions, PEP and Adverse Media lists inside your onboarding journey.

  • REST and SOAP for core banking and KYC systems
  • The same engine and audit trail as payment screening
  • Joined to the customer by CIF
Every query logged

Analyst ad-hoc search

Let investigators search every list directly, with each query and result kept as audit evidence.

  • Every screen is a case, with its Request and History
  • Every query and result written to the audit log
  • Explainable scores that show why a name matched
Transaction screening

Four ways in. The same answer from each.

Connect WICS the way your payment systems already talk. One setup serves every way in, so the same payment always gets the same result.

01

API

REST, and SOAP 1.1 and 1.2 with a WSDL. A GetStatus call tells the caller where a payment stands.

RESTSOAP 1.1SOAP 1.2WSDLGetStatus
02

Folders & SFTP

Drop message files in a folder, or exchange them over SFTP in both directions, with the server’s host key pinned.

FolderSFTP inSFTP outHost key
03

Message queues

Read payments from IBM MQ or Kafka and answer on the queue your system listens to.

IBM MQKafka
04

On screen

An officer pastes a message and screens it. Same engine, same case, same audit trail.

MTMXACH

Every channel has its own API keys, with scopes, an IP allow list and an optional HMAC signature.

API keysScopesIP allow listHMAC
Message mapping

Any SWIFT MT, any ISO 20022 MX, and ACH.

WICS reads each party by its role and screens the fields you choose. A field it does not know is kept under Other fields — never lost.

  • pacs, pain and camt messages, and every MT category
  • Many mappings per message type, one active at a time
  • One message field can feed several Master Record fields
  • No active mapping: the whole message is screened
  • Every change approved by a second person
wics.your-bank.internal/screening/configuration/mapping
WICSMessage mapping
AK
ConfigurationsPayments v4 · ActivePayments v3Trade desk
Message fieldMaster Record fields
  • :50K:Ordering customerFull nameAddresses
  • :59:Beneficiary customerFull nameAddresses
  • :57A:Beneficiary bankBIC
  • :70:Remittance informationFull name
  • :72:Sender to receiver informationFull name
  • :20:Sender’s referenceKept, not screened

A field WICS does not know is kept under Other fields.

Illustrative — invented names and figures.

From message to case

One payment, one decision.

WICS forms cases the way your officers think about payments. Each case shows what was entered: the header, each party by role and the free text of fields 70 and 72, with the matched words highlighted and the raw message one click away.

1

One MX message, one case

A pain.001 with 200 salaries is one decision, not 200.

2

A file of MTs is split

Three MT103s in one file become three cases, each with its own answer.

3

Duplicates are recognised

An identical resend gets the same case and answer, marked duplicate. Same reference, new content: a new case, linked to the earlier version.

4

Clean traffic closes at once

A payment with no hit goes straight to History. Only hits wait in a case.

Answers & delivery

Two answers, delivered wherever you need them.

The calling system hears from WICS at once, and again when a person has decided. Any channel in, any channel out.

Payment TRF-261013-0042

Answers on IBM MQ
  1. Immediate acknowledgement

    Hit pending

    09:41:07.184

    Sent as soon as the payment is screened. A clean payment gets “No hit” and closes.

  2. Status update

    Level 2 review

    09:58:40

    Optional: only for the statuses your bank ticks.

  3. Final answer

    Released

    10:12:03

    By A. Karim: “Different person — the date of birth does not match.”

Or rejected, or cancelled — always with who decided and why.

wics.your-bank.internal/screening/configuration/delivery
WICSDelivery
AK
Channels inWICSChannels out

Kafka → SOAPForce-ACKed by L. Haddad · reason kept in the audit log

Delivered 12,844NACK 0
MessageOutTriesAction
TRF-261013-0057SOAP3Force-ACKed · audited
ReasonConfirmed by phone with payments operations

Illustrative — invented names and figures.

NACK tab

When retries run out, the answer waits here. Send it again, or Force ACK with a reason — fully audited.

GetStatus API

Systems that prefer to ask can check where a payment stands, at any time.

Keys per channel

Each channel has its own API keys, scopes and IP allow list, with an optional HMAC signature.

Deadlines & calendars

WICS warns.It never moves money.

Every held payment has a deadline: the calling system’s, or the one a rule sets — the earlier wins. WICS counts it in your business hours.

  • A business calendar per company, with opening hours for each weekday
  • Gulf public holidays built in, confirmed by the bank
  • A warning before the deadline, an overdue mark after it
  • Release, reject or cancel always stays with a person

No deadline ever releases, rejects or cancels a payment.

wics.your-bank.internal/screening/calendars
WICSBusiness calendar
1AK

Head office· Sun–Thu · 08:00–16:00

Confirmed by the bank
0810121416
  • Wed
  • Thu
    Public holiday
  • Fri
    Closed
  • Sat
    Closed
  • Sun
    10:0012:00
Received
Wed 14:00
Rule: hold 4 business hours
Sun 10:00
Caller’s deadline
Sun 12:00
Deadline applied · the earlier wins
Sun 10:00

09:30Warning sent to the Level 1 team

10:00Overdue — the case is marked

Still held. Release, reject or cancel stays with a person.

Illustrative — invented names and figures.

Batch & onboarding

Your whole book, re-screened before the bank opens.

Schedule batch jobs for customer and counterparty files. Each hit row becomes its own case; the clean rows close as one line in History.

  • 3M+ records against 5M+ list entities within 4 hours
  • Scheduled jobs, with worker pods that scale out on their own
  • One case per hit row, one History line for the clean rows
  • Onboarding requests arrive as a channel into a batch, joined to the customer by CIF
wics.your-bank.internal/screening/batch
WICSBatch screening
27AK

Nightly customer re-screen

Every day · 01:00

Finished
Records
3,148,220
List entities
5,210,644
Elapsed
03:12
100%

03:12 of a 4 h window

Worker pods4 / 16

27 hit rows

27 cases

3,148,193 clean rows

1 line in History

Onboarding · todayRESTSOAP
CIF 00418273Amina HaddadNo hit

Illustrative — invented names and figures.

Multi-script matching

Names in any script. Scores you can explain.

Sanctioned parties appear in many alphabets and spellings. WICS brings every name to a comparable form before it scores a single candidate — and TreeSHAP shows what moved each score.

  1. 1

    Unicode NFKC normalisation

    Full-width letters, ligatures and other compatibility forms collapse to one form.

  2. 2

    Script detection

    Each part of a name is classed by script, so the right transliteration applies.

  3. 3

    Transliteration

    Arabic, Cyrillic, CJK and Hebrew names become comparable Latin forms, common variants included.

  4. 4

    Bit-parallel Damerau-Levenshtein

    Edit distance with transpositions, computed bit-parallel for high throughput.

wics.your-bank.internal/screening/cases/ON-7316/explain
WICSWhy this score?
AK

Customer

Wladimir Petrow

1968 · DE

List entry · OFAC SDN

Петров Владимир · PETROV, Vladimir

1968 · RU

TreeSHAP
  • Base value0.27
  • Name similarity · Damerau-Levenshtein+0.38
  • Transliteration agrees · Cyrillic → Latin+0.12
  • Year of birth matches+0.16
  • Country differs−0.04
  • Common given name−0.03
  • Score0.86
Threshold 0.85Above the threshold: a case opens

Illustrative — invented names and figures.

Noise reduction

Fewer false positives. Each one signed.

Your bank decides what is noise. When a rule answers a hit as a false positive, the hit stays on the case — greyed, with the rule’s name on it.

  • A bank noise-word list: legal forms and payment words
  • Rules that discard a hit, signed “Discarded by rule”
  • Small-amount exemptions, written in the rule
  • A good-guy list that survives a list change
wics.your-bank.internal/screening/cases/TX-20517
WICSTransaction screening
1AK
Case TX-20517MT103640.00 USD1 hit waits

Free text · field 70

PAYMENTpayment wordFORINVOICEpayment word7731GOLDENSTARTRADINGLLClegal form

Hits

  • 70GOLDEN STAR SHIPPING CO0.81
    Discarded by rule NR-04Hit in free text, amount under 1,000 USD
  • 50KAL-NUR TRADING0.88
    Good guyWhitelisted 2026-03-12 · kept after today’s list update
  • 59PETROV, Vladimir0.91

    Waits for a person

3 hits · 1 discarded by a rule · 1 good guy · 1 waits for a person

Illustrative — invented names and figures.