BaaS Program Managers Capture Interchange

Taking the program manager role turns a BaaS platform from a software vendor into the economic owner of the card program. In practice, that means interchange lands with the party running the program, then gets split out after fraud losses, chargebacks, compliance work, and operations are covered. That is why platforms that manage the program can price more flexibly and onboard riskier or earlier stage fintechs, because they control the cash flow coming off every swipe.

• The job is bigger than just routing API calls. Visa describes a launch stack with a bank, an issuer processor, and usually a program manager. The program manager handles lifecycle management and profitability on the issuer's behalf, which is why interchange economics usually sit there rather than with a pure processor.
  3 visa 4 visa
• The trade is revenue for liability. In the interview, the former Galileo executive explains that the program manager absorbs fraud and operational losses, and shares remaining interchange with the fintech. In a fee for service model, the fintech keeps more interchange, but the BaaS provider has to bill separately and take collection risk.
  1 sacra
• This also explains why pure processing is structurally lower take rate. Marqeta has disclosed that growth in programs where it provides processing with little or no program management reduces revenue mix. As fintech customers scale, more of the interchange pool gets negotiated upward to the customer, compressing the infrastructure layer beneath them.
  2 marqeta 5 sacra

The market is moving toward a clearer split between full stack operators that want interchange and control, and thinner infrastructure providers that sell software and processing. As sponsor bank oversight gets tighter, the platforms that can actually run program management, absorb losses, and keep compliance operations tight will own the most valuable slice of BaaS economics.