Commodity Dynamics of Card Issuing
Founder of startup card issuing platform on the competitive dynamics of card issuing
The strategic edge in card issuing does not come from owning a unique layer, it comes from running a commodity layer with fewer failures, lower cost, and more control at scale. In practice, sponsor banks, networks, processors, and middleware all perform standard jobs that can be swapped in theory. What is not easily replicated is a processor that can authorize transactions in real time, keep the ledger correct, stay online during volume spikes, and support migrations without downtime.
-
The most commodity parts are the wrappers around the core rails. A BaaS platform can bundle bank access, card manufacturing, compliance workflows, and processor integrations into one contract, which is valuable for speed, but the underlying components are still largely interchangeable. That is why companies like Bond sit above processors like i2c, and why larger fintechs often move closer to the processor as they scale.
-
Core transaction processing is the least commodity part in practice, even if it looks commodity on a market map. This is the system that receives an authorization request, checks rules and balances, updates the ledger, and returns an approve or decline decision in milliseconds. Marqeta, Galileo, i2c, and Lithic are hard to replace because that engine is technically difficult and switching it risks real downtime on billions of dollars of volume.
-
The money also pushes the stack toward commodity behavior. On a typical card transaction, interchange is split across the bank, network, processor or program manager, and the fintech brand. As customers gain scale, the bank and infrastructure layers usually get squeezed on take rate, while the customer facing fintech keeps more. That makes reliability, speed to launch, and fit for a specific workflow more important than claiming a unique toll booth in the stack.
The next phase of the market favors providers that either own the hard processing layer or package commodities into a much better workflow for a specific customer. Generic wrappers keep getting compressed. The durable winners are the ones that make cards easier to embed into real software products, or make the underlying transaction engine so dependable that customers will not risk moving off it.