Skip to content

Global payments intelligence

Updated Aug 24, 2026 · 23:31 UTC

Now tracking SEC Proposes Crypto Offering Exemptions and Conditional Safe Harbor
Payments intelligence
Regulation & Compliance

Bilt Says Reporting Error Sent Collection Notices to 1,850 Cardholders

Bilt attributed mistaken collection notices sent to about 1,850 cardholders to a third-party reporting error affecting an old beta card program.

About 1,850 Bilt cardholders received mistaken collection notices for balances they did not owe, according to reporting by The Wall Street Journal. Bilt attributed the incident to a reporting error by a third-party collections agency.

The company said the affected accounts came from its original beta card program, which it stopped offering in 2022. That distinction is important: the notices were not described as balances generated by Bilt’s current card program, and the collections agency was not named in the reviewed reports.

Bilt said it discovered the problem on July 31 and offered to work directly with affected customers. The company expected corrections to appear on credit reports within three business days and said it would give each affected customer 2,500 Bilt rewards points, redeemable for up to about $50 on specified purchases, according to a PYMNTS account of the Journal’s reporting.

A data-furnishing failure can outlive the original account

The incident illustrates a control problem that can persist after a product has been discontinued. Closing a card program does not end the need to govern account records passed to collection agencies and credit-reporting channels. Old account identifiers, balance fields and customer status data still require reconciliation, ownership and exception handling.

A mistaken collection notice can force a consumer to spend time disputing a debt and monitoring credit files. The Journal reported that some affected cardholders said their credit scores fell by 50 or 60 points. Those individual claims have not been independently verified, but they show why accuracy and rapid correction matter even when a company describes an incident as a third-party error.

For issuers, fintech program managers and servicing vendors, assigning work to a collections provider does not remove the need for controls over the data leaving the program. Practical safeguards include reconciling balances before a file is furnished, blocking closed or migrated portfolios from routine collection workflows, testing exception files, retaining an auditable record of corrections and confirming that updates reach each relevant credit bureau.

The responsible third party remains unidentified

Bilt’s explanation locates the immediate cause at a third-party collections agency, but the reviewed public accounts do not identify that agency or explain the exact technical or procedural failure. They also do not state how long the inaccurate information was present, which credit bureaus received it, or whether all affected consumers saw a tradeline on a credit report rather than only receiving a notice.

Those gaps matter for accountability. A complete remediation process should establish which system created the inaccurate balance, which party approved or transmitted the file, how the error escaped validation and how corrections were confirmed. Rewards points may compensate customers for inconvenience, but they do not replace correction of inaccurate collection data or reimbursement of any documented financial harm.

A separate 2026 transition drew CFPB scrutiny

The collections incident should also be kept separate from problems reported during Bilt’s transition to a new bank partner earlier in 2026. In June, the Consumer Financial Protection Bureau said it had worked with Bilt over transition-related technical issues and customer concerns. Bilt told the agency it had offered to reimburse potentially affected customers for overdraft, late or insufficient-funds fees, and the CFPB said more than 500 newly identified customers were due reimbursement by June 4.

The CFPB said at that time that Bilt’s documentation appeared to show the transition issues had been resolved, while the agency would continue monitoring redress. The newly reported collection notices concern an older beta portfolio and a different alleged failure. Together, however, the episodes underline the need for end-to-end oversight when customer data and servicing responsibilities cross banks, fintech platforms and outside vendors.