Demo on synthetic data (Kaggle datasets named on each report). No real client data.

WoWyrd

WoWyrd · Rule review

Rule review: technical report, all business lines

Client: Demo client with 3 business lines (synthetic). Business lines: 3. Generated: 2026-11-20 10:02 UTC.

  • Bank transfers: data 2022-09-01 to 2022-09-18 (daily periods), cut-off 2022-09-18, currency USD.
  • SEPA transfers: data 2026-10-01 to 2026-11-29 (daily periods), cut-off 2026-11-29, currency USD.
  • Mobile money: data 2017-01-01 to 2017-01-31 (daily periods), cut-off 2017-01-31, currency USD.

Internal report. Do not share it outside your firm.

Method

Each business line is measured on its own files, with its own cut-off and label delay, exactly as a single run. This page puts the lines side by side and adds a total.

Totals add counts. A share in the total row is computed again from the added counts, never by averaging the lines' shares. All lines use USD, so amounts are added too.

The summary file stays per business line: each line's folder holds its own summary.json, made by the same code with the same suppression as a single run. No combined summary is written.

No transaction may appear in two lines: the run stops if one does, so no count is added twice.

Totals per business line

MeasureBank transfersSEPA transfersMobile moneyTotal
Transactions58,33159,16154,510172,002
Alerts (transactions with at least one hit)53,48342,31054,425150,218
Alerts not yet mature (newer than the label delay)1435,5232,6748,340
Alerts on declined payments (no outcome; left out of precision)2,1297702,206
Confirmed fraud (label known by the cut-off)9672,0786,1539,198
Confirmed fraud with at least one hit9281,5706,1268,624
Evaluable fraud (mature, not declined)9482,0636,1539,164
False alarms50,30235,15545,625131,082
Declined payments with no fraud or disputed label (friction)2,1106202,172
False-alarm cost (estimate)249,889.60 USD168,992.00 USD219,000.00 USD637,881.60 USD
Share of fraud with a rule hit96.0%75.6%99.6%93.8%

Rules across business lines

Each cell: hits / precision in that line. A dash: the rule did not fire in that line. The total precision comes from the added caught and false-alarm counts.

RuleBank transfers: hits / precisionSEPA transfers: hits / precisionMobile money: hits / precisionTotal hitsTotal caughtTotal false alarmsTotal precision
Money from 5+ different senders into one account within 5 days (fan-in) tp_ffiec_fan_in_5_senders_5d
Finds one account that collects money from many people, as a collection or mule account does.
1,588 / 6.4%27,376 / 1.2%28,140 / 2.4%57,1041,05752,6932.0%
Large payment on an account less than 30 days old tp_ffiec_new_account_large_30d
Finds big money movement on a newly opened account.
—119 / 99.0%—11995199.0%
Many small payments in, then sent out within a day tp_ffiec_small_in_rapid_out_24h
Finds an account that collects several small payments and passes most of the money on at once.
15,845 / 0.5%738 / 2.9%—16,5838414,4080.6%
Money sent to 5+ different recipients within 5 days (fan-out) tp_u21_fan_out_5_benef_5d
Finds one sender spreading money to many receivers in a short time.
41,258 / 0.5%4,461 / 4.0%—45,71936242,6000.8%
Spending in the last 3 days doubles the monthly norm tp_u21_hist_deviation_3d_31d
Finds a sender whose recent outgoing volume jumps far above their own usual level.
—8,984 / 5.9%—8,9843695,8575.9%
Single payment above 9,000 USD tp_u21_large_txn_9k
Flags any one large payment for a closer look.
12,042 / 3.5%2,106 / 8.4%52,667 / 11.9%66,8156,45155,35910.4%
Money in, then almost all of it sent on within 3 days (layering) tp_u21_layering_10k_90pct_3d
Finds an account that receives a large sum and quickly passes nearly all of it to other people.
15,502 / 0.9%699 / 2.1%—16,20113113,9210.9%
10+ mid-size payments in 5 days, over 20,000 USD in total tp_u21_stats_10tx_1k3k_5d
Finds a burst of many similar mid-size payments that add up to a large total.
1,771 / 1.9%1,227 / 0.5%—2,998362,6721.3%
20+ small payments in 5 days, over 20,000 USD in total tp_u21_stats_20tx_0_1k_5d
Finds many small payments that together move a large sum.
349 / 0.6%——34923220.6%
Repeated payments just under 10,000 USD (structuring) tp_u21_structuring_9k_10k_5d
Finds payments kept just below a reporting limit to avoid a report.
554 / 2.3%109 / 7.1%—663133793.3%
Transfer above 500 USD tp_u21_transfer_over_500
Flags every transfer over a low fixed amount, so analysts see most mid-size transfers.
36,685 / 2.4%19,455 / 7.7%54,367 / 11.8%110,5078,27294,9128.0%
More than 2 wire transfers in 7 days tp_u21_wire_count_gt2_7d
Finds a sender who uses wire transfers unusually often.
653 / 0.0%——65305280.0%
Wire transfers above 4,999 USD in total within 7 days tp_u21_wire_total_gt4999_7d
Finds a sender who moves a large total by wire in one week.
505 / 0.0%——50503680.0%

Proposals per business line

Bank transfers

25 proposals. Evidence, effect and caveats: this line's technical report.

SEPA transfers

26 proposals. Evidence, effect and caveats: this line's technical report.

Mobile money

25 proposals. Evidence, effect and caveats: this line's technical report.

What changed since the previous report

Coverage by fraud type

Fraud types present in your labels

Fraud types present in your labelsAccount takeover: 535 caught, 163 missed; Purchase scam: 210 caught, 329 missed; Safe-account scam: 330 caught, 1 missed; Investment scam: 285 caught, 14 missed; Invoice redirection: 210 caught, 0 missed; Spread, then collect: 97 caught, 1 missed; Layers of accounts: 83 caught, 3 missed; Collect, then spread: 83 caught, 1 missed; One out to many (fan-out): 83 caught, 0 missed; Many into one (fan-in): 52 caught, 2 missed; Two groups paying each other: 47 caught, 2 missed; Money in a circle: 43 caught, 1 missed; Random hops: 40 caught, 1 missed; Money mule: 0 caught, 1 missed; Type not given: 6,526 caught, 55 missedAccount takeoverAccount takeoverAccount takeover: 535 caughtAccount takeover: 163 missed535 caught, 163 missedPurchase scamPurchase scamPurchase scam: 210 caughtPurchase scam: 329 missed210 caught, 329 missedSafe-account scamSafe-account scamSafe-account scam: 330 caughtSafe-account scam: 1 missed330 caught, 1 missedInvestment scamInvestment scamInvestment scam: 285 caughtInvestment scam: 14 missed285 caught, 14 missedInvoice redirectionInvoice redirectionInvoice redirection: 210 caught210 caught, 0 missedSpread, then collectSpread, then collectSpread, then collect: 97 caughtSpread, then collect: 1 missed97 caught, 1 missedLayers of accountsLayers of accountsLayers of accounts: 83 caughtLayers of accounts: 3 missed83 caught, 3 missedCollect, then spreadCollect, then spreadCollect, then spread: 83 caughtCollect, then spread: 1 missed83 caught, 1 missedOne out to many (fan-out)One out to many (fan-out)One out to many (fan-out): 83 caught83 caught, 0 missedMany into one (fan-in)Many into one (fan-in)Many into one (fan-in): 52 caughtMany into one (fan-in): 2 missed52 caught, 2 missedTwo groups paying each otherTwo groups paying each otherTwo groups paying each other: 47 caughtTwo groups paying each other: 2 missed47 caught, 2 missedMoney in a circleMoney in a circleMoney in a circle: 43 caughtMoney in a circle: 1 missed43 caught, 1 missedRandom hopsRandom hopsRandom hops: 40 caughtRandom hops: 1 missed40 caught, 1 missedMoney muleMoney muleMoney mule: 1 missed0 caught, 1 missedType not givenType not givenType not given: 6,526 caughtType not given: 55 missed6,526 caught, 55 missed
Labelled fraud cases per type. Blue: a rule fired on the payment. Orange: no rule fired. Source: labels file and rule-hit log, labels known by the cut-off.
Fraud typeLabelled casesCaughtMissedLibrary types it matchesYour rules' coverageWoWyrd
Account takeover698535163noneSEPA transfers: CoveredWoWyrd rule: planned
Purchase scam539210329noneSEPA transfers: Partly coveredWoWyrd rule: planned
Safe-account scam3313301noneSEPA transfers: CoveredWoWyrd rule: planned
Investment scam29928514noneSEPA transfers: CoveredWoWyrd rule: planned
Invoice redirection2102100noneSEPA transfers: CoveredWoWyrd rule: planned
Spread, then collect98971Money comes in and leaves fast, little balance stays (UA-NBU-S06), Most of an incoming amount leaves again within hours (OR-02)Covered (every line)WoWyrd rule available: Money leaves soon after it arrives rapid_pass_through
Layers of accounts86833noneBank transfers: CoveredWoWyrd rule: planned
Collect, then spread84831Money comes in and leaves fast, little balance stays (UA-NBU-S06), Most of an incoming amount leaves again within hours (OR-02), Many small credits, then one large debit (OR-13)Covered (every line)WoWyrd rule available: Money leaves soon after it arrives rapid_pass_through; Many small credits, then one large payout many_small_credits_then_large_payout
One out to many (fan-out)83830One payer sends to far more payees than similar payers (UA-NBU-S15), One account pays many new beneficiaries (OR-07)Covered (every line)WoWyrd rule available: One account pays many different payees account_many_payees
Many into one (fan-in)54522Many payers send to one payee, far more than for similar payees (UA-NBU-S16), Many different senders pay one account within a short time (OR-01)Covered (every line)WoWyrd rule available: Many senders pay one account inbound_sender_fan_in; One payee shared by several customers beneficiary_reuse
Two groups paying each other49472noneBank transfers: CoveredWoWyrd rule: planned
Money in a circle44431Money goes round in a circle between accounts within days (OR-11)Bank transfers: Covered; SEPA transfers: Not covered; Mobile money: Not coveredWoWyrd rule: planned
Random hops41401noneBank transfers: CoveredWoWyrd rule: planned
Money mule101noneSEPA transfers: Not coveredWoWyrd rule: planned
Type not given6,5816,52655noneUnknownWoWyrd rule: planned

Not in this dataset, so it cannot be measured here

Your labels hold no case of these types, so this data cannot show whether your rules catch them. This is not a gap in your rules. The rules column lists catalogue rules whose names match the type.

Library typeIDYour rules whose names matchSourcesWoWyrd
One user holds many more accounts or cards than similar usersUA-NBU-S01noneUA-NBU-S01WoWyrd rule: planned
One type of operation makes up an unusual share of a user's activityUA-NBU-S02noneUA-NBU-S02WoWyrd rule available: One type of operation dominates an account operation_type_concentration
Many operations of one type in a short time, incoming or outgoingUA-NBU-S03tp_ffiec_fan_in_5_senders_5dUA-NBU-S03WoWyrd rule available: Many requests from one account in an hour, then a payout payout_velocity_1h; A burst of operations of one type same_operation_type_burst
Balance stays low although large amounts pass throughUA-NBU-S04tp_ffiec_small_in_rapid_out_24hUA-NBU-S04WoWyrd rule available: Large amounts pass through an account that keeps a low balance low_balance_high_turnover
Large loans are taken and repaid again and againUA-NBU-S05noneUA-NBU-S05WoWyrd rule available: Large loans taken and repaid again and again loan_issue_repayment_churn
Gambling winnings arrive with no deposits, then card transfers followUA-NBU-S07noneUA-NBU-S07WoWyrd rule available: Gambling winnings with no gambling deposits gambling_winnings_without_deposits
Regular transfers to a personal account look like business activityUA-NBU-S08noneUA-NBU-S08WoWyrd rule available: A personal account paid by many payers personal_account_business_activity
A new merchant's volume is far above similar merchants, then the merchant closesUA-NBU-S09noneUA-NBU-S09WoWyrd rule available: A merchant with little history suddenly busy low_history_merchant_spike
Merchant account inflows mirror its outflows (transit)UA-NBU-S10noneUA-NBU-S10WoWyrd rule available: A business account pays out almost all it receives business_account_transit
Payment purposes do not fit the merchant's category codeUA-NBU-S11noneUA-NBU-S11WoWyrd rule available: Payment purpose does not fit the merchant's business payment_purpose_atypical_for_mcc; Card payment to a person without category or purpose acquiring_to_person_missing_data
Contacts, device, apps, IMEI, operating system or network address change oftenUA-NBU-S12noneUA-NBU-S12WoWyrd rule available: Payout right after an email or phone change contact_change_to_payout; One session from several network addresses session_multiple_ips; One account used from many devices account_many_devices
One device fingerprint is used by unrelated usersUA-NBU-S13noneUA-NBU-S13WoWyrd rule available: One device used by several customers multi_account_device
Two operations are too far apart to travel between in the timeUA-NBU-S14noneUA-NBU-S14WoWyrd rule available: Locations too far apart for the time between them impossible_travel
A new account gets large or many credits soon after openingOR-03tp_ffiec_new_account_large_30dUNIT21, UK-FINANCEWoWyrd rule available: A new account receives a large credit new_account_large_incoming_credit; A new account paid by several people new_account_inbound_fan_in
A dormant account suddenly moves large amountsOR-04tp_u21_dormant_100d_5kFFIEC-APPFWoWyrd rule: planned
Repeated amounts just under a reporting or limit thresholdOR-05tp_u21_stats_10tx_1k3k_5d, tp_u21_stats_20tx_0_1k_5d, tp_u21_structuring_9k_10k_5dFFIEC-APPFWoWyrd rule available: Payments just under a limit just_below_threshold_payment; Many small payments from one account add up to a large sum amount_structuring_account; Many small payments to one payee add up to a large sum amount_structuring_beneficiary
Repeated round amounts with no business reasonOR-06tp_ffiec_round_amountsFFIEC-APPFWoWyrd rule available: Several payments in large round amounts repeated_round_amounts
Outgoing payments per hour above the customer's usual levelOR-08tp_u21_hist_deviation_3d_31dUNIT21, EBA-GL-2021-02WoWyrd rule available: More payments in an hour than the customer usually makes high_customer_velocity_1h; Many requests from one account in an hour, then a payout payout_velocity_1h
A large first payment to a payee never paid beforeOR-09noneUK-FINANCE, UK-PSRWoWyrd rule available: A large payment to a payee added just before new_payee_high_amount
Many senders' accounts share one beneficiaryOR-10noneWOWYRD-SPIKE, FINCENWoWyrd rule available: One payee shared by several customers beneficiary_reuse
An amount far above the customer's own historyOR-12tp_u21_hist_deviation_3d_31dEBA-GL-2021-02, NBU-DRAFTWoWyrd rule available: A payment far above the customer's usual amount amount_far_above_customer_average
Credits from many different banks into one accountOR-14noneFIU-UA, FINCENWoWyrd rule available: Credits from many different banks into one account inbound_from_many_banks
Transfers to or from high-risk jurisdictionsOR-15noneFATF-REF, FFIEC-APPFWoWyrd rule available: A payment to or from a high-risk country high_risk_jurisdiction_counterparty
Cash withdrawn right after a credit arrivesOR-16tp_u21_hist_deviation_3d_31dFINCEN, FIU-UAWoWyrd rule available: Cash taken out soon after money arrives cash_withdrawal_after_credit
The payee name does not match and the payment still goesOR-17noneUK-PSR, EU-PSRWoWyrd rule available: Paid although the payee name did not match payee_name_mismatch_paid
The payment reference mentions investment, crypto or a 'safe account'OR-18noneUK-FINANCEWoWyrd rule available: The payment reference uses common scam wording payment_reference_scam_wording
An older customer suddenly sends a large amount to a new payeeOR-19noneFINCENWoWyrd rule available: An older customer sends a large amount to a new payee older_customer_new_payee_large
Activity at hours unusual for the customerOR-20noneNBU-DRAFTWoWyrd rule available: Activity at an hour unusual for the customer unusual_hour_for_customer

Incoming payments and money-mule signs

Each business line is measured on its own files; each line's own report has the detail.

Business lineIncoming credits in your rule logA rule fired on themAccounts with a money-mule signA rule fired on them
Bank transfersIncoming payments not measured: your transactions file has no direction column (for example direction, with values such as in and out).———
SEPA transfers91.3%0.0%70
Mobile moneyIncoming payments not measured: your transactions file has no direction column (for example direction, with values such as in and out).———

New accounts and onboarding rating

Each business line is measured on its own files; each line's own report has the detail.

Business linePayments from accounts 30 days old or youngerAlerts per 1,000 of those payments
SEPA transfers41.9%717.8

Requirements changed since the last review

Your rules are mapped to current requirements. We flag when a new requirement affects them. We follow official publications of regulators in Ukraine, the EU, the UK and the US.

Not legal advice. This report maps your rules to requirements, in our own short wording. It is not legal advice. You decide how you comply.

Requirements library read on 2026-11-11. No change file was given for this run, so no changed requirement is listed here.

Regulatory checks by regulator

Not legal advice. This report maps your rules to requirements, in our own short wording. It is not legal advice. You decide how you comply.

Regulatory statuses as of 2026-11-11 (library date). Check them again before you rely on this report.

Grouped by regulator. Our own short wording, not the regulator's text. Each line is checked on its own files; its own technical report gives the finding and the evidence.

Checks per NBU requirements

Rows citing the NBU draft of 17.07.2026 — draft, not in force: its text can change before adoption. Resolutions 51, 54 and 116 are in force. Bill 16013 is a Ukrainian bill, shown here with its status.

Requirement IDOur wordingResult: Bank transfersResult: SEPA transfersResult: Mobile moneySource statusAs ofOfficial source
UA-NBU51-01The acquirer passes payee (merchant) name and category code to the issuer. Check that these fields are filled in your data. Most time-relevant item: the deadline is about 20.11.2026.Not measurable from these filesNot measurable from these filesNot measurable from these filesin force since 20.05.2026; 6 months to comply (about 20.11.2026)2026-11-11bank.gov.ua
UA-NBU-01Review every rule at least monthly by back-testing it. (NBU draft §66; library item UA-NBU-01.)GapPartly metGapdraft (NBU draft resolution on control of payment operations, published 2026-07-17; not law)2026-11-11bank.gov.ua
UA-NBU-02Metric 1: compare how often each rule fired with how many payments were actually stopped. (NBU draft §60(1); library item UA-NBU-02.)Partly metPartly metGapdraft (NBU draft resolution on control of payment operations, published 2026-07-17; not law)2026-11-11bank.gov.ua
UA-NBU-03Metric 2: share of fraud value that was prevented, out of all fraud value. (NBU draft §60(2); library item UA-NBU-03.)Partly metPartly metGapdraft (NBU draft resolution on control of payment operations, published 2026-07-17; not law)2026-11-11bank.gov.ua
UA-NBU-04Set rule-effectiveness thresholds in writing. A rule under its threshold gets an immediate review. (NBU draft §62; library item UA-NBU-04.)GapGapGapdraft (NBU draft resolution on control of payment operations, published 2026-07-17; not law)2026-11-11bank.gov.ua
UA-NBU-05Record a review decision for every rule: keep, adjust or cancel. (NBU draft §68–69; library item UA-NBU-05.)Partly metPartly metPartly metdraft (NBU draft resolution on control of payment operations, published 2026-07-17; not law)2026-11-11bank.gov.ua
UA-NBU-11Have evidence ready for a supervisor: documents, rules, risk markers.Partly metPartly metPartly metdraft (NBU draft resolution on control of payment operations, published 2026-07-17; not law)2026-11-11bank.gov.ua
UA-NBU51-02Show the acquirer's full name before an online payment; receipts show payee, commission, purpose and category code.Not measurable from these filesNot measurable from these filesNot measurable from these filesin force since 20.05.2026; 6 months to comply (about 20.11.2026)2026-11-11bank.gov.ua
UA-NBU-09Reconcile payment operations every day.Partly metPartly metPartly metdraft (NBU draft resolution on control of payment operations, published 2026-07-17; not law)2026-11-11bank.gov.ua
UA-NBU51-03Acquiring for natural persons only for allowed categories, with the required data passed to the issuer.Not measurable from these filesNot measurable from these filesNot measurable from these filesin force since 20.05.2026; 6 months to comply (about 20.11.2026)2026-11-11bank.gov.ua
UA-NBU54-01Non-bank providers that acquire payments need an authorisation; the sanctions pause has ended.Not measurable from these filesNot measurable from these filesNot measurable from these filesin force; grace period ended 02.09.20262026-11-11bank.gov.ua
UA-NBU116-01Remote verification of natural persons uses the updated procedure with credit-bureau data.Not measurable from these filesNot measurable from these filesNot measurable from these filesin force since 10.10.2026; 3 months to align internal procedures (about 10.01.2027)2026-11-11bank.gov.ua
UA-NBU116-02Reports to the State Financial Monitoring Service go only through the e-cabinet, with numbered registers.Not measurable from these filesNot measurable from these filesNot measurable from these filesin force since 10.10.2026; 3 months to align internal procedures (about 10.01.2027)2026-11-11bank.gov.ua
UA-16013-01Passing cards, account access or payment data to fraudsters becomes a crime. Detect and restrict accounts used as drops.Not measurable from these filesNot measurable from these filesNot measurable from these filesadopted by the Rada 28.10.2026; presidential signature not confirmed2026-11-11itd.rada.gov.ua

Checks per EU requirements

Requirement IDOur wordingResult: Bank transfersResult: SEPA transfersResult: Mobile moneySource statusAs ofOfficial source
EU-PSR-05When a payee name check fails because of the payee's provider, that provider compensates the payer's provider. Keep evidence of the name check on received transfers.Not measurable from these filesNot measurable from these filesNot measurable from these filesagreed, not adopted (EU Payment Services Regulation; adoption expected by 12.2026)2026-11-11oeil.europarl.europa.eu

Checks per UK requirements

Requirement IDOur wordingResult: Bank transfersResult: SEPA transfersResult: Mobile moneySource statusAs ofOfficial source
UK-PSR-03A claim may carry an excess of up to 100 GBP, never for vulnerable customers.Not measurable from these filesNot measurable from these filesNot measurable from these filesin force2026-11-11psr.org.uk
UK-FCA-02Test and review rules; a poorly calibrated rule set the firm cannot explain is poor practice.Partly metPartly metPartly metguidance in force2026-11-11fca.org.uk

Checks per US requirements (FinCEN, NYDFS, FFIEC, Nacha, Federal Reserve)

FinCEN and Nacha items are not checked from your files in this run; the rows below are NYDFS and FFIEC items.

Requirement IDOur wordingResult: Bank transfersResult: SEPA transfersResult: Mobile moneySource statusAs ofOfficial source
US-NYDFS-01Analyse scenarios, rules and thresholds on an ongoing basis.Partly metPartly metPartly metin force2026-11-11dfs.ny.gov
US-NYDFS-02Test rules before and after they go live.Not measurable from these filesNot measurable from these filesNot measurable from these filesin force2026-11-11dfs.ny.gov
US-FFIEC-01Tune and validate monitoring; justify each threshold.Partly metPartly metPartly metguidance2026-11-11bsaaml.ffiec.gov

Run record per business line

Bank transfers

ItemValueSource
Input file: catalogue1ba1a64a09faa99994d49f08f3234ed3049002776677a9c0bf586127f873e484SHA-256
Input file: costs30f762bad066b62dfcb20d236f03995ea3edf0f809c04e934cdb957f3f4de2c4SHA-256
Input file: decisions4f93135d000b15749c574990d5b6d621308ff9be94c4d041d7554e31c022430cSHA-256
Input file: labels5300406887cc1c2d31e72f5a5ae5e77ff197767e26a261670539900ccf30716cSHA-256
Input file: transactions85182da32f2e942304c498041a2eb2ba71989d5c6bc63d6f8737aa49b780d121SHA-256
Collector versionv0.7.0-11-gba7bd7b03d5199dd42d1810a9e4294cde08c03a4git commit
Generation time2026-11-20 10:02 UTCrun time
cutoff2022-09-18T09:55:00+00:00client
label delay days7client
min cell10default
min join coverage0.95default
perioddayclient
thresholdnot givennot given
tokens for all rulesFalsedefault
Regulatory library2026-11-11statuses as of this date
Requirement change filenot given--changes
Tool mapnot given--tools or a tool column in the catalogue
Ledger exportnot given--ledger
Reference set sourcebuilt into this collector
Reference set versionv0.7.0published 2026-11-18
Reference set filee96e792983d3748de554ba3b49a15291c8d4110f1778795555caff0fa81ee119SHA-256

SEPA transfers

ItemValueSource
Input file: cataloguedf35f17dbf43833a1e61c25563e57f6acfacb60e533a103387a697a45eb8fc6dSHA-256
Input file: costs30f762bad066b62dfcb20d236f03995ea3edf0f809c04e934cdb957f3f4de2c4SHA-256
Input file: decisions0a3afffefaf56d8f501b025a1204e7bda8c43b7d82eda43a80f1afc92aa0bf98SHA-256
Input file: labels475a9301c1d99a63ac8076294c853809ac047bd7608793b3266de4e160ee5db7SHA-256
Input file: transactionseab82d5e97005ba696f800b5e3b30089593c4a590d3502f82e1a31d8caf88261SHA-256
Collector versionv0.7.0-11-gba7bd7b03d5199dd42d1810a9e4294cde08c03a4git commit
Generation time2026-11-20 10:02 UTCrun time
cutoff2026-11-29T23:11:10+00:00client
label delay days7client
min cell10default
min join coverage0.95default
perioddayclient
thresholdnot givennot given
tokens for all rulesFalsedefault
Regulatory library2026-11-11statuses as of this date
Requirement change filenot given--changes
Tool mapnot given--tools or a tool column in the catalogue
Ledger exportnot given--ledger
Reference set sourcebuilt into this collector
Reference set versionv0.7.0published 2026-11-18
Reference set filee96e792983d3748de554ba3b49a15291c8d4110f1778795555caff0fa81ee119SHA-256
Onboarding: account-opened columnaccount_created_attransactions file
Onboarding: band columnonboarding_risktransactions file
Onboarding: band order givenlow, medium, high--onboarding-bands

Mobile money

ItemValueSource
Input file: cataloguedf35f17dbf43833a1e61c25563e57f6acfacb60e533a103387a697a45eb8fc6dSHA-256
Input file: costs30f762bad066b62dfcb20d236f03995ea3edf0f809c04e934cdb957f3f4de2c4SHA-256
Input file: decisions478c1fcd2e5ea2286bace3a124f343280535660a6500a73c55df28b939000e5dSHA-256
Input file: labels9f116294ba8270bf7c932b4f31c59778e80e5e72f9e5d55cea96ce809553a35dSHA-256
Input file: transactions74b28df3ad96d7092c8b1d3293d38d9881d3bbfca834fc0c02575a66a7414ebcSHA-256
Collector versionv0.7.0-11-gba7bd7b03d5199dd42d1810a9e4294cde08c03a4git commit
Generation time2026-11-20 10:02 UTCrun time
cutoff2017-01-31T23:00:00+00:00client
label delay days7client
min cell10default
min join coverage0.95default
perioddayclient
thresholdnot givennot given
tokens for all rulesFalsedefault
Regulatory library2026-11-11statuses as of this date
Requirement change filenot given--changes
Tool mapnot given--tools or a tool column in the catalogue
Ledger exportnot given--ledger
Reference set sourcebuilt into this collector
Reference set versionv0.7.0published 2026-11-18
Reference set filee96e792983d3748de554ba3b49a15291c8d4110f1778795555caff0fa81ee119SHA-256

Rule glossary

Each rule in this review, in plain words: what it detects, the fraud type it guards against, when it fires, where it comes from, and the data it needs.

10+ mid-size payments in 5 days, over 20,000 USD in total Rule ID: tp_u21_stats_10tx_1k3k_5d

What it detects
Finds a burst of many similar mid-size payments that add up to a large total.
Fraud type it guards against
Money laundering (many similar payments); structuring
When it fires
10 or more payments in 5 days, each 1,000 to 3,000 USD on average, more than 20,000 USD in total.
Source
Unit21 open rule library
Data fields it needs
ts, sender_id, receiver_id, amount

20+ small payments in 5 days, over 20,000 USD in total Rule ID: tp_u21_stats_20tx_0_1k_5d

What it detects
Finds many small payments that together move a large sum.
Fraud type it guards against
Money laundering (smurfing); structuring
When it fires
20 or more payments in 5 days, up to 1,000 USD each on average, more than 20,000 USD in total.
Source
Unit21 open rule library
Data fields it needs
ts, sender_id, receiver_id, amount

Dormant account suddenly moves more than 5,000 USD Rule ID: tp_u21_dormant_100d_5k

What it detects
Finds an account that was quiet for months and then starts moving money, as when a taken-over or sold account is put to use.
Fraud type it guards against
Account takeover; mule account
When it fires
No activity for more than 100 days, then more than 5,000 USD in or out within 5 days.
Source
Unit21 open rule library; the source gives no exact numbers, so WoWyrd chose some of them
Data fields it needs
ts, sender_id, receiver_id, amount

Large payment on an account less than 30 days old Rule ID: tp_ffiec_new_account_large_30d

What it detects
Finds big money movement on a newly opened account.
Fraud type it guards against
New-account fraud; mule account
When it fires
A payment of at least 10,000 USD where the sender or receiver account is 30 days old or less.
Source
FFIEC BSA/AML Examination Manual, Appendix F red flag; the source gives no exact numbers, so WoWyrd chose some of them
Data fields it needs
amount, account_age_days

Many small payments in, then sent out within a day Rule ID: tp_ffiec_small_in_rapid_out_24h

What it detects
Finds an account that collects several small payments and passes most of the money on at once.
Fraud type it guards against
Mule account; money laundering (pass-through)
When it fires
3 or more incoming payments under 3,000 USD within 24 hours, then at least 80% of their total goes out within the same 24 hours.
Source
FFIEC BSA/AML Examination Manual, Appendix F red flag; the source gives no exact numbers, so WoWyrd chose some of them
Data fields it needs
ts, sender_id, receiver_id, amount

Money from 5+ different senders into one account within 5 days (fan-in) Rule ID: tp_ffiec_fan_in_5_senders_5d

What it detects
Finds one account that collects money from many people, as a collection or mule account does.
Fraud type it guards against
Mule account; scam proceeds collection
When it fires
One receiver gets money from 5 or more different senders within 5 days.
Source
FFIEC BSA/AML Examination Manual, Appendix F red flag; the source gives no exact numbers, so WoWyrd chose some of them
Data fields it needs
ts, sender_id, receiver_id

Money in, then almost all of it sent on within 3 days (layering) Rule ID: tp_u21_layering_10k_90pct_3d

What it detects
Finds an account that receives a large sum and quickly passes nearly all of it to other people.
Fraud type it guards against
Money laundering (layering); mule account
When it fires
At least 10,000 USD comes in, and at least 90% of it goes out to other receivers within 3 days.
Source
Unit21 open rule library
Data fields it needs
ts, sender_id, receiver_id, amount

Money sent to 5+ different recipients within 5 days (fan-out) Rule ID: tp_u21_fan_out_5_benef_5d

What it detects
Finds one sender spreading money to many receivers in a short time.
Fraud type it guards against
Money laundering (dispersal); mule network
When it fires
One sender pays 5 or more different receivers within 5 days.
Source
Unit21 open rule library
Data fields it needs
ts, sender_id, receiver_id

More than 2 wire transfers in 7 days Rule ID: tp_u21_wire_count_gt2_7d

What it detects
Finds a sender who uses wire transfers unusually often.
Fraud type it guards against
Money laundering through wires
When it fires
One sender makes more than 2 wire transfers within 7 days.
Source
Unit21 open rule library
Data fields it needs
ts, sender_id, channel

Repeated large round-number transfers Rule ID: tp_ffiec_round_amounts

What it detects
Finds a sender who keeps sending large, round amounts (a common money-laundering sign).
Fraud type it guards against
Money laundering; payments with no real purchase behind them
When it fires
One sender makes 3 or more transfers of at least 1,000 USD in whole hundreds within 30 days.
Source
FFIEC BSA/AML Examination Manual, Appendix F red flag; the source gives no exact numbers, so WoWyrd chose some of them
Data fields it needs
ts, sender_id, receiver_id, amount

Repeated payments just under 10,000 USD (structuring) Rule ID: tp_u21_structuring_9k_10k_5d

What it detects
Finds payments kept just below a reporting limit to avoid a report.
Fraud type it guards against
Structuring (avoiding the reporting threshold)
When it fires
One sender makes 2 or more payments between 9,000 and 10,000 USD within 5 days.
Source
Unit21 open rule library; the source gives no exact numbers, so WoWyrd chose some of them
Data fields it needs
ts, sender_id, receiver_id, amount

Single payment above 9,000 USD Rule ID: tp_u21_large_txn_9k

What it detects
Flags any one large payment for a closer look.
Fraud type it guards against
Large-value money laundering
When it fires
One payment is more than 9,000 USD.
Source
Unit21 open rule library
Data fields it needs
amount

Spending in the last 3 days doubles the monthly norm Rule ID: tp_u21_hist_deviation_3d_31d

What it detects
Finds a sender whose recent outgoing volume jumps far above their own usual level.
Fraud type it guards against
Account takeover; sudden cash-out
When it fires
The daily average sent over the last 3 days is more than twice the daily average over the last 31 days.
Source
Unit21 open rule library; the source gives no exact numbers, so WoWyrd chose some of them
Data fields it needs
ts, sender_id, receiver_id, amount

Transfer above 500 USD Rule ID: tp_u21_transfer_over_500

What it detects
Flags every transfer over a low fixed amount, so analysts see most mid-size transfers.
Fraud type it guards against
General transfer monitoring (no specific fraud type)
When it fires
One transfer is more than 500 USD.
Source
Unit21 open rule library
Data fields it needs
amount

Wire transfers above 4,999 USD in total within 7 days Rule ID: tp_u21_wire_total_gt4999_7d

What it detects
Finds a sender who moves a large total by wire in one week.
Fraud type it guards against
Money laundering through wires
When it fires
One sender's wire transfers add up to more than 4,999 USD within 7 days.
Source
Unit21 open rule library
Data fields it needs
ts, sender_id, amount, channel

Fraud types in plain words

Each fraud type named in your labels, in one sentence. The word in small grey text is the label as your file gives it.

Account takeover ATO
A criminal gets into a customer's account and sends money out of it.
Collect, then spread GATHER-SCATTER
Money from many accounts is collected in one, then sent on to many others.
Investment scam INVEST
The customer is talked into paying into an investment that does not exist.
Invoice redirection INVOICE
A false or changed invoice makes the customer pay a criminal instead of the real supplier.
Layers of accounts STACK
Money passes through several layers of accounts in a row, so its origin is hard to trace.
Many into one (fan-in) FAN-IN
Many accounts send money into one account, which collects it.
Money in a circle CYCLE
Money passes along a chain of accounts and comes back to the account it left.
Money mule MULE
An account receives stolen money and passes it on for someone else.
One out to many (fan-out) FAN-OUT
One account sends money out to many accounts, so it spreads thin.
Purchase scam PURCHASE
The customer pays for goods or services that never arrive.
Random hops RANDOM
Money hops between accounts along an irregular path with no fixed shape.
Safe-account scam SAFE
A caller who poses as the bank tells the customer to move money to an account the caller controls.
Spread, then collect SCATTER-GATHER
Money is split across many accounts, then collected again in one account.
Two groups paying each other BIPARTITE
One group of accounts pays a second group, with many payments crossing between them.
Type not given no type
Fraud labels in your file that do not say which kind of fraud it was.