Lithic.

You've probably swiped a Lithic card without knowing it.

Somewhere right now, a debit card is being tapped against a reader. The cardholder thinks about their coffee, not their plumbing. They have no idea that the authorization racing through the network - approved or declined in milliseconds - runs on infrastructure built by a 170-person company in lower Manhattan. That company is Lithic, and being invisible is exactly the point.

Lithic builds the card issuing and money-movement rails that other companies build their products on top of. When a fintech wants to hand its users a debit card, a business wants to issue corporate cards, or a brand wants a branded wallet, the hard part has always been the same: the issuing infrastructure underneath. Lithic turned that hard part into an API call.

Card issuing was a months-long ordeal.

The card networks are old. The bank partnerships are slow. The legacy processors were built for an era when "integration" meant batch files and a fax machine within reach. If you wanted to launch a card program the traditional way, you signed multi-year contracts, waited months, and inherited tooling that treated developers as an afterthought.

Lithic's founders knew this firsthand, because they had already lived it. Before Lithic, they ran Privacy.com - a consumer app that let people generate disposable, merchant-locked card numbers to protect their real ones. To build that, they had to wrestle with the same legacy issuers everyone else did. The infrastructure was the bottleneck, and the bottleneck was the business.

Build the rails. Then sell the rails.

Bo Jiang, Jason Kruse, and David Nichols made a decision that sounds obvious in hindsight and reckless at the time: if the existing card-issuing infrastructure was the problem, they would build their own. Not as a feature of Privacy.com - as the whole point.

So they did the slightly ironic thing of building plumbing so good that they decided to rent it out. In 2019, they opened a beta giving developers access to their card-issuing API. Early product-market fit followed. In 2020 came a $10.2M Series A. In May 2021, the company rebranded from Privacy.com to Lithic and announced a $43M Series B led by Bessemer. Two months later, Stripes led a $60M Series C at a roughly $800M valuation. Same company, same founders, two rounds, one summer.

A few API calls between you and a working card program.

What Lithic sells is deceptively simple to describe and genuinely hard to build. Developers can create and manage virtual and physical cards, push them into Apple Pay and Google Pay, set granular spend controls, and watch transactions stream in real time. Underneath sit the unglamorous-but-essential parts: ACH and money movement, fraud detection, 3-D Secure, chargeback handling, reconciliation, and the compliance tooling that keeps regulators content.

Then there are the newer modules. A Commercial Revolving Credit API for businesses that want to issue actual credit, not just debit. Issuing across both the Visa and American Express networks. And an integration with Visa's latest enrollment API that turns what used to be a multi-day batch process into something closer to real time.

Customers, networks, and a billion dollars a year.

Infrastructure companies live or die on who trusts them. Mercury, the banking platform for startups, scaled its debit and credit card programs on Lithic. Coinstar - yes, the coin-counting machines - picked Lithic to power the CINQ by Coinstar reloadable debit card. And the headline number that infrastructure companies care about: Lithic has surpassed $1 billion in annual processing volume.

The networks signed on too. Lithic issues across Visa and American Express, and its Visa enrollment integration was built to assign interchange and activate benefits in near real time rather than the days legacy methods take. For a business whose revenue runs largely on interchange, "faster interchange" is not a footnote.

Make money programmable.

Lithic's stated ambition is to make money programmable - to treat a card not as plastic but as a digital payment rail you can write logic against. It is a developer's view of finance: if you can express the rule in code, you should be able to enforce it at the point of payment.

That philosophy shows up in the small choices, too. A chunk of the stack is written in Rust, a language chosen for safety and speed rather than fashion. The company runs a B2B platform and a B2C product (Privacy.com is still alive and well) in parallel, which gives it a rare double view: it is both the landlord and a tenant of its own rails.

The next card company won't build a card company.

Every brand is becoming, in some small way, a financial company. The loyalty app wants a wallet. The marketplace wants instant payouts. The startup wants corporate cards on day one. None of them wants to spend two years and a legal team learning the difference between an issuer and a processor. They want to ship.

That is the future Lithic is positioned for: a world where launching a card or moving money is a build decision, not a corporate saga. The competition is real - Marqeta, Stripe Issuing, Galileo, Highnote - and the networks and regulators set the weather. But the direction of travel is clear, and Lithic has spent a decade pointed at it.

So return to that coffee shop. The card taps. The reader beeps. Approved. The cardholder walks out thinking about absolutely nothing technical, which is the whole achievement. The infrastructure did its job by disappearing - and somewhere in lower Manhattan, that counts as a very good day.