BaaS vs direct customer relationship: a decision frame

When the fork appears

Bank with established license thinks: monetise license via BaaS partnerships (telecom, marketplace, retailer want embedded finance), or keep direct customer relationships, protecting brand and data.

Frame criteria

Brand strategy. If ambition is to remain consumer-facing brand — direct better. BaaS dilutes.

Customer acquisition cost. Direct — high CAC, growth slow. BaaS — partner does acquisition, but margin shared.

Data ownership. Direct — full data. BaaS — partial (transactional but not behavioural).

Regulatory comfort. BaaS introduces partner risk — partner missteps reflect on the bank.

Capital efficiency. BaaS scales license without proportional balance sheet growth.

When BaaS

Bank with unused license capacity.

Strong technology stack — APIfication possible.

Limited consumer brand traction.

Fintech-driven market — partners available.

Regulator supportive of BaaS framework.

When direct

Strong consumer brand with loyalty.

Data strategic — ownership needed for AI / scoring.

Risk appetite low — BaaS partner risk too high.

Capital strong — direct growth feasible.

When hybrid

Direct for retail / SME (own brand).

BaaS for niche (e.g. FX via trade marketplace, lending via retailer).

Most banks settle on hybrid.

Where decisions usually go wrong

BaaS for quick revenue without strategy. Three years later partner consolidates customer relationship, bank becomes infrastructure.

Direct only without partnership tech. Five years later fintech competitors via BaaS partners overtake reach.

Related

• /en/solutions/banking-embedded-finance-platform/ — BaaS solution
• /en/architecture/banking-partner-api-platform/ — partner API
• /en/insights/banking-platform-economics/ — platform economics
• /en/insights/banking-brand-positioning/ — brand