Add Bank Connectivityto Your Platform
Lean (GCC) and Finverse (APAC) bank connectivity, normalised to one schema. Embed the Link SDK, ingest real bank data, and build the financial features your users need — without building the rails.
GCC / MENA
APAC
Add Bank Connectivity to Your Platform
Lean (GCC) and Finverse (APAC) bank connectivity, normalised to one schema. Embed the Link SDK, ingest real bank data, and build the financial features your users need — without building the rails.
GCC / MENA
APAC
Why TradeSocio Open Banking?
Building directly on Lean or Finverse means two integrations, two schemas, and two maintenance surfaces. One abstraction layer covers both — and a third rail is an adapter, not a rewrite.
One Schema, Multiple Rails
Provider-Agnostic Abstraction
Lean and Finverse are normalised into a single data model: bank_connections, bank_accounts, bank_transactions. Every downstream feature — analytics, AI narration, health scoring — is written once and works for both. Adding Plaid is an adapter, not a rebuild.
GCC + APAC in One Product
Two High-Growth Markets
Lean covers UAE, KSA, and the wider MENA Gulf. Finverse covers 220+ institutions in Singapore, Hong Kong, and APAC. A single user with accounts across both regions — the expat profile — is handled natively, without two separate integrations.
Read-Only, Consent-Native
AIS — No Payment Initiation
This is Account Information Services: read access granted through a regulated, revocable consent. The user authenticates directly with their bank — credentials never reach your servers. You receive structured data, not liability.
AI-Ready by Design
Pre-Structured for LLMs
Transactions arrive pre-categorised (rules + AI hybrid). The wealth engine computes financial health scores, debt payoff sequences, and investable surplus deterministically before any LLM narration. The numbers are auditable; the AI narrates.
Continuous, Not Batch
Sync Refreshes Everything
Every sync refreshes the complete financial picture without re-asking the user anything. AIS consent is long-lived; the platform stays current between sessions, enabling proactive triggers rather than point-in-time snapshots.
Proven in Production
Live Across GCC and APAC
The rails are deployed and validated end-to-end inside InvestWhat — real bank connections, live categorisation, and AI wealth analysis running daily. Not a proof-of-concept.
How It Works
Embed Once. Real Bank Data Flows.
From SDK embed to normalised data ready for your product — four steps, no credentials on your servers, no schema work on your side.
Embed the Link SDK
Drop the Lean or Finverse Link component into your app. The SDK handles the institution picker, authentication redirect, and consent grant — fully hosted by the provider.
User Authenticates with Their Bank
The user selects their institution and authenticates directly with their bank. No credentials touch your servers. The bank issues a consent token scoped to read-only AIS.
Data Flows into a Unified Schema
Accounts, balances, transaction history, and identity arrive normalised into one schema, tagged by provider. Your app receives the same structure regardless of which rail or institution the user chose.
Your Platform Builds on It
Run the AI wealth analysis, surface net worth, categorise spending, detect investable surplus, or power your own financial features — all on a continuously refreshing, first-party-quality data layer.
What You Get
Six Data Modules. One Normalised Schema.
Accounts, transactions, identity, health scoring, investable surplus, and net worth — all computed from real bank data and ready for your product layer.
Accounts & Balances
Current · savings · credit · FX
All account types — current, savings, credit, investment, FX, and (increasingly) crypto accounts — with live balances and account metadata across every connected institution.
All account types — current, savings, credit, investment, FX, and (increasingly) crypto accounts — with live balances and account metadata across every connected institution.
Full transaction history with automatic categorisation using a hybrid rules and AI categoriser. Recurring charge detection, income vs. transfer classification, and merchant-level tagging are applied on ingest.
KYC-grade identity fields — name, contact details, and national ID — delivered structured and verified by the bank. Replaces manual onboarding forms and provides a documented, bank-verified source of truth.
A deterministic health score built from real pillars: savings rate, emergency-fund coverage, credit utilisation, debt load, and cash flow. Honest by design — capped under revolving debt or negative cash flow rather than flattering the user.
The realistic monthly amount a user can invest after debt servicing and emergency fund, with a real (inflation- and fee-adjusted) long-term projection. Quantified, sequenced, and ready to convert into an advised portfolio.
A unified net worth across all connected accounts and regions. FX normalisation to a per-user base currency is in progress — the platform withholds cross-currency aggregates until conversion is reliable rather than summing different currencies blindly.
One Abstraction, Three Rails
Lean and Finverse are live today. Plaid expands the same layer to US and EU — no schema changes, no integration work.
Roadmap
What's Next
The GCC and APAC rails are live. These build on the same abstraction layer.
FX normalisation
SoonPer-user base-currency conversion across all linked accounts, unlocking trustworthy cross-region net worth and the full multi-bank picture.
Richer categorisation
SoonHousing, insurance, and loan minimums added as distinct categories so needs-based metrics — especially the emergency fund calculation — are exact.
Plaid — US / EU rail
SoonThird provider built on the same abstraction layer. Incremental on the existing schema: existing features work on day one with no rewrites.
Advisor console
SoonClient list, proactive triggers, and the suitability evidence trail packaged for advisory workflows. Later: payment initiation for funding flows.
Bruno Brokerage Suite
Part of the Bruno Brokerage Suite
Bruno Core
Client-Facing Trading Platform
Modern, mobile-first trading platform for your clients. Web, iOS, Android, and desktop from a single codebase.
Bruno OMS
Execution Engine
Institutional-grade order management with FIX connectivity, dealer desk, and smart routing. 10,000+ orders/sec.
Bruno Admin
Back-Office Operations
90+ modules for client management, compliance, finance, IB networks, and reporting. Included with Bruno Core.
Open Banking FAQ
What is TradeSocio's Open Banking module?
TradeSocio's Open Banking module is a provider-agnostic bank connectivity layer that normalises Lean (GCC/MENA) and Finverse (APAC) into a single data schema. Fintechs and brokers embed the Link SDK once and get real bank data — accounts, balances, transactions, and identity — without building or maintaining the provider integrations themselves.
Which regions and providers are covered?
Lean Technologies covers the GCC and wider MENA market (UAE, KSA, and others). Finverse covers 220+ institutions across APAC, with strong coverage in Singapore (DBS, OCBC, UOB) and Hong Kong. Plaid, which covers the US and EU, is on the roadmap as a third rail — incremental on the existing abstraction layer.
Is this Account Information Services (AIS) only, or does it include payment initiation?
The current implementation is AIS only: read access to accounts, balances, transactions, and identity. We use the consent-and-read slice of Open Banking. Payment Initiation Services (PIS) for funding flows is on the roadmap as a later capability.
How is user data kept secure?
The user authenticates directly with their own bank — credentials never reach your servers or ours. We receive structured data under a bank-issued, scoped, revocable consent token. AIS access is read-only by definition; no funds can be moved through an AIS integration.
What data does the integration provide?
Six normalised data modules: accounts and balances (all account types), full transaction history with automatic categorisation, KYC-grade identity, a deterministic financial health score, an investable surplus calculation with a real-terms projection, and a net-worth view across all linked accounts. FX normalisation to a per-user base currency is in progress.
How do you handle multiple currencies and cross-region accounts?
The platform stores balances in their native currencies and tags each record by provider and region. We withhold cross-currency aggregates until FX normalisation is reliable — so a user with both UAE dirhams and Singapore dollars will not see a misleadingly summed net worth until the conversion layer is production-grade. That work is the immediate next roadmap item.
We already have Lean or Finverse in-house. Is there still value in this layer?
If you have one provider live, this layer adds the second rail, the normalised schema, and all the computed outputs (health score, surplus engine, categorisation) without you building them. If you intend to add Plaid later, the abstraction means you never revisit the data model. The value scales with how many downstream features — analytics, AI narration, advisory tools — you want to build on top.