BaaS partner program launch: bank as infrastructure for marketplaces
Anonymised engagement: bank launched BaaS program with 3 retail partners (telecom, marketplace, ride-hailing). 12 months, scaled revenue stream.
Context
Mid-size commercial bank UZ with established license. Telecom operators and marketplaces requesting embedded finance integrations. Existing partnerships ad-hoc, each one a custom build.
CEO ambitious — make BaaS a strategic priority.
Diagnostic (5 weeks)
Internal capability: data engineering capable, but no API platform.
Regulatory: cbu.uz framework ambiguous but not blocking.
Partner inventory: 12 potential partners identified, 3 priority (large telecom, e-commerce platform, ride-hailing).
Technology stack: legacy ABS, an API/event layer needed above.
Approach (12 months)
Months 1-3. Architecture + regulator engagement. API platform design, cbu.uz consultation for BaaS framework clarity.
Months 3-6. Foundation build. API gateway, developer portal, sandbox, OAuth, monitoring, compliance layer.
Months 6-9. Pilot partner onboarding. Telecom first — wallet integration. Detailed contract, sandbox testing, gradual rollout.
Months 9-12. Expansion. Marketplace (split payments) and ride-hailing (driver wallets) onboarded.
Results
After 12 months:
- 3 active BaaS partners with production traffic.
- Combined transaction volume: 2.5M monthly transactions through partners.
- Revenue stream: $1.2M annualised — small initially, but high margin (>60%).
- Net new customers through partners: 48k (operator’s customer touchpoints).
- cbu.uz BaaS framework clarification — bank as preferred provider.
- Technology platform reusable for 5+ additional partner prospects.
What is critical
Regulator engagement before partner activation — framework clarity.
Sandbox-first partner onboarding — testing without production risk.
Strict contract terms on partner side — risk management.
Reusable platform — each new partner cheaper to onboard.
Related
- /en/solutions/banking-embedded-finance-platform/ — BaaS solution
- /en/architecture/banking-partner-api-platform/ — partner API
- /en/decisions/banking-baas-vs-direct/ — BaaS decision
- /en/insights/banking-platform-economics/ — platform economics
Similar challenge?
Tell me what's going on. I'll review the situation and suggest a concrete path forward.
Usually respond within a few hours