# Ground brief — bank-fintech-partnership-as-distribution-rent

**Status:** grounded (2026-07-31)  
**Vertical:** fintech  
**Claim (particular):** Bank–fintech partnerships are often a mutual rent of scarce assets: the bank rents its **regulatory perimeter, deposit insurance branding, and balance-sheet access**; the fintech rents **UX, marketing, and customer acquisition**. Neither side “owns” the customer cleanly — third-party risk guidance and joint agency statements treat the bank as still accountable when third parties deliver bank products.

## Who is arguing what

| Actor | Position | Source |
|-------|----------|--------|
| OCC/Fed/FDIC interagency third-party guidance (Jun 2023) | Banks must manage risks of third-party relationships including novel fintech structures | https://www.occ.gov/news-issuances/bulletins/2023/bulletin-2023-17.html |
| Joint statement on deposit delivery via third parties (Jul 2024) | Risks when third parties market/distribute bank deposit products to end users | https://www.occ.treas.gov/news-issuances/news-releases/2024/nr-ia-2024-85a.pdf |
| OCC/Fed/FDIC RFI bank-fintech arrangements (2024) | Agencies soliciting info on nature of bank-fintech arrangements and risk management | https://www.occ.gov/news-issuances/bulletins/2024/bulletin-2024-21.html |

## Facts that must appear

1. **June 2023 interagency third-party risk management guidance** applies across relationship types, including fintech.  
2. **Banks remain responsible** for safety, soundness, and compliance even when UX is outsourced.  
3. **July 2024 joint statement** targets arrangements where nonbanks facilitate bank deposit products.  
4. **RFI (2024)** shows supervisors still mapping the rent structure, not declaring it solved.  
5. **Economic structure:** sponsor bank fee/spread vs fintech CAC and interchange/float share — both are rents on scarce licenses and scarce attention.

## Theory hook

- Regulatory perimeter; two-sided platforms; rent vs ownership of customer relationship.

## Real case

Supervisory primary documents (guidance + joint statement). Do not invent a specific failed BaaS stack unless citing a public consent order by name (optional if time; skip to stay clean).

## Retrieval gaps

- Specific consent orders (e.g. named banks) would strengthen but are optional; guidance alone supports the accountability claim.

## Source test (must pass)

Every Source note must answer: *which sentence fails if this URL is removed?*