Card Issuing as Modular Fintech Layer

Diving deeper into

Nikil Konduru, GTM Strategy at Lithic, on the future of card issuing

Interview
Our philosophy is that the future of fintech infrastructure is in modular, interoperable APIs.
Analyzed 5 sources

Lithic is betting that card issuing becomes a layer in a larger fintech stack, not the whole stack. In practice, that means owning the hard card primitives, authorizations, network connectivity, controls, settlement, and card manufacturing, while leaving ACH, ledgering, KYC, and crypto ramps to specialists that can plug in cleanly. The strategic goal is to help customers launch unusual products faster, without forcing them into one vendor’s roadmap.

  • The customer tradeoff is speed now versus flexibility later. All in one BaaS works like a preconfigured suit for teams that want to launch quickly and avoid bank relationships. Lithic fits better once a fintech wants custom KYC, new card products, bespoke physical cards, or direct coordination with its sponsor bank.
  • This modular view is shared by adjacent infrastructure players. Sila focuses on ACH, ledgering, and compliance, then partners for card issuing instead of trying to do everything itself. That is the real meaning of interoperable APIs here, fewer hand built services layers, more specialist systems connected through shared docs, mapped funds flows, and coordinated implementations.
  • The competitive contrast is not just product architecture, it is go to market. Legacy processors and Marqeta were built around large enterprise programs and heavier implementations. Lithic’s self serve model aims at the long tail of Seed through Series C fintechs and embedded finance companies that need to test cards quickly, then add more modules as they scale.

Over time, fintech infrastructure is likely to split the way enterprise software did, with suites serving simpler use cases and modular stacks winning where product differentiation matters most. If that happens, issuer processors that behave like clean building blocks, and invest in partner integrations instead of trying to own every layer, should become the default starting point for the next wave of embedded finance products.