Program Manager vs Processor Tradeoffs
Ronnie Caspers, Product at Lithic, on using Retool for fintech ops
The program manager model turns a card partner into the operating layer of the business, not just the transaction engine. A processor mainly moves authorizations and settlement messages between bank and network. A program manager also handles the messy launch and compliance work, like BIN setup, bank and network coordination, and ongoing controls. That is why Lithic built internal ops apps around configuration and approvals, because program management creates a large human workflow that pure processing does not.
-
In a processor only setup, the fintech keeps more of the stack and usually more control, but must assemble other pieces itself, including bank partner, KYC, ledger, compliance workflows, and card operations. That is closer to a DIY model with more engineering and operating burden.
-
In a program manager setup, the partner usually takes on launch work and day to day oversight, and economics shift accordingly. In card economics, the program manager can take roughly 0.25% of interchange in addition to bank and network fees, reflecting that extra operational and compliance layer.
-
The line is getting blurrier. Some newer platforms try to offer both processing and program management in one system, or let customers start with managed services and take more in house later. That flexibility matters because scaled fintechs often want direct bank relationships and tighter control over product behavior and margins.
The market is moving toward hybrid models. Early programs will keep buying program management to launch faster and satisfy banks, while larger fintechs will increasingly pull pieces back in house once card issuing becomes core to product and P&L. The winners will be providers that can support both phases without forcing a full rebuild.