Cards as Reconciliation Anchor
Bo Jiang, CEO of Lithic, on the power of the cards as a digital payment rail
This modular ACH stance is really a wedge to own the reconciliation layer, not a push to win ACH processing itself. Lithic is trying to become the system that shows a customer every debit, credit, fee, and settlement in one place, while letting card issuance stay the anchor product. That makes ACH an attach product and reduces the risk that a customer avoids Lithic just because they already use Sila, Dwolla, or another ACH stack.
-
The practical buyer is a payments team that already has an ACH vendor wired into bank accounts, ledgering, and compliance flows. Letting that team keep its ACH provider removes a painful replatforming step, while still letting Lithic plug card data and settlement data into the same reconciliation view.
-
This fits Lithic's long running product philosophy. Across earlier interviews, Lithic describes itself as a point solution for programmable card issuing inside a composable fintech stack, with partners like Sila and Dwolla filling adjacent jobs. The company has consistently positioned flexibility as the alternative to all in one BaaS bundles.
-
Order shows why this matters in practice. Order uses Lithic virtual cards for vendor payments, wants broader ACH support, and cares most about unified workflows, easier reconciliation, and a single payments channel inside its software. For that customer, rail choice matters less than whether the platform keeps books clean and operations simple.
The next step is a multi rail control plane where cards, ACH, and newer bank payment methods all run through one ledger and one reconciliation workflow. If Lithic keeps card issuing as the high control product and layers in enough ACH to complete the workflow, it can expand wallet share without becoming a generic standalone ACH vendor.