Prioritizing robustness in card issuing
Bo Jiang, co-founder and CEO of Lithic, on the key primitives in card issuing
In card issuing, the low price option often shifts cost from the contract into the customer’s engineering and operations teams. The processor sits between the bank and the card networks, handles authorizations, clearing, settlement, card setup, and often compliance coordination. If that layer is weak, the customer ends up spending more time handling edge cases, building internal tools, and working around missing product flexibility, which matters more than a cheaper headline rate once card volume and complexity rise.
-
Lithic’s own positioning is that card issuing is one layer in a modular stack, not a cheap commodity API. It emphasizes specialized primitives, partner integrations for ACH, compliance, and crypto, and flexibility as a company’s roadmap changes, instead of trying to be the lowest priced all in one vendor.
-
Ramp described the tradeoff clearly. Smaller modern issuers can help teams launch faster, but larger and more established players tend to be stronger on operational support, supplier economics, and proven scale. That means buyers are balancing speed, roadmap fit, and long run robustness, not just initial pricing.
-
The work hidden behind a card program is very concrete. A processor configures BIN ranges, connects the bank to the network, routes network messages, monitors transactions against bank and network rules, and manages exceptions. Lithic built internal apps for these workflows because generic tools broke on its two layer B2B2C data model.
The category is moving toward fewer generic platforms and more infrastructure chosen for durability, flexibility, and fit with the customer’s exact use case. As embedded finance spreads beyond fintech into software and vertical products, the processors that win will be the ones that reduce operational burden over years, not the ones that simply look cheapest in the first sales cycle.