Bond as Program Manager in BaaS

Diving deeper into

Roy Ng, co-founder and CEO of Bond, on BaaS's business model

Interview
we are what we call a "program manager" for our brands.
Analyzed 6 sources

Calling itself the program manager means Bond is not just selling APIs, it is taking over the messy operating job between brand, bank, network, and processor. In practice that means Bond helps decide what customer data to collect, manages compliance reviews, coordinates the sponsor bank, and runs day to day issue handling, so a software company can launch cards or accounts without building a bank operations team from scratch.

  • This role sits in the middle of the money flow. In BaaS, the program manager often receives interchange first, covers fraud losses and operating costs, then shares the remainder with the fintech. That is why program management is higher touch and higher risk than pure processing or APIs.
  • The concrete value is abstraction of the bank relationship. A brand can come to Bond with a card or account idea, while Bond chooses the bank partner behind the scenes, works through approvals, and handles much of the compliance back and forth that would otherwise stretch launch timelines into months.
  • This is also where Bond differed from bank friendly marketplace models like Synctera. Bond emphasized taking work off the brand's plate, while Synctera described itself more as a facilitator that lets banks and fintechs share visibility and responsibility directly on the same platform.

The category has been moving toward tighter oversight and more explicit bank supervision, so the winning program managers will look less like simple API wrappers and more like operating systems for compliance, case management, and bank coordination. Bond's later sale to FIS points in that direction, where scaled infrastructure providers absorb this operational layer and sell it as part of a broader embedded finance stack.