Own the Cardholder Relationship

This is really a warning about who controls the customer and the economics. In card issuing, the company that owns the cardholder relationship decides the onboarding flow, sees the user behavior, handles support, and has standing with the sponsor bank. If a BaaS provider sits between the program and the end user, it can turn the fintech into a thin distribution layer, making it easier to lose the bank relationship, accept worse interchange splits, and get boxed out of product decisions.

• A mediated setup can be fast at launch because the BaaS has prebuilt templates and bank connections. But that speed usually comes from accepting someone else’s default compliance flow, card setup, and bank relationship, which becomes restrictive once the program wants custom KYC, new card products, or direct access to the sponsor bank.
  1 sacra 3 sacra
• The money angle matters because debit economics are thin. BaaS providers often add their own take through interchange share, account fees, program management, or card production. Broader BaaS research shows interchange is the main revenue pool, so every extra middle layer directly cuts into already narrow margins.
  1 sacra 2 sacra 4 sacra
• The pattern in the market is launch on an all in one stack, then unbundle as volume grows. Card infrastructure providers like Lithic and Highnote both describe a breakpoint where scaled programs want more modularity, more direct bank dialogue, and more control over ledgering, compliance, and card operations.
  3 sacra 4 sacra

Going forward, the winning fintech programs will treat BaaS as a temporary assembly layer, not the permanent owner of the program. As sponsor banks tighten expectations and larger programs demand direct dialogue, the market will keep shifting toward structures where the fintech owns the cardholder, owns the data, and can replace vendors without rebuilding the whole stack.