Fintech & Payment Processors AML Red Flags
Search 427 AML and BSA red flags specifically for fintech & payment processors. Filter by risk level, transaction type, and customer profile, each sourced from a FinCEN advisory, FFIEC manual, or federal regulation. Whether you're preparing for an exam, filing a SAR, or training your team, find exactly the red flags that apply to your regulated business in seconds.
- 1
Pick your industry: Select from 13 regulated sectors like Money Services Businesses, Fintech, Real Estate, or Crypto to instantly filter relevant red flags.
- 2
Narrow by risk or transaction type: Sort by Critical, High, or Medium risk, or filter by wire, cash, ACH, or crypto transactions.
- 3
Save, share, or print: Copy filtered sets for your compliance program, export for SAR documentation, or use Training Mode to quiz your team.
Turn this library into an active study session. Use Training Mode to hide risk levels and test your own classification skills. Or jump into Quiz Mode for flashcard-style review with pass/review tracking, a progress bar, and a readiness score, exactly what you need before exam day.
What AML and BSA red flags are, and how to use them
This library is more than a list. It is a working reference for compliance officers, examiners, and training programs. Before diving into the database, here is how red flags fit into an effective AML program and what they do and do not mean.
What AML and BSA red flags are
A red flag is a transaction pattern, customer behavior, or operational anomaly that may indicate money laundering, terrorist financing, fraud, or sanctions evasion under the Bank Secrecy Act. Red flags are warning signs drawn from FinCEN advisories, FFIEC examination manuals, and federal regulation. They help a compliance team know where to look; they are the beginning of an analysis, not the end of one.
Why red flags vary by industry
Money laundering risk is not the same everywhere. A cash-intensive money services business, a mortgage lender funding a home purchase, a casino handling chips, and a crypto exchange moving virtual assets each face different typologies. That is why this library is organized by industry and why a red flag that is critical for one sector may be irrelevant to another.
A red flag is not proof of suspicious activity
Identifying a red flag does not automatically mean suspicious activity has occurred. Legitimate customers trigger indicators for entirely benign reasons. The framework expects institutions to weigh each indicator against the customer profile, the nature of the business, and the surrounding facts before deciding what it means.
Escalation and investigation
Once an indicator is observed, the next step is investigation, not accusation. Staff compare the activity against the expected profile, gather supporting facts, and route the review through a documented escalation path to the compliance officer. The goal is a clear, consistent, and documented decision about what the activity means.
The importance of documented procedures
A red flag only becomes useful when there is a written procedure for handling it. Documented escalation steps, investigation notes, and decision records show examiners that the institution has a repeatable process, regardless of how any single case turns out. Good documentation is what makes a program defensible.
Connection to SAR decision-making
Red flags feed into Suspicious Activity Report decisions. When the facts meet the applicable threshold and suggest illegal activity, evasion of the BSA, or no apparent lawful purpose, a SAR is filed. When they do not, that decision is documented too. Not every red flag requires a SAR, and treating it as though it does is a common misunderstanding.
Educational versus legal conclusions
The entries in this library are educational and informational. They describe indicators; they do not determine guilt, liability, or compliance. They are not legal advice and do not replace a qualified review of your specific facts, your obligations, and the current text of the regulation. Always confirm against the official source.
Red flags organized by industry
Every entry in the database is tagged by industry. Skip straight to the dedicated guide for your sector, or use the selector below to filter the full library on this page.
Nothing on this hub is legal, regulatory, or compliance advice. Red flags are educational indicators and do not establish that suspicious activity, criminal conduct, or a violation has occurred. Confirm every requirement against the official FinCEN, FFIEC, or federal source and consult a qualified professional for your specific circumstances.
Select your industry to get started
34
of 427 totalMatching Red Flags
Fintech
Currently filteredIndustry
27
FinCEN & FFIECSource Documents
15
Red flag typesCategories
Fintech platform experiences a ransomware attack where customer data is exfiltrated and a cryptocurrency ransom demand is made, with subsequent dark web postings of stolen account information.
Hide risk levels and source documents to test your own classification skills. A proven way to lock in knowledge before your CAMS or BSA exam.
34 of 427 red flags
Synthetic identity created using a real Social Security number combined with fabricated personal information passes initial KYC checks but fails deeper identity verification or credit bureau cross-referencing.
Biometric verification fails liveness detection: the user submits a high-resolution photo or deepfake video instead of a live capture, bypassing facial recognition controls.
Account shows rapid inflows and outflows (velocity) with funds passing through within minutes, showing no legitimate holding pattern consistent with normal payment or savings behavior.
Account is used to purchase virtual currency and immediately transfer it to an external wallet with no prior history of crypto trading, followed by rapid liquidation or mixing service use.
Customer reports unauthorized transactions after their account credentials were compromised, with login attempts from unfamiliar IP addresses, geolocations, or devices not previously associated with the account.
Fintech platform experiences a ransomware attack where customer data is exfiltrated and a cryptocurrency ransom demand is made, with subsequent dark web postings of stolen account information.
Fintech platform processes cross-border payments for customers using virtual currency to circumvent traditional banking channels and avoid sanctions screening in jurisdictions subject to OFAC restrictions.
Multiple prepaid debit cards are loaded with state unemployment insurance benefits using stolen or synthetic identities, then immediately used for ATM withdrawals or P2P transfers to a common recipient.
Customer uses a peer-to-peer payment app to receive funds from multiple users and immediately converts them to virtual currency, sending the crypto to a mixer or privacy coin wallet.
Customer uses a deepfake-generated video call to verify identity for a high-value account opening, with the synthetic persona mimicking a real person whose identity was stolen from social media.
Multiple accounts are opened in rapid succession using the same device, IP address, or phone number, with slight variations in name or date of birth to evade duplicate detection.
Account applicant provides a selfie or document photo that has been manipulated using AI tools, with telltale signs such as unnatural skin texture, inconsistent shadow direction, or missing security features.
Merchant account receives a sudden spike in transaction volume from unrelated cardholders, with chargeback rates far exceeding industry norms, suggesting account takeover or transaction laundering.
Peer-to-peer payment account receives large volumes of small transactions from multiple unrelated users, then consolidates and wires the funds overseas, indicating potential money mule activity.
Payment processor shows merchant settlement funds being directed to personal accounts rather than the merchant’s business account, with no legitimate business reason for the diversion.
Business customer’s API credentials are compromised, leading to unauthorized batch transactions that drain the account within minutes, with no corresponding legitimate business activity.
Customer uses a fintech remittance service to send funds to a sanctioned individual or entity by slightly altering the beneficiary name or using an intermediary in a non-sanctioned country.
Payment platform used by an escort service or massage business shows deposits from clients followed by rapid transfers to a single personal account, with no legitimate payroll or business expense pattern.
Elderly customer’s account shows a sudden change in transaction pattern, with large transfers to new payees who claim to be tech support, IRS agents, or grandchild impersonators.
Business customer onboarding provides corporate registration documents from a jurisdiction known for shell company formation, with no physical office, website, or verifiable employees.
Business customer changes its beneficial ownership information shortly after onboarding, replacing legitimate owners with nominees or individuals with no traceable employment history.
Account is accessed from IP addresses associated with high-risk jurisdictions or Tor exit nodes, with transaction patterns inconsistent with the customer’s stated residence or business location.
Fintech bank account receives direct deposits from multiple state unemployment agencies for the same individual or SSN, with no legitimate basis for multi-state eligibility.
Unemployment benefit prepaid cards are activated and the PIN is changed from an IP address in a different state than the recipient’s listed address, followed by immediate cash withdrawal.
Merchant’s transaction history shows a high proportion of transactions from cardholders in unrelated geographic regions, with no corresponding shipping or digital delivery records.
Neobank account shows round-dollar ACH credits from multiple different employers in a short period, with no corresponding payroll tax withholdings or consistent deposit timing.
Customer contacts customer support to dispute legitimate transactions they previously authorized, then withdraws the dispute after the funds are temporarily credited, suggesting a chargeback fraud scheme.
Merchant customer changes its business description, MCC code, or website content shortly after onboarding to a completely unrelated industry, suggesting transaction laundering or account flipping.
Cross-border payment platform processes invoices for goods with pricing that is inconsistent with commodity exchanges or market benchmarks, with no supporting bills of lading or customs documentation.
Voice authentication system is bypassed using an AI-cloned voice of the account holder, generated from publicly available audio clips, to authorize wire transfers or account changes.
Elderly customer authorizes recurring ACH debits to a previously unknown merchant that sells vitamins, sweepstakes entries, or investment products with no verifiable business registration.
Customer registers with an address in a low-risk country but all transactions originate from a high-risk jurisdiction, suggesting the use of a proxy or VPN to mask true location.
Customer repeatedly attempts to open new accounts after previous accounts were closed for suspicious activity, using slightly modified personal information to evade detection systems.
Business customer’s payment pattern shows funds moving in a circular fashion between related entities in different countries, with no apparent commercial purpose for the transactions.
Showing 34 of 427 red flags
Found a fintech red flag? See what your AML program should do next.
Most fintechs that move money, issue prepaid access, or handle virtual assets are classified as money services businesses, which brings the 31 CFR 1022.210 program expectations, plus sponsor-bank requirements on top.
How every red flag is sourced, cited, and reviewed
This library is meant to be checked, not just read. Each entry shows where it came from and when it was last reviewed, so examiners, compliance officers, and trainers can verify the basis for any indicator.
Every entry cites its source — and its attribution strength
Each red flag is linked to a related FinCEN, FFIEC or regulatory source. The wording is Soflo's summary, not a quotation, so confirm any indicator against the source before relying on it. Reviewed records also carry an attribution tier, so you can see whether the source names the indicator directly or whether it was adapted from that source.
Citations are shown, not summarized away
Where a record maps to a regulation, the 31 CFR citation is displayed with a direct link so you can read the operative text yourself instead of trusting a paraphrase.
Each record carries a last-reviewed date
Records show the date they were last checked against the source document. The library is reviewed periodically against current FinCEN advisories, FFIEC manual updates, and the Code of Federal Regulations.
SAR categories are mapped, not implied
Where applicable, records show the corresponding FinCEN SAR Form 111 checkbox category and key term, so the link between an indicator and a filing decision is explicit.
How we signal the strength of each citation
Not every entry is a literal, named FinCEN indicator \u2014 some are FinCEN indicators applied to a new industry context, and some are generalized training scenarios. Rather than blur those distinctions, each reviewed record is tagged with one of three attribution tiers:
Direct FinCEN indicator
Restates an indicator that the cited FinCEN advisory or guidance itself identifies.
Adapted from FinCEN advisory
Applies an indicator from a FinCEN advisory to this industry’s context rather than quoting it verbatim.
Composite training scenario
A generalized compliance scenario assembled from multiple concepts or standard practice. Useful for training; it is not a single named advisory indicator.
Tagging is being applied sector by sector as each industry\u2019s records are re-checked against their source documents. Insurance and Fintech are classified first; records without a tier are still being reviewed and carry no attribution claim until they are.
Red flags are educational indicators drawn from official sources. They do not establish that suspicious activity, criminal conduct, or a violation has occurred, and this library is not legal or compliance advice.
Browse compliance resourcesEducational & Informational Use Only
This library is a training aid and reference tool. It is not legal, regulatory, or compliance advice. Results are a self-reported estimate, not a formal examination or audit. There is no guarantee of regulatory compliance, and this is not a substitute for an independent BSA audit by a qualified professional. No attorney-client or consulting relationship is established. No warranties are made regarding the accuracy, completeness, or fitness for purpose of the content herein. Always consult a licensed compliance professional for guidance specific to your situation.
Red Flag Reference by Topic
Deep-dive guides for specific red flag categories and industries. Each page includes expanded explanations, regulatory context, and related training resources.
AML Red Flags for Title Companies
30+ BSA red flags specifically for title companies, escrow agents, and closing attorneys. Sourced from FinCEN advisories...
MSB Suspicious Activity Indicators
45+ suspicious activity indicators specifically for money services businesses. Drawn from the FFIEC Exam Manual and rela...
Cryptocurrency Money Laundering Red Flags
40+ red flags for detecting money laundering in cryptocurrency transactions. Drawn from FIN-2019-G001, FIN-2021-A004, an...
SAR Red Flags List
427+ BSA red flags organized by SAR checkbox category. Each red flag includes the SAR checkbox it maps to, its source do...
Structuring Red Flags for Banks
25+ structuring indicators specifically for banks. Sourced from the FFIEC Core Examination Manual, FinCEN advisories, an...
AML Red Flags by Industry
427+ BSA red flags organized by 13 regulated industries. Each entry is sourced from a FinCEN advisory, FFIEC manual, or ...
BSA Red Flags List
427+ Bank Secrecy Act red flags covering every compliance category, industry, and risk level. Each flag cites a FinCEN, ...
Money Laundering Red Flags
427+ money laundering indicators organized by the three stages: placement, layering, and integration. Each flag cites a ...
FinCEN Red Flags for Mortgage Companies
35+ BSA red flags for mortgage companies under 31 CFR § 1029. Drawn from FIN-2012-A009 and FinCEN mortgage fraud reporti...
FinCEN Red Flags for Fintech Companies
35+ BSA red flags for fintech companies under 31 CFR § 1022. Drawn from FIN-2020-A007, the 2024 Financial Trend Analysis...
FinCEN Casino AML Red Flags Examiners Look For
30+ BSA red flags for casinos under 31 CFR § 1021. Adapted from FinCEN casino guidance and advisories, each record shows...
FinCEN Red Flags for Insurance
25+ BSA red flags for insurance under 31 CFR § 1025. Based on FinCEN's insurance rule and related FinCEN advisories, eac...
FinCEN Red Flags for Investment Advisers
25+ red flags for investment firms. Based on FinCEN's investment adviser rule and related guidance, each record shows it...
FinCEN Red Flags for Precious Metals Dealers
20+ BSA red flags for DPMS under 31 CFR § 1027. Based on FinCEN's dealer rule at 31 CFR Part 1027 and related guidance, ...
FinCEN Red Flags for Real Estate
25+ BSA red flags for real estate under the FIN-2017-A003 Real Estate Advisory and GTO Orders. Sourced from 31 CFR § 101...
FinCEN Red Flags for Charities and Nonprofit Organizations
20+ red flags for nonprofits. Drawn from FIN-2014-A005, FinCEN's Hizballah financing alert (FIN-2024-Alert003), and FinC...
FinCEN Red Flags for Auto Dealers
15+ red flags for auto dealers, tied to Form 8300 and OFAC duties. Each flag includes its SAR checkbox and source citati...
Need Help Building Your AML Program?
Soflo Consulting provides end-to-end BSA/AML compliance solutions for regulated businesses across 13 industries. From risk assessments to annual training, we have you covered.