How a card program fits together
A card that looks like one product is usually four or five companies in a row. Which seat a firm owns, and which it rents, is the whole overview.
Sample note, written to show the format. This is a structural overview, not a profile of a named company and not its accounts.
A card program that looks like one product to a customer is usually four or five companies standing in a row. Reading any of them starts with naming the seat, not the feature list.
The program manager owns the experience: the app, the balance the customer sees, the fees, the support desk. This is the company people mean when they say “the neobank”. It often does not own the licence that lets a card exist.
The BIN sponsor, sometimes called the issuer of record, is the regulated entity whose name is on the scheme membership. It holds the compliance relationship, the settlement account, and the argument when something goes wrong. A sharp product team can still be renting this seat.
The processor connects both of them to the scheme. It handles authorisations, clearing files, tokenisation for phone wallets, and the virtual cards an app wants to spin up in an afternoon. Switching processor is a long project pretending to be a procurement choice. Treat it that way.
The scheme sets the rules the other three live inside: chargeback windows, merchant categories, what a token is allowed to do. You do not negotiate those rules in a sprint.
Around that row sit the vendors a launch actually depends on. Identity, so an account can be opened. A sanctions screen. A manufacturer, if there is plastic. A ledger the processor will believe. For a program funded from digital assets, a way in and a way out, and a decision about which balance is allowed to fund the card in real time.
Which company is which
A useful overview asks which of those seats a firm occupies, and which it rents.
A firm that owns the app and rents the BIN, the processor and the ramps is a distribution company with a regulated partner. A firm that owns the BIN and sells it to many apps is infrastructure. They show up at the same conference. They do not have the same business, and a write-up that treats them as the same “card company” will misread both.
Launch work clusters in a predictable order. First the licence path and the BIN. Then the processor integration and the ledger. Then identity, so accounts can open. Then virtual cards, then plastic, then the phone wallets. Payment links and virtual accounts often ride alongside, because a card with no way to get money in is a demo.
Partnerships follow the same map. A wallet wants a card. A card program wants distribution. The term sheet is mostly about who owns the customer, who holds the float, and whose name is on the plastic. Those three answers matter more than the roadmap slide.
Nothing in this note is a revenue line, a valuation, or a claim about a named issuer. When a real program is worth filing, replace this file and keep the frontmatter. The question to keep is the same: which seat do they own?