Issuing Primitives versus Managed Services

This is the core trap in card issuing, the closer an infrastructure company gets to custom enterprise work, the more it risks selling people time instead of selling repeatable software. In practice that means engineers and ops teams get pulled into one customer’s reconciliation rules, bank setup, card controls, fraud workflows, and money movement edge cases, which slows self serve product work and lets big customers start steering the roadmap.

• Legacy processors often looked like managed service businesses with technology attached. Ramp described older providers like TSYS and First Data as blends of services and tech, while newer issuers won by replacing more of that handholding with cleaner APIs and faster developer workflows.
  2 sacra
• The commercial pressure comes from concentration. Research on BaaS and card issuing shows large providers can end up with a few giant customers, and once a customer gets big enough it pushes on price, asks for roadmap priority, and can treat the processor as middleware to optimize away or bring in house.
  3 sacra 4 sacra 5 sacra
• The strategic alternative is to stay narrow and modular. Lithic is positioned as an issuer processor 2.0 for developers, while Brex shows the opposite path, owning more of the stack directly to serve global enterprise needs, including network connectivity, credit operations, and country by country rollout work.
  1 sacra 3 sacra 6 sacra

Going forward, the winners in issuing will split more clearly into two camps. One group will become software primitives with strict product boundaries and broad self serve distribution. The other will move upstack into deeply integrated enterprise infrastructure, where they can justify the heavier service load by owning more economics and more of the customer workflow.