Seed-Series C Overlooked in Issuing

The strategic bet is that card issuing expands fastest when it stops being a whale sale and starts being a developer tool. Legacy and first wave issuers were built for large fintechs that could tolerate long implementations, monthly minimums, and heavy support. That left Seed through Series C companies with real product ideas, but not the budget or staff to navigate manual setup, bank coordination, and bespoke integrations, so fewer new card use cases ever got built.

• Marqeta proved the enterprise model, serving about 160 customers at roughly $3M in revenue per customer, but that model naturally pulls product and sales effort toward a few very large accounts. Smaller startups get deprioritized because supporting them with the same manual motion does not pay back.
  2 sacra
• The missing startups were not just smaller versions of Brex. They included insurance payouts, procurement software, travel fulfillment, incentive programs, and other products where a card is one workflow step inside a broader app. These teams need sandbox keys fast, flexible controls, and modular integrations, not a full bank in a box.
  3 sacra 4 sacra 5 sacra
• This is why self serve matters economically despite lower ACV. A developer first issuer can treat its customer base like a venture portfolio, where many small programs stay small, but a few compound into very large payment flows. That is the same pattern seen in Twilio style API businesses and in issuer processing more broadly.
  2 sacra 4 sacra

Going forward, the winners in issuing are likely to split into two lanes. One lane serves giant programs with deep service and custom economics. The other captures the long tail with software, automation, and modularity, then grows alongside the breakout customers that emerge from that pool. That second lane is where new card driven product innovation is most likely to come from.