Study guide

Transaction and Payment Screening

CAMS Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: CAMS Orientation and Exam Facts

Current CAMS Exam Format Eligibility Credits and ACAMS Membership Package Pricing and Study Materials Pearson VUE Scheduling Window Passing Score and Result Reporting Exam Non-Disclosure and Practice Ethics

2 Chapter 2: Financial Crime Risks and Methods

AML, CFT, Sanctions, Fraud, ABC, and Tax Evasion Financial Systems and AFC Consequences Predicate Crimes and Financial Crime Exposure Sector, Product, Customer, Jurisdiction, and Channel Risk Banking Products and High-Risk Sectors Politically Exposed Persons and High-Risk Customers

3 Chapter 3: High-Risk Sectors and Structures

MSBs, PSPs, and E-commerce Platforms Insurance Product Risk VASPs, Cryptoassets, and Related Products Gaming, Gambling, and Real Estate Gatekeepers, Trusts, and Company Service Providers Accountants and Other High-Risk Structures

4 Chapter 4: Global AFC Frameworks

FATF Role and Recommendations United Nations Sanctions Regimes Regulators, Law Enforcement, and FIUs Public Sector, Private Sector, and NGO Objectives Cross-Border Cooperation Authority Reports, Trends, and Typologies

5 Chapter 5: Governance Regulations and Information Sharing

Risk-Based Regulatory Expectations Regulatory Examinations and Enforcement Public-Private Partnerships Information Sharing Mechanisms De-Risking and Financial Inclusion RFIs, Tipping Off, and Customer Communication

6 Chapter 6: AFC Compliance Program Design

Effective Program Pillars Three Lines of Defense and MLRO Role Risk Appetite Statement Enterprise Risk Assessment Risk-Based Controls Policies Standards and Procedures

7 Chapter 7: Program Governance and Operating Model

Horizon Scanning and Regulatory Guidance Governance Committees and Terms of Reference AFC Team Structure and Responsibilities Front Office Interaction Supporting Functions and Risk Partners Training, Awareness, and Staff Risk Culture

8 Chapter 8: Customer Lifecycle Controls

Control Tools Across the Customer Lifecycle Data Quality, Integrity, Access, and Taxonomy Customer Experience and Friction Digital Onboarding and Electronic KYC (e-KYC) External Data Sources and Beneficial Ownership Customer Screening and Sanctions Lists

9 Chapter 9: Ongoing Controls and Monitoring

Periodic Refresh and Perpetual KYC Adverse Media Screening Batch Screening and Fuzzy Logic Transaction and Payment Screening Rules-Based Transaction Monitoring Model Risk Management and Tuning

10 Chapter 10: Investigations and Case Support

Investigation Triggers and Case Triage Open Source Tools and Investigator Support Escalation and Suspicious Activity Decisions Documentation and Evidence Quality Law Enforcement and FIU Requests Post-Investigation Feedback Loops

11 Chapter 11: Technology and Emerging AFC Practice

AI and Machine Learning in AFC Controls Blockchain Transaction Screening Automation to Support Investigators Scenario Coverage and Threshold Setting Data Privacy, Cybersecurity, and Other Risk Functions Technology Governance for AFC Tools

12 Chapter 12: Final CAMS Review and Exam Day

Domain-Weighted Study Allocation Simulator Practice Without Actual Exam Claims Pearson VUE Identification and Test Rules Time Management and Guessing Strategy Retake Extension and Appeal Boundaries Recertification and Ongoing Membership

Transaction and Payment Screening

Key Takeaways Explain This Topic AI

Payment/transaction screening inspects in-flight payment messages (e.g., SWIFT MT103/pacs.008) against sanctions lists in real time, before funds move.

Screening targets all parties and free-text fields: originator, beneficiary, ordering/intermediary banks, and payment references.

A true sanctions hit results in blocking or rejecting and timely reporting (OFAC report within 10 business days); it is not a SAR decision.

Stripping or omitting party data to evade screening is itself a serious offense (the basis of major correspondent-banking enforcement actions).

Last updated: June 2026

Transaction and Payment Screening

Transaction (payment) screening is real-time sanctions screening of payment messages in flight , before settlement. It is distinct from transaction monitoring (covered next), which looks at patterns of activity after the fact to detect money laundering. Payment screening answers a single urgent question: does this payment involve a sanctioned party, country, or item, such that it must be stopped before the money moves?

What gets screened

A payment message — a SWIFT MT103 customer credit transfer or its ISO 20022 successor pacs.008 — contains multiple parties and free-text fields, and all of them are screened, not just the named beneficiary:

  • Field / party Why it is screened
  • Originator (ordering customer) May be a sanctioned person sending funds
  • Beneficiary May be a sanctioned recipient
  • Ordering, intermediary, and beneficiary banks A sanctioned financial institution in the chain
  • Country / address fields Comprehensively sanctioned jurisdictions
  • Remittance information / free text Vessel names, dual-use goods, sanctioned-entity references
  • Block versus reject

When a real hit is confirmed, the correct action depends on the sanctions program. Under OFAC, property in which a blocked person has an interest must be frozen (blocked) — the funds are held in a blocked account and cannot be returned to the sender. For payments merely involving a sanctioned jurisdiction without a blocked-person interest, the bank may reject the payment (return it without processing). Confusing block and reject is a classic exam trap: a blocked transaction must be reported to OFAC within 10 business days , and a year-end report of blocked property is due by September 30.

Screening is not a SAR decision

A confirmed sanctions hit triggers a sanctions action (block/reject and OFAC reporting), which is separate from the suspicious-activity reporting regime. The two can both apply, but they are different obligations. On CAMS, do not answer "file a SAR" for a clean sanctions block; the immediate duty is to stop the payment and file the OFAC report.

Sanctions evasion through data stripping

A major enforcement theme is stripping — removing or altering originator/beneficiary information from payment messages so that screening filters do not fire. This practice is the basis of several of the largest correspondent-banking penalties on record. Detecting cover payments (MT202COV) and incomplete originator data is therefore a core control, reinforced by FATF Recommendation 16, the "travel rule," which requires complete originator and beneficiary information to accompany wire transfers.

Worked scenario

A same-day MT103 names a beneficiary that exactly matches an OFAC SDN entry, confirmed by address. The funds have not yet been released. The correct CAMS workflow: hold the payment, confirm the match, block the funds (do not return them to the originator), notify the sanctions/compliance officer, and file the OFAC blocking report within 10 business days. Releasing the payment "because the customer is long-standing" is wrong; so is quietly returning the funds, which would be an unauthorized release of blocked property.

Real-time screening and the cost of false positives

Payment screening must be fast — it sits in the live payment flow, and every alert holds a payment until an analyst clears it. This creates intense pressure to minimize false positives without weakening coverage. The same fuzzy-matching and threshold considerations from batch screening apply, but with an added time dimension: a payment held too long can breach settlement deadlines and harm customers, while a payment released too quickly can violate sanctions.

Institutions therefore staff real-time screening for prompt review and use disambiguation data, whitelists of cleared true non-matches, and tuned thresholds to keep legitimate payments moving while still stopping true hits.

Comprehensive sanctions, 50% rule, and jurisdictions

Screening is not only about named individuals. Comprehensive (country) sanctions prohibit dealings with entire jurisdictions, so country and address fields matter as much as party names. OFAC's 50 Percent Rule extends blocking to any entity owned 50% or more, directly or indirectly, by one or more blocked persons — even if that entity is not itself named on the SDN list. A payment to an unlisted company can therefore still require blocking if its ownership traces back to sanctioned parties, which is why screening must connect to beneficial-ownership data rather than treating list-name matching as sufficient.

Governance and escalation

Like all controls in this chapter, payment screening operates under documented procedures: clear hold-and-investigate steps, defined escalation to the sanctions officer, recordkeeping of every hit and disposition, and independent testing of filter coverage. Confirmed blocks are reported to OFAC within 10 business days, and blocked property is reported annually by September 30.

Common traps

Screening only the beneficiary and missing intermediary banks or free-text references.

Returning (rejecting) funds that should have been frozen (blocked) under OFAC.

Treating a sanctions hit as merely a SAR matter and missing the OFAC reporting deadline.

Forgetting the 50% rule, so a payment to an unlisted but sanctioned-owned entity is released.

Overlooking stripped or incomplete originator data, which is itself a red flag for evasion.