Subsequent enforcement-record finding (9 September 2026): the public descriptions analyzed below do not exhaust Cash App's obligations. The16January2025 CFPB consent order expressly requires restriction explanations and an account-appeal procedure with a10-business-day grant/deny deadline (paragraph108(c)–(d), qualified as stated). See the regulator packet. This narrows the earlier procedural gap; actual compliance, applicable modifications and a Lantern-specific correction/remedy trace remain unestablished. The original source-specific analysis below is preserved.
Observed 9 September 2026. Bounded agreement lane; no customer account, support contact, private API, historical contract reconstruction or enforceability opinion. The main instrument is the agreement with Block, Inc. It grants service-access and fund-access discretion separately. Neither contractual power proves why any particular account was closed, nor does closure itself establish loss of ownership of the remaining money.
The current official [Cash App Terms of Service](http[local research file] displays Effective 7 February 2024; Last Updated 26 August 2026. The original HTML and derived text are retained as agreement-cashapp-tos.html / .txt. The opening identifies Block, Inc. as the contracting company and says gray annotations have no legal effect (derived lines 1–10). Section II distinguishes revised terms from terms applicable to a dispute arising before a change (lines 213–219). This is a present public instrument, not proof of the terms accepted by the accounts in the 2025 Lantern example. Earlier search-index text displayed June 2026 dates; the captured original and fresh canonical page control this reading.
The incorporated [Acceptable Use Policy](http[local research file] was captured separately as agreement-cashapp-aup.html / .txt. Its displayed text has no effective/updated date; 9 September is the observation date, not an inferred adoption date. The complete policy was read, emphasizing the clauses below. These instruments are two related company sources, not independent corroboration. Exact URLs, response status, acquisition timestamps, sizes, SHA-256 hashes and scoped reading extent are in captures-agreement.json.
| Mechanism | Operative provision and retained locator | Evidence boundary |
|---|---|---|
| End service access | Terms XXIII.9, text 1276–1278: Block can suspend/terminate the account, associated accounts or service access for any reason; reasonable notification steps by email or next attempted app access. | Reasonable notice steps are not an advance-notice period, detailed-reasons promise or prior hearing. |
| AUP enforcement | AUP II, text 70–74: reported violations can produce suspension/termination without notice; suspected violations may be investigated. | Read alongside the general notice wording, without declaring which clause legally prevails in a specific dispute. |
| Delay ordinary cash-out | Terms VI.1(e)(iii), text 414: discretion to delay/limit transfers for financial exposure or investigation; also deferral/redirection/restriction for law, subpoena, court order or governmental request. | Do not say every restriction requires a court order; the clause includes other stated bases. |
| Balance after closure | Terms XXIII.11, text 1282–1284: pending transactions settle; withdrawal of custodial funds less applicable fees is conditional/discretionary; a new linked bank may be required; risk and investigation holds are permitted. | No universal release deadline here. The broader gray annotation about returning funds is expressly non-operative. A hold is not proof of confiscation. |
| Transaction refusal | Terms XXIII.4, text 1247–1252: funding sources and transactions can be restricted; notice has prohibited-transaction exceptions. | Available authority, not a demonstrated instruction from a particular network/bank. |
| Compelled fund action | Terms XXIII.3, text 1245–1246: freeze, withholding or remittance in response to specified binding instruments. | Distinct from the discretionary risk clauses and ordinary closure. No such order was acquired for the Lantern example. |
| Recover liabilities | Terms XXIII.1, text 1232–1242: recovery/setoff against account or linked funds for stated liabilities, disputes and other agreement grounds. | Do not convert contractual recovery language into a right to take every closed account's balance. |
| Custodial access | Terms VI.3, text 443–445; XXIII.8, text 1274–1275: separate corporate/customer funds, possible pooling, Block agency, access through Cash App rather than direct withdrawal from custodial banks/brokerages. | A documented intermediary access condition; neither partner-bank direction nor sole legal ownership by Block follows. |
The AUP has separate restrictions for criminal activity (including child sexual-abuse material), adult-content sales, and businesses believed to create elevated financial risk or breach bank/card-network policies (AUP I, text 35–36, 54–55, 62–63). This is a contractual route by which external policy can matter. It identifies no particular bank, policy version, instruction or causal role in the Lantern closures. Its sanctions subsection separately contemplates indefinite holding in apparent violations; that is not the universal rule for closed accounts (text 50–51).
The terms distinguish the Cash App service contract from a cardholder's agreement with the issuing bank; that bank agreement governs card use/bank relationship in an inconsistency (VIII.1–2, text 620–626). No individual customer's product/card agreement was obtained, and no bank-specific closure authority is asserted here. Custodial placement, card issuance and an instruction to close are different relations.
XXIII.19–20 contains a broad dispute definition and a separate pre-filing informal dispute process, including written notice, a personal conference and a 60-day negotiation window (text 1314–1323). This is not a routine support appeal or a promise to restore access. Only the opening and pre-filing paragraphs were substantively read; this packet does not evaluate enforceability, opt-outs or every arbitration condition. Parent's separately retained help article addresses operational closure review. Its ordinary withdrawal instructions should not be treated as overriding the agreement's hold conditions.
The public instruments establish a service-mediated path to money and a broad internal decision space. Competing explanations remain live: fraud/risk protection, compliance with an external obligation, enforcement of Cash App's own acceptable-use choices, or a mistaken decision. The contract alone cannot choose among them. Reinstatement review and balance release also remain different outcomes.
The most discriminating missing records are the actual closure reason/notice, applicable customer/product terms at the event date, any hold rationale and release ledger, and the internal or external instruction that caused the decision. The relevant holders would be Block's account/support/compliance records and, only if a bank or authority actually participated, that actor's corresponding instrument. No inference of current access to such records is made. No public account-level record was acquired for the 18-account Lantern example; no historical backfill, bank-name hunt or additional acquisition is proposed by this packet.
Acquisition closed after two successful ordinary public GETs. Full original capture is not a whole-document legal review. No canonical graph, package or research note outside this lane was modified.