CFPB Data: Fintech Reconciliation Failures and How They Resolve

When a consumer files a complaint with the Consumer Financial Protection Bureau, the outcome most likely to end with the company paying money back to the consumer is a reconciliation failure, not a fraud dispute, not an access problem, not a fee disagreement. Reconciliation-related complaints receive CFPB-recorded monetary relief at 9.96%, compared to 3.51% for all other fintech payment complaints in the same dataset. That gap, nearly three times, holds across years and product categories.

This post reports the findings from an analysis of 97,028 CFPB consumer complaints filed against major US consumer fintechs between 2021 and 2025. The classified dataset, validation set, and source query are published for independent audit.

What the data covers

The analysis draws from the CFPB Consumer Complaint Database, filtered to complaints filed between January 2021 and December 2025 against eleven major consumer fintechs: PayPal and Venmo, Block (Cash App), Chime, Wise, Early Warning Services (Zelle), Coinbase, Revolut, Klarna, Affirm, SoFi, and Robinhood. Product scope includes money transfer, digital wallet, prepaid card, checking, and consumer installment loan products. Only complaints with a consumer narrative were included.

Each complaint was classified by a reasoning-capable large language model using chain-of-thought prompting. The classifier was validated against 80 hand-labeled complaints and produced accuracy of 88.75%, precision of 89.19%, and recall of 86.84%. Those metrics reflect a balanced classifier: it neither systematically over-flags nor under-flags.

What counts as a reconciliation failure

Reconciliation is the process of confirming that two or more records of the same money movement agree. A payment processor records a transfer as settled. An internal ledger does not. A refund is logged as sent by a merchant but never posted to the consumer’s account. A charge appears twice and only one is reversed. In each case, two systems hold disagreeing records of the same event.

The classification captures complaints where the consumer describes that kind of mismatch, regardless of how they label it. Most consumers do not use the word reconciliation. They describe a transfer that left their account and never arrived, a duplicate that was not corrected, a balance that does not match what they expected. The classifier tests whether the described sequence is consistent with a recording, matching, settlement, or ledger error, and excludes fraud, account access failures, and service quality disputes.

The monetary relief gap

When the CFPB records a complaint as “closed with monetary relief,” it means the company paid the consumer to resolve the dispute: a refund, fee reversal, or direct restitution. This is the strongest resolution outcome in the CFPB dataset. It reflects a company determining, under regulatory review, that the consumer was owed money. It is not an order from the CFPB; it is a company decision to pay.

Reconciliation-related complaints are nearly three times more likely to end with the company paying the consumer. They are also 6 percentage points less likely to close with explanation only.

The reason is structural. Reconciliation failures involve traceable discrepancies. A duplicate charge can be matched against the original transaction record. A transfer that left one account and never arrived can be traced through provider logs. A refund the merchant can document as sent can be compared against the consumer’s account history. When these disputes reach a regulator, both sides can usually determine where records diverged and whether the consumer is owed money. Fraud and account-access disputes are harder to adjudicate because the central question is authorization, not record agreement. Companies know the difference and resolve accordingly.

Prevalence: roughly one in seven complaints in 2021-2024

Across the full 97,028-complaint dataset, 7,880 complaints describe reconciliation-related failures. That is 8.12% of the total, but that pooled figure is distorted by 2025.

In December 2024, the CFPB filed suit against Early Warning Services and three major US banks over Zelle fraud. That action generated a wave of template complaints in 2025 that were service grievances, not transaction-level errors. Total fintech payment complaints in this dataset jumped approximately sevenfold in 2025, inflating the denominator. The 2025 reconciliation share drops to 5.39% as a result, even as the absolute count of reconciliation-related complaints continued to rise from 1,537 to 3,642.

The 2021 through 2024 period is the cleaner signal.

In those four years, reconciliation-related complaints represented between 12.95% and 15.64% of all fintech payment complaints annually. Pooled across 2021 through 2024, the share is 14.39%, or roughly one in seven. Overall complaint volume roughly doubled over the same period; reconciliation complaints more than doubled, meaning their share was rising, not stable.

Where complaints concentrate

Reconciliation-related complaints concentrate in the platforms with the most complex payment routing across external banks, processors, wallets, and internal ledgers.

These are raw counts, not failure rates. The CFPB data provides no transaction denominator. The concentration in platforms with multi-party payment routing is consistent with the structural conditions that produce reconciliation failures, but it says nothing about which platforms have higher rates relative to transaction volume.

What this means for fintech operations teams

Every complaint in the classified 7,880 is a consumer who escalated to a federal regulator. The larger population is the discrepancies that never reach the CFPB: duplicates that closed without a refund, settlement breaks absorbed as write-offs, transfers that disappeared and were never traced.

The monetary relief gap implies that reconciliation failures are resolvable when someone can trace the transaction across every system it touched. That capability, tracing a payment across processors, banks, wallets, and internal ledgers to the exact point of disagreement, is what separates a dispute that closes with a payment from one that closes with an explanation.

The operational implication is that this is a detection and traceability problem, not a support staffing problem. Adding headcount to handle the escalated complaints does not change the outcome for the discrepancies that never escalate. Catching them earlier requires transaction-level visibility across every system the payment touched.

How Rexi approaches this

Rexi is an agentic reconciliation platform built for fintechs, neobanks, payment companies, and marketplaces that move money across fragmented systems. It ingests transaction data from processors, banks, wallets, ledgers, and ERPs, reconciles across sources, and surfaces discrepancies before they become consumer complaints.

Two capabilities are directly relevant to the failure pattern this data describes. Exception management identifies transactions that fail to match, routes them for investigation, and tracks resolution at the transaction level. Revenue leakage detection catches duplicate charges, settlement breaks, and unrecovered fees before they accumulate. Both depend on transaction-level visibility across every record boundary the payment crosses.

The CFPB data in this analysis measures the cost of those gaps after the fact. Reconciliation software addresses them before the consumer notices.

The full research paper, classified dataset, and CFPB source query are available for independent review at the links below. The classification prompt is available on request.

Data availability: - Classified dataset (97,028 records, narratives removed for privacy) - CFPB source query (reproduces exact 97,028-complaint dataset) - Classification prompt available on request