Observed 9 September 2026. The operative instrument is the [16 January 2025 consent order](http[local research file] administrative proceeding 2025-CFPB-0001, against Block, Inc., defined to include successors and assigns. It explicitly reaches account-restriction appeals as well as transaction-error investigation. It supplies a legally required process and a regulator-monitoring route; it does not establish that any particular appeal succeeded, that all customers actually received timely service, or that Lantern caused the investigated conduct.
Instrument, consent and currentness
Order ¶¶1–3, PDF 2–10, establish jurisdiction, effective date on administrative-docket entry and definitions. ¶4, PDF 11, identifies Block as a Delaware corporation operating Cash App. The stipulation.
The retained [official case page](http[local research file] displays “Post Order/Post Judgment”; its last-modified date is 24 January 2025. The retained [official docket](http[local research file] likewise displays post-order status and lists only document 001 (order) and 002 (stipulation), both filed 16 January 2025; last modified 16 January 2025. Two targeted official-domain searches for this docket/order with termination and 2026 amendment terms did not reveal a later CFPB instrument. This is a scoped public-record observation, not certification that no written modification exists. Order ¶¶154–155 permit written changes to non-material requirements for good cause, including extensions/reporting changes. ¶159, PDF 73–74, sets termination at the later of five years from effective date or the relevant qualifying enforcement-action extension, subject to written amendment, suspension, waiver or termination. The initial five-year date is 16 January 2030; the packet does not assert an unchanged end date.
The [official 16 January 2025 notice](http[local research file] is now expressly marked archived, with an outdated-content warning and last-modified date 25 June 2026. That modification stamp is not a new order date. Use the operative order for exact hours, remedies and exceptions.
What the Bureau found
The order describes failures across several historical periods, not one uniform period applicable to every finding. ¶¶7–18, PDF 12–16: no live telephone customer support until February 2021, misleading contact representations, scams exploiting fake support numbers, and slow/form responses. ¶¶24–27, PDF 18–19: automatic “need more information,” “pushback” and bulk “inquiry” communications delayed or prematurely closed error cases and shifted work back to consumers. These are described templates/macros; the instrument does not establish a generative-AI system or join these practices to Lantern.
The most direct account-access findings are ¶¶34–36, PDF 21. CFPB found missing restriction notifications, generic terms-of-service explanations, failure proactively to publicize the appeal process introduced around 2021, slow reconsideration, weeks to unfreeze even successful appeals, and consumers unaware that withdrawal might be available. ¶¶55–58, PDF 26–28, explain the regulator's unfairness finding: consumers' dependence on reaching the company made loss of access difficult to avoid. This establishes a historically identified failure of recourse, rather than proof that closure always confiscates funds.
Transaction-error findings are separate: ¶¶19–33,39–48 and72–105, PDF 16–25,32–40, describe deficient investigations, denied/delayed provisional credits and refunds, missing explanations/document-access notices, misapplied reporting windows, and wrongful substitution of linked-bank chargebacks. The rule-and-order analysis does not depend solely on Cash App's help wording or contract discretion.
Who must do what
All locators below refer to the order; PDF and printed page numbers agree.
| Decision or duty | Actor and operative requirement | Exact scope / limit |
|---|---|---|
| Reachable customer service | Block must maintain service able to intake and appropriately resolve or escalate complaints, error notices, account-access issues and fraud reports, including noncustomers; publish access instructions. ¶108(a)–(b), PDF 44–45. | Service available 24 hours/day; human voice at least 12 hours/day; human chat at least 18 hours/day. Do not turn the notice's shorthand into 24 hours of human telephone support. |
| Restriction notice | Within 24 hours of freezing, suspending, locking, closing or otherwise restricting an account, provide written explanation of the decision and appeal procedure. ¶108(c), PDF 45–46. | Exception is expressly “unless prohibited from doing so by law enforcement.” Except when funds are frozen, also say whether and how funds can be transferred out, if possible. The frozen-funds exception belongs to the transfer-information limb; do not silently extend it to every notice duty. |
| Account appeal | Establish/maintain an appeal or change-status procedure, clearly publish instructions on the support primary webpage and in-app; grant or deny within 10 business days from receiving the request, with written explanation if denied. ¶108(d), PDF 46–47. | This is an account-restriction requirement, not merely a transaction-error rule. It does not guarantee reinstatement or establish an independent external adjudicator for each appeal. |
| Transaction-error decision and evidence | Prompt, thorough, reasonable investigation; report results within 3 business days of completion; explain no-error/different-error findings, notify the right to relied-on documents and promptly supply copies on request. Correct found errors within 1 business day; provisionally credit within 10 business days if investigation incomplete. ¶108(e), PDF 47. | Applies to a defined Notice of Error, ¶3(f), PDF 9–10. Do not transfer this express document-access right wholesale to every account-closure appeal. |
| Stop obstructing error investigation | No unnecessary-information delaying communications, required police/merchant contact or extra information as investigation prerequisites; no stopping/delaying because further information was not supplied; no sending qualifying linked-account notices away to the issuing bank. ¶107(a)–(g), PDF 41–44. | Concerns the specified financial-service/error processes. This is not a prohibition on all lawful verification, fraud control or information requests. |
| Fraud controls and account exclusion | Policies must identify accounts suspected of fraudulently inducing transactions, prevent their operation and prevent associated individuals returning; track complaints/trends, provide refunds under Cash App policies and warnings for suspected scam transfers. ¶108(f), PDF 48. | The same order requires anti-fraud restrictions and notice/appeal safeguards. No named signal supplier, mandatory Lantern membership or cross-platform exclusion instruction appears. |
| Internal responsibility | Committee with required risk, compliance, business, customer-operations and data-science roles, and three working groups; assessment, escalation, reporting, resources and correction duties. ¶109, PDF 49–52. Board ultimately responsible; executives/Board review plans and submissions; annual Board-approved sworn progress report. ¶¶113–116, PDF 54–56. | These are mandated corporate responsibilities. The order does not identify outside NGOs or vendors as decision-makers. |
| Plans and supervisory records | Create/implement Compliance Plan within 120 days; provide it to Bureau on request. ¶¶110–112, PDF 53–54. Keep compliance, redress and complaint records in original electronic form, accessible for historical analysis; produce on request. ¶¶143–145, PDF 67–69. | Compliance Plan is not expressly subject to the same prior non-objection procedure as the Redress Plan. Required plans/reports were not obtained here. |
| Regulator oversight and complaint route | Identify CFPB complaint channel, remain on Company Portal and comply with response requirements. ¶¶148–149, PDF 70. On written request, additional sworn reports/testimony/documents within 14 days; consenting affiliated interviewees may have counsel. ¶¶150–153, PDF 71. | This supplies monitoring and escalation powers, not proof that CFPB independently adjudicates every restriction appeal. Bureau enforces order; ¶162, PDF 74–75. |
The earlier help article's eligibility screen and unspecified “up to 10 days” do not exhaust the operative duty. The order measures the appeal/change-status decision from receipt of the request and expressly uses business days. Establishing an actual violation would require the applicable procedure, request/notice dates and response, plus any relevant written modification; comparing two short public descriptions is insufficient.
Required money, allocation and timing
Order ¶¶117–125, PDF 56–60, require USD 75 million to be reserved or placed in a segregated deposit account within 10 days; redress to affected consumers is capped at USD 120 million. These are commitments, not observed paid amounts. ¶126–128, PDF 61, separately assess a USD 55 million civil penalty, payable to CFPB within 10 days for its Civil Penalty Fund. The notice's USD 175 million headline is the upper redress figure plus that penalty, not evidence USD 175 million reached consumers. Per ¶160, PDF 74, unspecified day limits are calendar days.
A further allocation distinction matters: if completed consumer redress is below USD 75 million, ¶123 requires the shortfall to be sent to CFPB 90 days after the Redress Report. CFPB may use it for further redress and may send impracticable/inappropriate-to-distribute residue to Treasury (¶124). Thus the minimum commitment does not guarantee USD 75 million is directly received by consumers. No return to Block is permitted for funds paid (¶132, PDF 63), and redress cannot be conditioned on customers waiving rights (¶125).
Affected categories and formulae are in ¶3(a), PDF 3–8, and ¶118, PDF 56–57. They include noninvestigated and wrongly timed unauthorized-transfer claims, partial-refund cases, omitted provisional credits, and frozen accounts that were later unfrozen. The latter requires a freeze of at least 14 days and balance of at least USD 25, with exclusions for specified law-enforcement/government/statutory grounds and customer-caused verification delay. Its payment is a pro-rata portion of USD 50, not a universal USD 50 per closed account. The category definition refers to transactions as of 1 July 2019; the order's release is separately limited to known pre-effective-date practices (¶157, PDF 73).
Within 120 days Block must submit its Redress Plan for the Enforcement Director's review/non-objection. The Director may require revision, due within 15 days; Block must follow the non-objected-to plan. ¶¶119–120, PDF 57–59. It must pay credit redress and begin non-credit redress within 30 days of non-objection (¶121); completion-report due within 15 days after plan completion (¶122). The report must state recipient/account counts and amounts paid. This packet did not obtain that report, the non-objection, plan-level distribution deadlines or any extension. A required payment is not evidence of receipt or timely completion.
Integration and next discriminating record
Defensible directional relations are CFPB → Block: imposes account-restriction notice/appeal and error-redress obligations; Block Board → compliance: has ultimate responsibility; CFPB Enforcement Director → Redress Plan: reviews/non-objects or requires revision; Block → affected consumers/CFPB: owes specified redress/penalty obligations. Distinguish each from implementation and payment events. The record supplies a material counterweight to an unrestricted-private-discretion narrative: a regulator identified procedural harms and imposed deadlines, reasons, record access for error claims and reporting. It also orders anti-fraud account exclusion, so neither unrestricted access nor unconditional restoration follows.
No mention of Lantern or Tech Coalition was found in the complete extracted order/stipulation or case/notice reading. That does not prove Cash App never uses those systems; it means this instrument supplies no attribution to them. General account restriction, transaction error, redress eligibility and Lantern signal correction remain separate mechanisms unless a later record joins them.
The strongest next discriminator is the Board-approved annual compliance report and implemented account-appeal procedure under ¶¶108(d),110–116, plus any written modification; for distribution, the Redress Plan, non-objection and ¶122 Redress Report. Custodians are Block and CFPB Enforcement. These would show how the legal requirement became a working process, what exceptions were applied and what was actually paid. Their existence is required by the order; this packet does not assert that they are publicly released. Acquisition stops here for the forest assessment.
Custody and reading scope
Five originals were obtained by ordinary unauthenticated GET, all HTTP 200, on 9 September 2026 at approximately 10:53 UTC. Metadata, final URLs, byte counts and SHA-256 are in captures-cfpb.json. cfpb-order.pdf SHA-256 8b72ad0538889fd6b4e9d1481806611955fb9a0e4e219bb87f2809471c351ed1; cfpb-stipulation.pdf SHA-256 7634dc07a22f9abfad610af9464c10101a5f897190fa6b9fba2597316f227100.
The order was read in full through the extracted text of PDF 1–75, with PDF 46 visually inspected for the notice/exception/appeal structure. The stipulation was read in full through PDF 1–6, with PDF 6 visually inspected because extraction of the final waivers/signature page was degraded. The full main article/case/docket bodies and displayed metadata were read from retained HTML; navigation/footer inventories were not treated as substantive source reading. Captured originals are sources; extracts and two PNGs are reading aids. No appeal submission, private account, outreach, paid route, canonical edit or further branch was undertaken.