Open banking: lead or follow

When the fork appears

Open banking framework in UZ developing — cbu.uz consultations, regional examples (PSD2 EU, India UPI). Bank decides: invest now in API, partnership, capabilities — or wait, do regulatory minimum, watch competitors.

Frame criteria

Strategic ambition. If ambition is platform / infrastructure provider — lead. If retain product-only — follow OK.

Capital availability. Lead requires CapEx (API platform, partner program). Follow minimal.

Competitive landscape. If competitors are leading — follow is risky.

Internal capability. API platform requires engineering capacity.

Regulator timing. If mandates 12 months away — lead for preparation. 36+ months — wait may be OK.

Partnership opportunities. If sees clear partner roadmap — lead delivers value sooner.

When lead

Strategic platform ambition.

Strong engineering team.

Clear partnership opportunities.

Capital available.

Want to shape regulator framework through early engagement.

When follow

Conservative bank.

Limited capital for major investment.

Customer base satisfied with current offering.

Regulator framework still ambiguous.

Hybrid

Build foundational API capabilities (limited initial scope), monitor regulator, scale based on market signals.

Where decisions usually go wrong

Lead without regulatory engagement — direction misaligned.

Follow indefinitely — fall behind permanently.

Lead in scope too broad — capital wasted on unused capability.

Related

• /en/architecture/banking-partner-api-platform/ — partner API
• /en/insights/banking-open-banking-uz/ — open banking UZ
• /en/decisions/banking-baas-vs-direct/ — BaaS decision
• /en/expertise/banking-regulatory-engagement/ — regulator