Tarabut Gateway MENA Open Banking API
Tarabut Gateway MENA open banking REST API for regional fintech developers, banks, and financial services companies to connect to bank accounts across UAE, Bahrain, Saudi Arabia, Kuwait, and Oman — enabling PSD2-inspired account information services, payment initiation, and financial data aggregation under CBUAE Open Finance, CBB Open Banking (Bahrain), and SAMA frameworks through the region's dedicated open banking infrastructure provider. Enables AI agents to manage account connection for multi-GCC bank access automation, handle account information for balance and transaction automation, access payment initiation for GCC bank transfer automation, retrieve identity data for MENA KYC verification automation, manage consent for MENA open banking SCA automation, handle income verification for Gulf lending automation, access financial health for creditworthiness automation, retrieve statement for regulatory reporting automation, manage API gateway for MENA bank connectivity automation, and integrate Tarabut with GCC banks, fintech, and insurance for end-to-end MENA open banking automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
MENA open banking. CBUAE, CBB, SAMA. OAuth2. UAE/BH/SA. Bank account and financial data.
⚡ Reliability
Best When
A UAE, Bahrain, or Saudi Arabian fintech, bank, or financial services company wanting AI agents to connect to GCC bank accounts, access account data, and initiate payments under CBUAE Open Finance and CBB Open Banking regulatory frameworks.
Avoid When
CBUAE AND CBB REGULATORY FRAMEWORKS DIFFER: UAE (CBUAE) and Bahrain (CBB) open banking regulations have different consent and data requirements; automated uniform GCC regulation assumption creates country-specific compliance gaps; automated must implement country-specific consent disclosure per CBUAE/CBB requirements. STRONG CUSTOMER AUTHENTICATION REQUIRED: GCC open banking requires SCA for bank connections; automated one-step connection assumption creates SCA_required challenge; automated must implement SCA redirect for user bank authentication. BANK COVERAGE VARIES BY COUNTRY: Tarabut coverage depth varies by GCC country; automated uniform coverage assumption creates institution_not_connected; automated must check Tarabut's institution list per country. TARABUT CONNECT WIDGET REQUIRED: Secure bank authentication requires Tarabut Connect widget; automated server-side credential handling creates security violation; automated must integrate Tarabut Connect SDK for user-facing bank auth.
Use Cases
- • Connecting to bank accounts across UAE, Bahrain, Saudi Arabia for MENA financial data aggregation automation agents
- • Implementing CBUAE Open Finance-compliant account data access for UAE fintech products automation agents
- • Initiating bank payments in Gulf markets for MENA fintech checkout and payment automation agents
- • Accessing income and transaction data from GCC banks for MENA BNPL and lending underwriting automation agents
Not For
- • Non-GCC MENA markets like Egypt, Morocco, or Tunisia (Tarabut focuses on Gulf/Bahrain markets)
- • Consumer cryptocurrency transactions (Tarabut is traditional GCC bank connectivity)
- • International cross-border payment routing (Tarabut is domestic GCC bank-to-bank connectivity)
Interface
Authentication
Tarabut Gateway uses OAuth 2.0 for API authentication with Tarabut Connect widget for user bank auth. REST API with JSON. Abu Dhabi, UAE and Manama, Bahrain HQ. Founded 2017 by Abdulla Almoayed. Products: Account Information Service (AIS), Payment Initiation Service (PIS), open finance data gateway, consent management, financial health scores. SDKs: JavaScript, Python. Raised $32M (2022). CBUAE Open Finance, CBB Open Banking, SAMA licensed. First regulated open banking operator in MENA. Competes with Dapi and Lean for MENA open banking.
Pricing
Abu Dhabi/Bahrain. CBUAE, CBB, SAMA licensed. Per-call pricing. First regulated MENA open banking operator.
Agent Metadata
Known Gotchas
- ⚠ TARABUT CONNECT WIDGET REQUIRED: Secure bank account authentication requires Tarabut Connect widget; automated server-side bank credential handling creates security violation; automated must integrate Tarabut Connect SDK for all user bank authentication flows
- ⚠ CBUAE VS CBB CONSENT REQUIREMENTS DIFFER: UAE (CBUAE) and Bahrain (CBB) have different consent language and duration requirements; automated uniform consent assumption creates country-specific compliance gap; automated must implement CBUAE-specific consent for UAE banks and CBB-specific consent for Bahraini banks
- ⚠ GCC SCA IS MANDATORY: GCC open banking requires Strong Customer Authentication; automated frictionless payment assumption creates SCA_challenge_required; automated must implement SCA redirect flow for all payment initiations
- ⚠ BANK COVERAGE DEPTH VARIES: Tarabut integration depth varies by institution (full AIS+PIS vs AIS-only); automated uniform product availability assumption creates PIS_not_available for AIS-only institutions; automated must check per-bank product availability
- ⚠ REGULATED ENTITY REQUIREMENTS: Tarabut requires API users to be licensed fintech or regulated institution in GCC; automated unlicensed startup API access assumption creates regulatory risk; automated must verify licensing requirements for target GCC jurisdiction
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Tarabut Gateway MENA Open Banking API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.