Rules
Regulation E for a missing fintech charge: who gets the notice
Regulation E for a missing fintech charge: find the issuing bank behind the app, send it a dated written notice, and know what the 60-day window does.
What to take away
- Regulation E, at 12 CFR Part 1005, is the federal rule that covers debit card and prepaid card errors, including most fintech card accounts.
- The card issuer, not the app, is normally the regulated party. The app is often only a program manager.
- Ask for the issuer's name in writing, then send the notice to the issuer as well as to the app.
- You must tell the institution within 60 days of the statement showing the problem. That notice starts the clock.
- Your first written notice, and the date you sent it, is the record that matters later.
Find the regulated party before you write
Regulation E implements the Electronic Fund Transfer Act. The Consumer Financial Protection Bureau writes the rule, and the official text sits at Regulation E, 12 CFR Part 1005. The legal duty sits with the institution that issued the account.
Who Regulates What
Entity
- CFPB
- Writes Regulation E
- Federal Reserve
- Keeps parallel index
- Neobank app
- Front end only
- Chartered bank
- Issues card, legal duty
Role
- CFPB
- Federal Reserve
- Neobank app
- Chartered bank
The rule reaches banks, savings associations, credit unions and most nonbank providers of electronic fund transfer services, including prepaid accounts. A neobank is usually a front end; the deposit account and the card are issued by a chartered bank behind it.
This split matters when a charge goes missing. You may be talking to an app's support chat while the legal duty sits with the issuing bank, so ask for the name of the issuer in writing.
| Party | Role in a missing-charge case | What to send or ask |
|---|---|---|
| Issuing bank | Carries the legal duty | A written notice with the charge details |
| Neobank or app | Usually the front end, often the program manager | The issuer's name, in writing |
| CFPB | Writes the rule and takes complaints | A complaint if the answer does not come |
What the written notice carries
A notice has to identify the transaction. A compliant notice typically includes the account name, the date and dollar amount of the charge, the merchant descriptor, and a short statement of why the charge is wrong. Keep it factual: unauthorized, duplicated, wrong amount, or goods never received.
- Account name and last four digits of the card
- Date, amount and merchant descriptor of the charge
- One sentence on what is wrong
- The date you send the notice and how you sent it
The record you keep decides a later dispute. Save a copy of the notice, the send date and any confirmation number.
Screenshots of the app's transaction detail screen help, because descriptors on fintech cards are often cryptic, and reading the card transaction record explains what each line shows. If the problem is a repeat charge, separating a duplicate authorization from a posted charge comes first.
The clock, step by step
A compliant error resolution disclosure tells you how to report an error, the deadline, what happens after you report, and how the outcome is communicated. The timeline runs in this order:
- The institution sends the statement or document that first shows the problem.
- Your notice reaches the institution within 60 days of that date.
- If you gave notice by phone, confirm it in writing, because an institution may require written confirmation within 10 business days of an oral notice.
- The institution generally has 10 business days to investigate and must provisionally credit you while it works, with a possible 45 calendar day extension in narrow cases.
- The institution tells you the outcome.
The official procedures sit in the CFPB's text of Regulation E's error procedures, which also says that an institution may require written confirmation of an error within 10 business days of an oral notice. Where it requires that, it has to tell you the address.
What a missed window changes
Miss the 60 day notice window and your protections narrow sharply. The institution may still investigate as a courtesy, but it is no longer bound by the Regulation E error resolution timeline.
You can lose the right to provisional credit and the right to a defined answer within 10 business days. A second consequence is quieter. If you report by phone and never confirm in writing, you may have no proof the clock started. Institutions are required to investigate oral notice too, but proving the date is easier with a written record.
To see how a disputed card charge moves through authorization, clearing and settlement before it reaches this stage, read the card payment guide.
Where the issuer's charter changes the route
Federal Regulation E sets a floor, and states may add consumer protections on top. Some states impose their own timelines or require additional disclosures for prepaid products.
State money transmitter licensing also applies to many fintech operators, which is a separate regime from the card rules. You can check whether an operator holds such a license with this money transmitter license lookup.
If your account is at a state-chartered bank, the state regulator and the federal regulator may both take complaints. If it is at a national bank, the Office of the Comptroller of the Currency handles the bank side while the CFPB handles the rule itself.
Example: naming the issuer on day three
A written notice on day three gives every later step an anchor. A user finds a $38.40 charge from an unfamiliar descriptor on a fintech debit card.
They report it in the app chat on day three, then send an email the same day with the date, amount and descriptor. On day nine, no provisional credit has appeared. They send a second email citing Regulation E's 10 business day limit and ask for the investigation status. The credit posts on day eleven with a written explanation.
Without that notice, the day nine follow up would have had nothing to cite. For how app balances and deposit insurance differ from a bank account, read the guide to digital accounts at banks and nonbanks.
