Card Issuing as Product Lock-in
Banking-as-a-Service: The $1T Market to Build the Twilio of Embedded Finance
Card issuing becomes most strategic when it makes a software product harder to leave, not when it is treated as a profit center. In embedded finance, the card is the operating handle for money inside the app. It lets the product control when funds move, where they can be spent, and what data comes back. That creates features like instant worker payouts, merchant locked virtual cards, spend controls, and automated expense flows that make the core software more useful every day.
-
The cleanest contrast is fintechs like Chime or Cash App versus apps like Instacart, Uber, or Squire. Fintechs push card volume because interchange is a main revenue source. Embedded finance companies use issued cards to make a workflow work better, like paying a courier at checkout or loading a barber’s pay and tips instantly after a shift.
-
What the card actually adds is programmability. Marqeta and similar platforms made it possible to instantly create virtual cards, set merchant or amount limits, and approve or deny transactions in software. That is why cards fit naturally into products like BNPL, expense management, fleet, and marketplace payouts, where the app needs precise control over each payment.
-
This is why vertical software keeps moving into finance. Once a SaaS product already manages bookings, payroll, invoicing, or job workflows, adding cards and accounts lets it absorb the cash flow too. The result is a vertical ERP, where payments, balances, and spend live inside the same product instead of leaking out to a bank or separate tool.
The next phase is more software companies using cards as an embedded control layer for specific money moments, then expanding into accounts, lending, and payouts. The winners will be products that turn card issuing into a daily workflow primitive, because that is what makes retention compound and gives the software room to monetize later across a much larger financial surface area.