App-only banks present a single clean product, yet much of what makes the account work is supplied by other institutions. Understanding which parts are borrowed explains both their speed and their limits.
The licence is the expensive part
A full banking licence requires capital, governance and continuous regulatory reporting. Obtaining one takes years, and holding one constrains how quickly a firm can change its products.
Many app-based providers therefore operate under a partner bank's licence or under a narrower payments authorisation. The customer sees one brand while a licensed institution holds the deposits.
This distinction determines what the provider may legally do. Holding deposits, lending and issuing cards each sit under different permissions.
The ledger often belongs to someone else
Core banking systems record balances, apply interest and produce statements. Building one is slow, so newer providers frequently license a core platform instead.
The app then becomes a layer of design and logic sitting on top of that ledger. Features that feel novel are often familiar mechanics presented more clearly.
Because the ledger is shared infrastructure, several unrelated brands can run on the same underlying platform. Their differences are real but sit above the accounting layer.
Card issuing runs through a processor
Issuing a physical or virtual card requires membership of a card network, a bank identification number and a processor to authorise transactions. Few new entrants hold all three directly.
Specialist issuer-processors package these together, which is why a new card product can launch in months rather than years. The processor makes the authorisation decision in milliseconds.
Control of that decision matters. A provider that cannot set its own authorisation rules is limited in how it manages fraud and spending controls.
Deposit protection follows the licence, not the brand
Where money is protected depends on which institution holds it. If deposits sit with a partner bank, protection is generally provided through that bank's scheme.
Balances held under a payments authorisation are usually safeguarded rather than protected by a deposit scheme, which is a different legal mechanism with different consequences in a failure.
Providers disclose this, but it appears in terms rather than in the interface. Customers regularly assume the app they use is the institution holding their money.
Why the model persists
Outsourcing infrastructure lets a provider compete on the parts customers actually touch, which is the app, the support and the pricing. Those are also the parts easiest to change.
The cost is dependence. A partner's decision on risk appetite or pricing can force product changes the brand did not choose.
Some providers eventually obtain their own licence and migrate the stack inward. That transition is slow and usually visible to customers as a period of restricted features.