Romance Scam Prevention Act: A Compliance Burden or a Trust Opportunity?

The US Senate has closed a lucrative loophole in online romance fraud enforcement. Dating platforms will soon be required to alert users when their matches get banned for scamming, even after the conversation has migrated to WhatsApp or Telegram. The legislation targets the precise moment where platform accountability ends and user vulnerability accelerates.

The Romance Scam Prevention Act cleared the Senate by unanimous consent on 23rd September and now awaits President Trump's signature. It follows months of congressional pressure on Match Group, including a September letter from Senators Marsha Blackburn and Maggie Hassan demanding transparency on fraud metrics, algorithmic recommendations, and whether the company profits from scam-adjacent engagement.

Closing the off-platform gap

The core vulnerability isn't that scammers exist on dating platforms. Trust and safety teams spend tens of millions annually trying to contain them. The gap is what happens when a conversation migrates to Telegram or WhatsApp, often within the first few exchanges. Once off-platform, the dating app loses visibility, the user loses protection of on-platform reporting tools, and the scammer gains operational freedom.

According to Federal Trade Commission data, romance scams cost Americans $1.14 billion in reported losses during 2024 alone, with median individual losses of $4,000. A meaningful proportion of those conversations began on dating platforms and moved elsewhere before the fraud occurred. Until this bill, there was no mechanism requiring platforms to reach back out to users whose matches had been flagged and banned after the fact, even when those users were demonstrably still at risk.

The 24-hour notification window is the operational teeth here. Scammers move fast. A week-old notification is useless. A same-day alert whilst the conversation is still active might actually interrupt the fraud cycle.

The typical cadence is message, build rapport, request a platform switch, then escalate to a financial ask within days. Timing matters. The legislation's 24-hour requirement directly targets this operational rhythm.

Technical implementation and false positive risk

Platforms have one year to comply, which raises immediate questions about what systems need to be built. Most dating apps don't currently retain granular message histories post-ban, particularly for users who've gone dormant or deleted conversations. Operators will need to track which users received messages from an account prior to its ban, retain contact details for users who may have unmatched or left the platform entirely, and build automated notification pipelines that trigger within 24 hours of a ban decision.

That's technically straightforward for platforms with modern data infrastructure. For smaller operators running legacy systems, it's a compliance cost and a timeline problem. The larger issue is definitional.

The bill hinges on 'suspected fraud', which means platforms are making pre-adjudication determinations: no court is involved, no appeals process is mandated. Trust and safety teams already grapple with false positives: legitimate users flagged by automated systems for behaviour that pattern-matches scam tactics. The legislation offers no clarity on what standard of evidence justifies a ban, nor what recourse wrongly banned users have.

Platforms might tighten ban thresholds to avoid notification obligations, letting borderline accounts linger. Or they might lower the bar and increase bans, accepting higher false positive rates as the cost of regulatory compliance.

Enforcement without teeth

The Federal Trade Commission gets enforcement authority, with state attorneys general able to bring actions as well. But the bill treats violations as breaches of the FTC Act generally, rather than specifying penalty amounts or creating a distinct enforcement regime. That's a weaker deterrent than it could be.

FTC Act violations carry civil penalties, but they're case-by-case and often settle for amounts that large platforms can absorb as a compliance cost. Compare that to the EU's Digital Services Act, which allows fines of up to 6% of global turnover for systemic failures. The Romance Scam Prevention Act has no such leverage.

For Match Group, which disclosed $3.65 billion in revenue for 2024, even a multimillion-dollar FTC settlement would be a rounding error. The reputational risk and the congressional scrutiny matter more than the financial exposure: at least until the first enforcement action sets a penalty precedent. Smaller operators face a different calculus. Compliance infrastructure has a fixed cost.

What happens next

The bill now sits with President Trump, who is expected to sign it. Passage was bipartisan and unopposed: romance fraud is one of the few technology policy issues with zero constituency defending the status quo. Once enacted, the one-year implementation window begins.

Expect Match Group to announce compliance early, potentially positioning notification transparency as a trust and safety differentiator ahead of the deadline. Bumble and Grindr will follow similar timelines. Smaller platforms, particularly white-label operators and international apps serving US users, face a compliance scramble.

The broader implication is that this won't be the last prescriptive federal requirement aimed at dating platforms. Blackburn and Hassan's letter to Rascoff wasn't just about this bill: it was a shot across the bow on algorithmic transparency and revenue models that might benefit from fraud-adjacent engagement. Congress is watching. The question for operators is whether they wait for the next mandate or start building beyond compliance now.