Every fintech partnership ends eventually — by choice, by failure, or by acquisition — and the exit is a compliance event as demanding as the launch. Most sponsor banks maintain detailed onboarding playbooks and nothing comparable for offboarding, which is how customer funds get stranded, records go missing, and monitoring lapses in the final months when risk is highest. An exit executed without a plan generates the same findings as a launch without diligence.
Key Takeaways:
- The Interagency Guidance on Third-Party Relationships treats termination as a formal lifecycle stage that requires planning, not improvisation
- BSA obligations survive the partnership: transaction monitoring runs through account closure, SAR obligations continue, and records must be retained for five years under 31 CFR § 1010.430
- The Synapse collapse showed publicly what ambiguous ledger custody and undefined wind-down responsibility cost end customers
- A complete wind-down plan assigns owners and deadlines for customer transition, records custody, complaint handling, marketing takedown, and middleware dependencies
Why Fintech Partnerships End
Offboarding is not an edge case; it is a lifecycle stage that arrives for one of four reasons. Compliance failure — the partner cannot or will not meet the bank's standard, findings persist across cycles, and the contractual termination triggers fire. Economics — the program never reached the volumes that justify its oversight cost, for either side. Strategic exit — the bank leaves BaaS partly or entirely, a path several institutions have taken publicly in recent years, often following supervisory pressure. The fintech itself fails or is acquired — funding runs out, or an acquirer moves the program to a different charter.
The reason shapes the timeline but not the obligations. A cooperative migration to another sponsor and a hostile termination for compliance cause both require the same core work: customers transitioned, funds disbursed accurately, records preserved, and monitoring maintained to the last day. Banks that discover this during the exit, rather than planning it before, do the same work under worse conditions.
What the Interagency Guidance Requires for Termination
OCC Bulletin 2023-17 makes termination the fifth stage of the third-party risk lifecycle and expects banks to plan for it: managing the transition to another provider or in-house operation, handling the risks of service interruption, and addressing data retention and destruction. The FDIC adopted the same framework in FIL-29-2023.
For a sponsor bank the stakes are higher than the guidance's general language suggests, because the "service" being terminated includes live consumer accounts holding insured deposits. The wind-down leverage the bank will need — cooperation duties, data delivery, funds transition mechanics, surviving records access — must already exist in the partnership agreement, because a fintech in failure or in dispute has little incentive to negotiate new obligations. The contract signed at the beginning of the relationship is the wind-down plan's legal foundation.
The Components of a Fintech Wind-Down Plan
Customer notification and account transition. The plan should specify who sends account closure notices and on what regulatory timelines, how final statements are produced and delivered, and the mechanics of funds disbursement: transfers to successor institutions, checks to last known addresses, and escheatment for unreachable customers. Every disbursement must reconcile against the ledger — which is precisely why ledger custody, covered below, decides whether this step is administrative or catastrophic.
Data migration and records custody. Before access to the fintech's systems ends, the bank needs complete customer records, transaction histories, complaint files, and compliance evidence in usable formats. Define the extraction format, the delivery deadline, and the validation step that confirms completeness — discovering a gap after the fintech's engineers have been laid off is discovering it too late.
Complaint handling during and after wind-down. Complaints spike during transitions, and they keep arriving after the program closes. The plan should name who handles them once the fintech's support team is gone, how customers reach that channel, and how regulatory complaints get escalated when the partner's compliance staff no longer exists.
BSA obligations that continue. Monitoring does not stop when the termination notice is signed. Transaction monitoring must run through the last account closure, SAR obligations under 31 CFR § 1020.320 continue for activity detected during and after wind-down, and records must be retained for five years under 31 CFR § 1010.430. Wind-downs concentrate exactly the behaviors monitoring exists to catch — rapid fund movements, account draining, mule activity exploiting reduced attention.
Marketing takedown. The fintech must stop representing the banking relationship the moment it ends: app store listings, websites, and archived pages referencing the bank or FDIC insurance through it. Representations of deposit insurance that no longer exist implicate 12 CFR Part 328, which prohibits misrepresentation of insured status and reaches non-bank entities. Takedown verification belongs on the checklist with a date and an owner, not an assumption.
Middleware dependencies. If a middleware platform sits between the bank and the fintech, the wind-down inherits its complexity: ledger data may live with the middleware provider, not the fintech, and the bank may need cooperation from a company it has no direct contract with. Map this dependency before termination begins, not during.
What the Synapse Collapse Taught the Industry About Wind-Downs
The 2024 bankruptcy of Synapse, a middleware provider that connected multiple banks to dozens of fintech programs, is the public cautionary example. When Synapse failed, the banks and fintechs it connected disputed whose ledger records were authoritative, and reconciling end-customer balances against pooled FBO accounts proved slow and contentious. Many end users lost access to their funds for extended periods while the parties and the bankruptcy court worked through records that no single institution fully controlled.
The lesson for wind-down planning is specific: ledger custody and reconciliation rights must be resolved in the contract, and verified continuously — not negotiated during a failure. A bank that cannot independently reconstruct which customer owns what, from records in its own possession, cannot execute a wind-down no matter how good the rest of the plan is. That capability is built or lost long before termination, in the daily discipline of FBO account reconciliation.
Communicating With Regulators During a Wind-Down
Regulators should hear about a material wind-down from the bank, early, not from customer complaints or press coverage. For terminations involving live consumer programs, notify the primary federal regulator before execution where feasible, share the wind-down plan with owners and timelines, and report progress at a defined cadence: accounts remaining, funds disbursed, complaints received and resolved, records secured.
Proactive communication changes the supervisory posture. A bank that presents a controlled exit with a plan demonstrates exactly the third-party risk management the FDIC's guidance on bank-fintech partnerships calls for; a bank that surfaces only after customers complain about frozen funds invites examination of everything else in the portfolio.
Post-Termination Records Retention
The relationship ends; the records obligation does not. The retention schedule needs named owners inside the bank, because the fintech will not exist to answer requests.
| Record category | Minimum retention | Post-termination owner |
|---|---|---|
| BSA records (CIP, monitoring, SARs) | 5 years (31 CFR § 1010.430) | Bank BSA officer |
| Account records and final statements | Per bank retention policy and applicable state law | Bank operations |
| Complaint files and dispositions | Through applicable limitation periods | Bank compliance |
| Wind-down execution evidence (notices, disbursements, reconciliations) | Retain permanently as examination evidence | Bank third-party risk function |
Examiners reviewing a completed wind-down will ask for exactly these artifacts. The wind-down file should read like a closing binder: every notice sent, every dollar reconciled, every record archived with an owner who can retrieve it.
How Sponsor Banks Make Exits as Controlled as Launches
Offboarding fails when it is treated as a negotiation that begins at termination instead of a program defined at signing. The banks that exit cleanly are the ones whose standard already includes the exit.
In Canarie, wind-down obligations are part of the standard the bank defines once and every partner inherits: cooperation duties, data delivery requirements, records custody, and monitoring-through-closure controls exist as assigned obligations from day one. When a termination trigger fires, the wind-down becomes a provisioned workstream — owners named, deadlines set, evidence captured for every notice, disbursement, and takedown — and the portfolio view shows regulators an exit under control rather than a scramble under scrutiny. The same system that stood the partner up stands the partner down.
See how sponsor banks keep every partner — including departing ones — under one standard →
Frequently Asked Questions
How long does a fintech partner wind-down take?
A cooperative migration to a successor bank typically runs three to nine months, driven by customer notification timelines, funds transfer mechanics, and data migration. A wind-down triggered by fintech failure compresses to weeks and gets harder, because the partner's staff and systems disappear while the work remains. The single biggest determinant of timeline is whether the bank can independently reconcile customer balances from records it already holds; banks that depend on the departing party's ledger discover their timeline is not theirs to control.
Who is responsible for customer funds during a fintech wind-down?
The bank. The deposits sit on the bank's balance sheet regardless of which fintech or middleware interface customers used, and the bank must ensure every dollar is disbursed to its verified owner — through transfers, checks, or ultimately escheatment for unreachable customers. This is why continuous FBO reconciliation matters before any exit is contemplated: the bank's obligation to return funds does not shrink because a third party's ledger is disputed or missing.
Do SAR obligations continue during offboarding?
Yes, fully. Suspicious activity reporting under 31 CFR § 1020.320 applies to activity detected during the wind-down and through final account closure, and wind-downs are high-risk windows — rapid fund movements and account draining concentrate exactly when staffing and attention decline. Transaction monitoring must operate at full capability until the last account closes, and supporting records fall under the five-year BSA retention requirement even though the partnership no longer exists.
What records must be kept after a fintech partnership ends?
BSA records — CIP documentation, monitoring output, and SAR support — must be retained for five years under 31 CFR § 1010.430. Account records, final statements, and complaint files follow the bank's retention schedule and applicable state law, and the wind-down execution evidence itself (notices, disbursement reconciliations, takedown confirmations) should be kept as permanent examination evidence. Every category needs a named owner inside the bank, because the fintech will not exist to produce records when an examiner or a customer asks.
Can a bank terminate a fintech partnership immediately for compliance failures?
Only if the contract permits it, and even then the operational reality intervenes: live customer accounts cannot be abandoned, so "immediate" termination in practice means immediate suspension of new business while the wind-down executes on a controlled timeline. This is why well-drafted agreements include both suspension rights and termination triggers, with wind-down cooperation duties that survive termination. The bank's obligations to customers and regulators continue regardless of how badly the partner behaved.