Apto applies Stripe motion to issuing
Meg Nakamura, co-founder and CEO of Apto, on winning underserved markets with card issuing
This reveals that Apto saw the real prize in card issuing as copying Stripe’s product motion, not its product category. Stripe turned acquiring into a self serve developer business where a team can sign up, get keys, and start building without a long integration project or sales process. Apto’s bet was that issuing could work the same way for startups and mid market builders that were too small or too custom for enterprise first issuers.
-
Acquiring and issuing solve different jobs. Stripe’s core business lets a merchant accept card payments online. Issuing lets a company create cards for its own users, drivers, shoppers, or employees. Apto admired the go to market model from acquiring, then applied it to the slower, more manual issuing layer.
-
That mattered because much of issuing was still sold like enterprise software. Marqeta built the category and proved scale with a small number of very large customers, while newer issuer processors aimed at the long tail with self serve APIs. Apto positioned itself with that second group, focused on removing manual setup and letting developers configure programs directly.
-
The deeper implication is customer mix. Big issuers can win a few giant accounts and grow with them, but a developer first issuer can aggregate hundreds of smaller programs and hope some break out. That is closer to Twilio’s model, and it fits Apto’s emphasis on experimentation, fast launches, and pay as you go economics.
The market keeps moving toward embedded finance inside software products, which favors infrastructure that is easier to start with and easier to customize later. The winners in issuing are likely to split into two lanes, enterprise platforms serving the biggest programs, and developer first platforms serving the broad middle where speed, flexibility, and self serve onboarding matter most.