The TRAPS Act requires the Secretary of the Treasury to form a Task Force for Recognizing and Averting Payment Scams within 90 days. The Task Force brings together federal regulators, law enforcement, financial institutions, payment networks, community banks, credit unions, consumer representatives, tech industry groups, and victim advocates to study payment‑related scams and propose coordinated responses.
The Task Force must evaluate scam techniques (including spoofing, scam texts, malicious ads, and business email compromise), review international approaches, identify prevention and victim‑support strategies, and recommend legislative or regulatory changes. It must deliver an initial public report to congressional financial committees within one year and then update that report annually; the group terminates three years after the initial report is filed.
At a Glance
What It Does
The bill directs Treasury to establish a cross‑sector Task Force that includes specified federal agencies and appointed private‑sector and victim representatives to study payment scams, craft education and prevention strategies, and recommend policy or enforcement changes. The Task Force must meet at least three times in its first year, produce a public report within one year, and issue annual updates thereafter.
Who It Affects
Federal regulators and law enforcement agencies named in the membership list will be formal participants; banks, credit unions, payment networks, fintechs, and industry associations are expected contributors. Consumer advocates, victim support organizations, and State, local, and Tribal authorities are invited as stakeholders in coordination and reporting efforts.
Why It Matters
By centralizing cross‑agency expertise and private‑sector insight, the Task Force can harmonize reporting, surface best practices for detection and response, and push coordinated recommendations that could shape future rulemaking or legislation—especially around data sharing, industry standards, and business email compromise.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The Act tells Treasury to get a national group up and running within 90 days to tackle payment scams. That group is chaired by the Secretary (or a designee) and includes a fixed set of federal players (CFPB, FCC, FTC, DOJ, OCC, Federal Reserve Board, NCUA, FDIC, FinCEN) plus appointed private‑sector representatives from banks, credit unions, community banks, digital payment networks, tech/online platform associations, consumer groups, and up to five advocates or victim representatives.
Appointments last until the Task Force ends, and vacancies are filled the same way they were made.
The Task Force must meet at least three times during its first year; after that the chair schedules meetings as needed and may use remote conferencing. Its work list is broad: review current scam trends and specific tactics (spoofed calls, scam texts, malicious ads/pop‑ups, fraudulent websites), compare international anti‑scam approaches, catalogue methods used to exploit payment platforms, and develop consumer education strategies to improve recognition and reporting of scams.
The group is also charged with improving the ability of law enforcement to identify and pursue perpetrators and with looking specifically at business email compromise schemes.Practically, the Task Force must consult with State, local, and Tribal agencies and industry providers and may propose additional federal legislation or regulatory changes. It has to publish a public report within one year describing its findings, strategy, and any legislative or regulatory recommendations, including ideas to harmonize data collection, improve reporting channels, estimate affected consumers, and evaluate anti‑scam training.
After the initial report the Task Force issues annual updates. The statute also specifies that chapter 4 of title 5, United States Code, does not apply to the Task Force, compensation rules for federal members, and that the Task Force sunsets three years after it files the initial report.
The Five Things You Need to Know
The Secretary of the Treasury must establish the Task Force within 90 days of enactment.
Membership is explicit: CFPB, FCC, FTC, DOJ, OCC, Federal Reserve Board, NCUA, FDIC, FinCEN, plus appointed private reps from banks, credit unions, payment networks, community banks, consumer groups, tech/online platforms, and up to five victim or support‑network representatives.
The Task Force must submit a public report to Senate Banking and House Financial Services committees within one year and then provide annual updates.
It must meet at least three times in the first year and focus duties on evaluating scam tactics, international practices, consumer education, law‑enforcement coordination, and business email compromise solutions.
The statute exempts the Task Force from chapter 4 of title 5, and the Task Force terminates three years after submitting its initial report.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
This section gives the Act its name: the Taskforce for Recognizing and Averting Payment Scams Act, or TRAPS Act. It’s a naming provision only and has no operational effect beyond labeling the statute for citation.
Key definitions
Section 2 defines central terms that shape the scope of the Task Force’s work: 'payment' is written broadly to mean any electronic mechanism for transferring funds via a platform or intermediary; 'Secretary' refers to the Treasury Secretary; and 'Task Force' is shorthand for the body created later in the bill. The definition of 'payment' frames the group’s remit to cover bank rails, card networks, digital wallets, P2P apps, and similar intermediated transfers.
Establishment and membership
Treasury must create the Task Force within 90 days. Membership is a mix of federal agencies (financial regulators, enforcement, and communications), industry representatives chosen in consultation with the Task Force, consumer and victim voices, and payment network expertise. The statute requires that private‑sector appointees be chosen ‘by the Secretary in consultation with the Task Force,’ which preserves Treasury‑led control over selections while expecting input from other members.
Purpose, meetings, and duties
The Task Force’s stated purpose centers on examining payment scam trends, adopting a cross‑sector approach, and including victim and industry perspectives. It must meet at least three times in its first year and can meet remotely. Its enumerated duties are operational: identify scam methods, study international practices, map how payment platforms are misused, design consumer education strategies, improve coordination for prosecuting perpetrators, consult with subnational authorities, assess the need for federal law changes, and explore solutions for business email compromise.
Compensation, reporting, applicable law, and sunset
Federal members serve without additional pay; they receive only their normal federal employee compensation. The Task Force must provide a public initial report to the Senate Banking Committee and House Financial Services Committee within one year, describing findings, strategies, and legislative or regulatory recommendations, and then update that report annually. The statute states that chapter 4 of title 5 does not apply to the Task Force, and the body terminates three years after filing its initial report, limiting its lifespan unless Congress acts later.
This bill is one of many.
Codify tracks hundreds of bills on Finance across all five countries.
Explore Finance in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Consumers and scam victims — The Task Force’s work on education, reporting harmonization, and victim‑support coordination aims to reduce losses and make recovery and reporting simpler for affected individuals.
- Law enforcement and prosecutors — Improved coordination among federal, State, local, and Tribal authorities and harmonized reporting can make it easier to trace perpetrators and construct investigatory leads across payment rails and jurisdictions.
- Financial institutions and payment networks — The Task Force will surface operational best practices and industry standards that can reduce fraud losses and provide clearer expectations for cooperation with law enforcement.
- Consumer and victim advocacy groups — The statute guarantees direct representation and a platform to influence recommendations, potentially raising the profile of victim needs and remediation practices.
- Regulatory agencies — Participating agencies gain a structured venue to align policy ideas, share intelligence, and develop coordinated legislative or regulatory proposals.
Who Bears the Cost
- Treasury and participating federal agencies — Staff time, data analysis, and interagency coordination impose administrative burdens that the bill does not separately fund.
- Banks, credit unions, and community financial institutions — These organizations are expected to contribute expertise and may face pressure to adopt Task Force‑recommended standards or reporting practices, with attendant compliance costs.
- Digital payment platforms and tech firms — Participation and potential implementation of prevention or reporting measures could require product or process changes, engineering effort, and ongoing operational adjustments.
- State, local, and Tribal agencies — The Act anticipates consultation and coordination with subnational authorities, which may require resource commitments to share data, align reporting, or participate in joint initiatives.
- Privacy and data stewards — Any move toward harmonized data collection and cross‑jurisdictional sharing will require resources to address legal, privacy, and cybersecurity constraints.
Key Issues
The Core Tension
The central dilemma is between speed and coordination on one hand—creating a Treasury‑led, flexible forum that can rapidly collect cross‑sector intelligence and propose concrete measures—and accountability and restraint on the other—avoiding unchecked influence, preserving privacy, and preventing unfunded or burdensome mandates on smaller institutions.
The Act centralizes expertise and creates a formal mechanism for cross‑sector collaboration, but it leaves significant implementation questions unresolved. The statute exempts the Task Force from chapter 4 of title 5, which reduces some procedural constraints but also raises transparency and oversight questions about how appointments, deliberations, and influence will be documented.
The bill does not provide dedicated funding, so agencies and private participants must absorb the time and analytic costs of convening, studying complex payment‑rail data, and drafting recommendations.
Operational challenges could blunt the Task Force’s impact. Harmonizing data collection across banks, fintechs, telecom carriers, and law enforcement is technically and legally difficult; privacy law, varying incident classification systems, and commercial sensitivities limit what can be shared.
The Act requires recommendations on legislative or regulatory changes but leaves the heavy lifting of drafting and enforcing any subsequent rules to Congress or agencies, which may slow or dilute reforms. Finally, appointed private‑sector members and the method of selection create a risk that industry perspectives dominate technical recommendations unless the Task Force actively protects victim and consumer voices.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.