Industries / Finance and business services / Finance and banking / Payments processing
Fraud and chargebacks
This work stops payments made with stolen card details or by trickery, and settles disputes when a cardholder says a charge is wrong.
5
Milestones achieved, from 1974 to 2025.
2
To watch for: announced, not yet confirmed outside.
2
Open deliverables. Nobody has shipped them.
The road
AchievedWatch forOpen
Achieved
1974
A right to dispute charges
The US Fair Credit Billing Act, Title III of Public Law 93-495 of 28 October 1974, set out to protect consumers "against inaccurate and unfair credit billing and credit card practices". Card issuers must investigate billing errors, which include charges the cardholder did not make and goods never received, if the cardholder writes within 60 days of the first bill that shows the error, and federal law limits a cardholder's liability for unauthorized charges to $50, by the Federal Trade Commission's account. A card payment reversed this way, back through the merchant's bank, is called a chargeback.
Credit
US Congress
1992
Neural networks score card fraud
HNC Software led a group of banks that pooled their card data in 1992 to train Falcon, a fraud scoring system, by Eric Siegel's account in his book The AI Playbook. In October 1993 American Banker reported that AT&T Universal Card Services had signed a long-term agreement to use HNC's system, "based on a neural network", a program that learns patterns from examples. FICO bought HNC ten years after Falcon began, Siegel writes, and Falcon now screens transactions for 2.6 billion cards, drawing on a data consortium of more than 9,000 banks.
Credit
HNC Software and the banks that pooled their data
2006
One standard for card data
American Express, Discover, JCB International, Mastercard and Visa founded the PCI Security Standards Council in 2006. It maintains the Payment Card Industry Data Security Standard (PCI DSS), the security rules for any business that stores, processes or transmits card data. The Council does not enforce them: the card networks and the banks that serve merchants decide who must comply.
Credit
the five card networks
2016
Chip cards push fraud online
As US stores moved to chip cards, the share of in-person card payments by value that were checked by chip rose from 3.2% in 2015 to 26.4% in 2016, by the Federal Reserve's count. Over the same year in-person card fraud fell from $3.68 billion to $2.91 billion, while remote card fraud, on payments made online or by phone, rose from $3.40 billion to $4.57 billion.
LessonClosing one route for fraud moves it to the next weakest one.
Credit
the EMV chip standard of Europay, Mastercard and Visa; measured by the Federal Reserve Payments Study
2025
Strong checks shown to work
EU rules under the second Payment Services Directive (PSD2) require strong customer authentication (SCA) for most electronic payments: proof from two separate factors, such as a phone the payer has and a code or fingerprint, with set exemptions. In December 2025 the European Banking Authority (EBA) and the European Central Bank (ECB) reported that in 2024, card payments inside the European Economic Area (EEA) without SCA had twice the fraud rate of those with it, and that card fraud rates were about 17 times higher when the other party was outside the EEA, where SCA may not be required. Card fraud in the EEA came to €1.3 billion in 2024, 0.033% of card payment value.
Credit
the EBA and ECB, which collect the fraud reports under PSD2
Watch for
Refunds for bank impersonation scams
Negotiators for the European Parliament and the Council agreed the EU Payment Services Regulation on 27 November 2025. Under the deal, a payment provider must refund in full a customer whom a scammer posing as the provider's staff persuaded to approve a payment, if the customer reports it to the police and tells the provider; online platforms that were told about fraudulent content and did not remove it become liable to providers that reimbursed victims; and providers must check that a payee's name matches the account it gives.
Achieved whenThe regulation is formally adopted and in force, and the EBA or national authorities publish refund and fraud figures under it.
Claimed by
European Parliament, November 2025
AI drafts dispute responses
Visa said it processed 106 million card disputes in 2025, up 35% from 2019, and in April 2026 launched dispute tools for banks and merchants. They include Dispute Recovery Manager, which drafts merchants' responses with generative AI and predicts the chance of winning, in pilot with wider rollout planned for late 2026.
Achieved whenAn outside party publishes how often AI-drafted responses win, and how long cases take, compared with responses written by people.
Claimed by
Visa, April 2026, as reported by Fintech News Singapore
Open
01
Test payment-page tamper alarms
A lab test of the tools that watch online checkout pages for skimmers, small scripts that copy card details as a shopper types them. Build a test shop with a sandbox payment form, add skimmer code that security researchers have already published, one sample at a time and in the ways real attacks loaded it, and record whether each monitoring tool raises an alert and how fast. Use only test card numbers, and send anything a skimmer captures to a server inside the lab.
The briefCredit · unclaimed02
One table of fraud rates
An open table of official card fraud statistics by country and year, split where the source allows into in-person and remote payments and into payments with and without strong authentication, keeping the source page and the definition used for every number.
The briefCredit · unclaimed
Open 01 · the brief
Test payment-page tamper alarms
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A lab test of the tools that watch online checkout pages for skimmers, small scripts that copy card details as a shopper types them. Build a test shop with a sandbox payment form, add skimmer code that security researchers have already published, one sample at a time and in the ways real attacks loaded it, and record whether each monitoring tool raises an alert and how fast. Use only test card numbers, and send anything a skimmer captures to a server inside the lab.
Why it is still open
PCI DSS version 4.0 made two rules mandatory from 31 March 2025: a list of every authorized script on a payment page (requirement 6.4.3) and an alarm when a payment page's scripts or headers change without authorization (requirement 11.6.1), as summarized by PageCrawl.io, a page-monitoring firm. Vendors point to reviews of their own product, such as a security assessor's review of Reflectiz's platform described in a partner article in The Hacker News in June 2026, which compares no other tool. Pedro Pereira and colleagues (November 2025) trained models to classify script behaviour on a real-world data set, but did not test the monitoring tools merchants deploy. This research found no public, repeatable test that compares those tools.
Built with what exists
Magento Open Source or WooCommerce with a payment provider's test mode, such as Stripe's sandbox; Playwright to load pages as a shopper's browser would; open-source monitors and free trials of commercial ones; the browser's own script checks, Content Security Policy reports and Subresource Integrity hashes.
First step
Build the test shop, add one documented skimmer, and see whether Content Security Policy reporting alone flags it.
Done looks like
At least 20 published skimmer samples, each loaded three ways (written into the page, hidden in a changed third-party library, and added as a new script), run against at least five monitoring tools, with a public table of which tools alerted and how many minutes each took, and the lab setup released so another team can rerun it.
Open 02 · the brief
One table of fraud rates
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
An open table of official card fraud statistics by country and year, split where the source allows into in-person and remote payments and into payments with and without strong authentication, keeping the source page and the definition used for every number.
Why it is still open
Each authority publishes on its own definitions and periods. The joint EBA-ECB report covers only the EEA, with half-yearly data for 2022 to 2024; the Federal Reserve's fraud study covers the United States and compares 2012, 2015 and 2016. This research found no open table that lines such figures up across countries.
Built with what exists
A web agent to find and download reports, such as Browser Use (see the Note "Deleting 80% to start over"); an AI model that reads tables in PDFs, such as Claude Fable 5.2 (see the Note "Three working devices"); a reviewer that cites the line behind each number (see the Note "Findings that cite notes"); CSV files on GitHub.
First step
Put the EBA-ECB figures for 2022 to 2024 and the Federal Reserve's figures for 2015 and 2016 in one table, and write down where their definitions differ.
Done looks like
Figures for at least 15 countries over at least five years each, with in-person and remote fraud rates wherever published, under an open license; a second person checks 100 random values against the source pages and agrees with at least 98 of them.