News & Insights

Transaction monitoring isn't a system a bank installs once and leaves running. It has a shelf life, and 2026 gave banks two clear signals that a lot of existing systems have quietly passed theirs: confidence in whether current monitoring actually works has collapsed, and regulators keep finding gaps in programs that looked compliant on paper. The question isn't whether a bank has transaction monitoring. It's whether the bank actually knows if it's still working.

Most payment providers can already answer "do we have transaction monitoring." Far fewer can answer the question a Dutch regulator asked one of their peers in July 2026: does it actually cover every merchant, and does anyone properly investigate what it flags. That's the moment to rethink transaction monitoring — not when it's missing, but when nobody can confirm it's complete.

Gambling operators have technically been obliged entities under EU AML rules for years, but the EU's new AML Regulation makes that obligation sharper and more specific — including for transaction monitoring. The moment to rethink monitoring isn't when a license is at risk. It's now, while the compliance window the regulation set is still open.

The moment a telecom operator starts moving money — mobile wallets, airtime-linked remittance, mobile money — it inherits the same ongoing monitoring obligations a payment institution carries, whether or not "AML" was ever part of its original compliance function. The trigger isn't a specific fine against a telecom operator. It's the moment mobile money volume makes the operator look, to a regulator, like the payment institution it's actually become.

Key Takeaways: Partnership: Finchecker integrated real-world operator logic from regulated Canadian provider Montowire MSB Ltd (FINTRAC/Bank of Canada registered). Technology: A 4-layer transaction monitoring system designed to cut false positives and evaluate cross-border risk in real time. Outcome: Enterprise-ready compliance with out-of-the-box rule sets, zero calibration delays, and full auditability.

Crypto platforms and fiat on-ramps accept card payments at one of the highest risk points in digital finance. Why is card fraud on a crypto platform exponentially more dangerous than in traditional e-commerce? In e-commerce, a fraudulent shipment can sometimes be stopped or returned. In crypto, a stolen card buys cryptocurrency that is transferred on-chain within minutes. The transaction is irreversible, meaning the platform absorbs 100% of the chargeback loss if the fraud isn't caught at authorization.

iGaming operators process high volumes of deposits from players who demand instant account funding. Why do fraud rings target iGaming? Because stolen cards provide high liquidity. Fraudsters use stolen cards to fund accounts (carded deposits), play minimal rounds, and attempt to withdraw "clean" funds before the cardholder notices. Anti-fraud software must run at deposit velocity, because once a withdrawal clears, lost funds are unrecoverable when a chargeback arrives weeks later.

A bank's card portfolio is the fastest-moving part of its exposure — thousands of debit and credit card authorizations a minute, each requiring an immediate pass/fail decision before settlement. Traditional post-transaction AML batch checks are insufficient at the authorization layer: once a card-not-present (CNP) authorization goes through, the loss or chargeback liability is created. Banks need specialized card anti-fraud software to act as an inline gatekeeper, preventing credit card fraud and debit card fraud before settlement and long before a manual credit card fraud investigation is triggered.

Payment Service Providers (PSPs) and Electronic Money Institutions (EMIs) process transactions for diverse merchant portfolios where conversion speed is critical. Why isn't a standard back-office fraud tool enough? Because for a PSP, card anti-fraud is a core part of the checkout experience. If a PSP's fraud engine is too slow, checkout conversion drops; if it's too lax, credit card fraud and chargeback rates skyrocket—threatening acquiring licenses and scheme standing.

A payment provider's banking partners, card networks, and national regulators all ask a version of the same question during due diligence: what happens after a customer is onboarded and starts moving money. Sanctions screening and KYC answer who the customer is. Transaction monitoring is the only control that answers what they're actually doing — and it's usually the first thing a banking partner's audit checks before deciding whether to keep supporting a PSP or EMI.

A crypto platform's KYC and sanctions screening confirm a user is who they say they are, at the moment they onboard. None of that tells a regulator, a banking partner, or the platform itself what happens to that user's funds afterward — which wallets they touch, whether a clean onboarding turns into a laundering vector six months later. The aml transaction monitoring process is the control built specifically to answer that question, continuously.

Every bank already runs KYC at onboarding and screens new customers against sanctions and PEP lists. Transaction monitoring exists because neither of those checks answers the question that actually causes most AML failures: what does this customer do after the account is open. A clean onboarding file doesn't guarantee clean activity two years later — accounts get compromised, ownership changes quietly, legitimate businesses get used as fronts. The aml transaction monitoring process is the control that keeps watching after the onboarding file is closed.