The program model decision determines everything that follows.
BaaS, direct MTL, or hybrid — the choice determines your margin structure, compliance exposure, and long-term flexibility. Most teams make this decision reactively, after a vendor has already been selected. We define it first.
BaaS vs direct MTL vs hybrid
Each model carries different economics, compliance obligations, and operational requirements. The right choice depends on your product, distribution strategy, and risk appetite — not on which vendor has the best sales process.
Hybrid structures
Many programs benefit from hybrid structures that combine elements of different models. Defining the hybrid architecture requires understanding the trade-offs of each component.
Economics implications of the model choice
Interchange ownership, revenue sharing, and fee structures differ materially across program models. The economics need to be modeled against the program model before the decision is made.
Compliance obligations by model
Each program model carries different compliance obligations — licensing, sponsor bank requirements, and controls frameworks. These need to be understood before the model is selected.
Scalability and optionality
The program model determines the long-term scalability of the program and the optionality to evolve. Programs designed for launch often hit structural limits as volume grows.
- Model the economics of each program model against your product and distribution strategy
- Define the compliance obligations and licensing requirements for each model
- Identify the right model — or hybrid structure — for your program
- Document the decision rationale for future reference and partner alignment
- Define the infrastructure requirements that follow from the model decision
What goes wrong when this is skipped
Model selected by vendor recommendation
Vendors recommend the model that fits their platform. This is rarely the model that best fits the program's economics, compliance, and scalability requirements.
Economics discovered after launch
Programs that select the model without modeling the economics discover margin compression after launch. Renegotiating economics after partner selection is expensive.
Compliance requirements surface late
Licensing requirements and sponsor bank constraints that emerge after the model is selected create expensive rework. They should be defined at the architecture stage.
Start With the Right Architecture.
Most embedded finance programs don't fail because of technology. They fail because the system was never designed correctly. Start with architecture.