The UX of Consent Models in Open Banking

Key Takeaways for UAE Implementation

The article outlines the OBIE (Open Banking Implementation Entity) three-stage consent model, which provides a useful framework for Al Tareq implementations:

The Three Stages

1. Consent Stage - The TPP explains what data is needed and why
2. Authentication Stage - The bank verifies customer identity
3. Authorisation Stage - The customer approves specific data sharing

Relevance to UAE

While the UK model differs from UAE’s centralized Nebras infrastructure, the UX principles remain applicable:

• Clear data scope communication - Customers must understand exactly what they’re sharing
• Familiar authentication patterns - Banks should use consistent login experiences
• Explicit authorization confirmation - The final step reinforces customer control

Design Principles Worth Adopting

The article emphasizes several principles that align with CBUAE’s customer protection focus:

• Make consent time-bound to reinforce customer control
• Create visual distinction between TPP and bank flows
• Use positive friction at key decision points
• Provide clear revocation paths

How This Applies to Al Tareq

When building on the Al Tareq platform, consider:

1. Pre-consent education - Help users understand Open Finance before the flow begins
2. Consent duration visibility - Make the 90-day consent window clear
3. Account selection UX - Allow granular control when multiple accounts exist
4. Post-consent confirmation - Summarize what was shared and for how long

Further Reading

This reference pairs well with:

• CBUAE Open Finance customer consent guidelines
• Al Tareq consent API specifications
• FDX (Financial Data Exchange) consent receipt standards