The previous lesson sorted out when you legally need a license. Most builders who get to that answer decide they do not want to acquire a charter, raise the capital a charter demands, or wait the year-plus it takes. So they rent. Renting a license means standing on a sponsor bank's charter through a Banking-as-a-Service (BaaS) arrangement: the bank holds the regulated permissions, and you build the product on top.
This is the most common path to market for a card program, a deposit-style wallet, or an ACH money-movement feature. It is also the path that produces the most painful surprises, because the thing you are renting is not a commodity. The bank controls assets and authorities that, in a bad month, it can pull. Understanding exactly what stays on the bank's side of the line is the difference between a partner relationship and a hostage situation.
What you are actually renting
You are not renting "a license" as a single object. You are renting a bundle of specific regulated capabilities, and each one belongs to the bank, not to you.
For card programs, the core asset is the BIN. A Bank Identification Number is the prefix on a card that routes it to an issuer on the Visa or Mastercard network. In the US, BINs are issued only to chartered banks, and the BIN remains the property of the bank and the card network. When you "issue" cards, you issue them on the bank's BIN under a sponsorship arrangement. The bank is the issuer of record in the network's eyes and acts as guarantor for your program's behavior.
For deposit-style products, you are renting the bank's ability to hold insured deposits. Customer balances sit in an account the bank owns, usually a custodial or for-benefit-of (FBO) structure, with your end users as the beneficial owners underneath. For ACH and wire movement, you are renting the bank's access to the rails and its standing with the operators.
The pattern is the same across all three. The regulated thing lives with the bank. You operate the experience.
What the partner controls
The bank keeps a short list of levers, and you should be able to name every one of them before you sign.
Compliance ownership and the kill switch
Regulators have been blunt that the bank owns the compliance obligation. You may run onboarding, underwriting, and transaction processing, but the sponsor bank remains responsible for every regulatory requirement attached to those activities, including BSA/AML, sanctions screening, and consumer-protection rules. That ownership is why the bank gets approval rights over your marketing, your customer-service scripts, and material program changes, and why it requires daily, weekly, or monthly oversight reporting.
It also means the bank can suspend or terminate your program. If an examiner flags the bank's fintech book, the cheapest fix for the bank is often to offboard the program causing the heat. Several banks did exactly this in 2024 and 2025 after consent orders landed. Treat the kill switch as real, not theoretical.
The funds and the ledger
In a custodial or FBO setup, the money is in the bank's account. Your ledger says which end user owns which slice, but the bank's records are what deposit insurance and a receiver ultimately rely on. If your ledger and the bank's ledger disagree, the bank's view governs, and your customers are exposed to the gap.
The Synapse collapse in April 2024 is the case study every builder should know. Synapse sat between fintech programs and partner banks including Evolve, and its ledger of who owned what diverged from the banks' records. When Synapse failed, no one could cleanly reconcile the FBO pools, and end users lost access to funds for months. The FDIC's response, a proposed recordkeeping rule for custodial accounts with transactional features published on October 2, 2024, would require banks to keep records identifying each beneficial owner and to reconcile those accounts daily. As of mid-2026 it remains a proposal, not a final rule, so do not assume the protection exists yet. Build the reconciliation discipline yourself. Lesson 9 goes deep on this.
The account of record and Regulation E
Under Regulation E, the institution holding the account of record carries the legal obligation for error resolution and dispute handling. In a BaaS program that is the bank, even when your app is the only thing the customer ever sees. Your contract has to spell out who actually performs disclosures, dispute intake, and the investigation clock, because regulators will hold both parties accountable if a consumer is harmed. Ambiguity here is not a paperwork problem. It is a liability you discover during your first dispute spike.
A worked example
Say you are launching a spending card for gig workers. You sign with a sponsor bank and a program-manager platform that sits between you and the bank.
The bank provides the BIN, so every card you ship is the bank's card on the network. Customer balances land in an FBO account the bank owns; your platform's ledger tracks each worker's balance underneath. You build the app, set the rewards, and run first-line support. The bank reviews your launch creative, sets a monthly active-account cap for the first two quarters, and requires a daily transaction and balance file.
Now a worker disputes a $240 charge. Under Regulation E the bank is on the hook for the resolution timeline, but your contract assigns first-line intake and evidence-gathering to you, with the bank making the final call. If your reconciliation between the platform ledger and the bank's FBO balance is off by even a few thousand dollars across the book, that is the exact failure mode that turned Synapse from an outage into a catastrophe. None of these are edge cases. They are the operating reality of renting, and each one traces back to a control the bank never handed over.
The takeaway
Renting a license is a legitimate, fast way to ship, and for most builders it is the right first move. Just go in clear-eyed about the trade. You get speed and you skip the capital and the charter wait, but you do not get control of the BIN, the funds, the compliance obligation, or the off switch. The contract is where those boundaries are set, so read the program agreement for who owns the account of record, who reconciles the custodial balance and how often, what triggers suspension, and how a wind-down works if the bank exits BaaS. The builders who survived 2024 were not the ones with the best app. They were the ones who knew exactly what their partner controlled, and had reconciled to it daily, before anyone asked.