Privacy as Lithic's First Customer
Charles Birnbaum, partner at Bessemer Venture Partners, on the five waves of fintech
Privacy as the first and biggest user made Lithic better before Lithic had outside scale. Every card decline, merchant quirk, fraud edge case, and customer support fire hit the company on its own consumer product first, which forced the team to harden the API, speed up debugging, and design features around real transaction flows instead of hypothetical enterprise requirements. That gave Lithic a live test environment that most infrastructure startups do not have.
-
Privacy started as a consumer virtual card app, then exposed the internal issuing stack it had built to power itself. That meant Lithic was born from operating pain, not from a greenfield API idea, and the B2B product had already been used in production before broad enterprise selling began.
-
The practical benefit is edge case density. Years of Privacy transactions let the team identify and fix thousands of card issuing issues across authorizations, settlements, card controls, and reliability. That is especially valuable in issuing, where small bugs create failed payments, support tickets, and compliance risk fast.
-
This also shaped Lithic's market position versus older processors and all in one BaaS vendors. Instead of selling a rigid package, Lithic built modular card primitives for teams like Mercury and Novo that wanted to customize flows, because the platform had already been stretched by an internal product with real user demands.
Going forward, this internal customer loop points to how modern fintech infrastructure will keep differentiating. The winners are likely to be platforms that are tested by real money movement every day, then turned outward as flexible tools for other builders. In card issuing, that makes product speed and resilience compound together over time.