Apto Embeds Card Issuing in BaaS
Meg Nakamura, co-founder and CEO of Apto, on winning underserved markets with card issuing
This points to card issuing becoming a wholesale infrastructure layer, not just a direct sales product. Apto is trying to sit inside broader banking stacks like Dwolla, so a fintech that already uses one platform for money movement can add cards without sourcing a separate issuer processor from scratch. That matters because many BaaS platforms bundle accounts, ACH, and compliance, but still rely on specialist partners underneath for card issuance.
-
Apto had already used this motion early. Its first launch was with Dwolla in August 2015, and the goal since then has been to reduce the manual work required for a Dwolla customer to turn on a card program.
-
This reflects how the stack actually works. Many all in one BaaS providers package bank accounts, payments, and compliance, while outsourcing issuer processing to specialists like Marqeta, Visa DPS, or newer developer first vendors.
-
The closest comparable playbook is Lithic’s integration partner program with Dwolla and others. The value is not a loose referral, but shared guides, mapped funds flows, and engineering work that removes setup friction for joint customers.
The next step is deeper modularity. BaaS platforms will keep becoming storefronts for financial features, while specialist issuers compete to be the easiest card layer to plug in behind them. The winners will be the providers that turn card launch from a consulting project into a near instant product switch inside an existing banking workflow.