SECTOR / 01 Industry

Banking, SAMA-aligned by default.

From core-modernization to fraud detection to Open Banking integration — engineered for SAMA-licensed entities, where compliance is the floor and speed is the differentiator. We've sat on both sides of the regulator's desk.

SAMA-licensed clients
12banks & fintechs
Active programs
23
Avg. SAMA CSF uplift
+1.4maturity
Fraud detection lift
3.6×vs. baseline
المصرفيةBANKING & FINTECH · KSA
REGULATORSAMA
DATA RESIDENCYIn-Kingdom mandated
OPEN BANKINGSAMA OBF live
VISION 2030 TARGET70% non-cash by 2030
01 / The brief

What banking actually feels like in the Kingdom.

Six pressures we hear from CFOs, CTOs, and Heads of Risk on every first call.

01 /

SAMA velocity

The regulator publishes new circulars on a quarterly cadence — Open Banking, Cyber, Counter-Fraud, ESG — and expects implementation, not interpretation. Compliance is no longer an annual exercise.

→ Counter-Fraud · OBF · CSF v1.1
02 /

Core legacy

Most tier-1 banks still run cores from the late 90s. Modernization without a "big bang" — strangler patterns, event sourcing, side-by-side ledgers — is the only realistic path forward.

→ Strangler · Event-sourced
03 /

Real-time fraud

Cards, instant payments, e-wallets, and Open Banking AISP/PISP create attack surface in places risk teams haven't historically watched. Detection has to land in milliseconds — not overnight batch.

→ Sub-300ms decisions
04 /

Open Banking integration

SAMA's OBF is live. AISP and PISP onboarding requires standardized APIs, FAPI-compliant security, and consent management most cores were never designed to support.

→ FAPI · CIBA · OBF
05 /

Talent scarcity

The Kingdom is producing world-class talent fast — but demand outpaces supply. Saudization targets and the AI/data stack arms race are pulling from the same shallow pool.

→ Saudization · Build-to-transfer
06 /

Customer expectations

Saudi consumers compare banking apps against TikTok and STC Pay, not against other banks. UX latency, Arabic NLU, and instant onboarding are the new table stakes.

→ Bilingual-first
02 / Service mapping

How our six service lines land in banking.

Same disciplines, sector-tuned. Each service rebuilt around SAMA's specific posture and the operational shape of a regulated bank.

03 / Flagship deployments

Where it has actually shipped.

Two engagements that anchor our banking practice. Names redacted under MNDA — the regulators know the work.

CASE / 01 · TIER-1 BANK

Real-time fraud platform

Tier-1 retail bank · 12M+ accounts · live since Q3 2025

Replaced a nightly-batch fraud engine with a stream-native platform: ~8K transactions/sec at peak, sub-300ms decisions, and a feature store shared across cards, transfers, and Open Banking flows. SAMA Counter-Fraud submission accepted on first review.

3.6×FRAUD CAUGHT
−42%FALSE POSITIVES
280msP95 DECISION
SAR 91MRUN-RATE LOSS AVERTED
CASE / 02 · DIGITAL FINTECH

Open-banking-native onboarding

SAMA-licensed digital fintech · launch program · Q1 2026

Greenfield onboarding flow built on SAMA OBF: AISP-pulled income verification, automated KYC with vision-based document forensics, and an Arabic-first conversational journey that compresses median onboarding from 11 minutes to 92 seconds.

92sMEDIAN ONBOARDING
97%STRAIGHT-THROUGH
0SAMA FINDINGS
4.8★APP STORE
04 / Compliance posture

The frameworks we operate inside.

SAMA CSF v1.1
SAMA Counter-Fraud
SAMA OBF
SAMA Cyber Threat Intel
SAMA BCP
PDPL
NDMO Classification
PCI-DSS v4
ISO 27001
FAPI 2.0
SWIFT CSP
ISO 20022
05 / Ecosystem

Who we work alongside.

Hyperscalers, core providers, regulator-blessed partners. We are vendor-honest and integrate the stack you've already chosen.

HyperscalerAWS Bahrain
HyperscalerAzure UAE
HyperscalerGoogle Dammam
Sovereignstc cloud
CoreTemenos
CoreFinacle
Paymentsmada
Open BankingSAMA OBF
06 / FAQ

Common questions.

Are you on SAMA's vendor list?

Yes — we are registered as a technology service provider with multiple SAMA-licensed entities and have been through SAMA outsourcing reviews on four engagements to date.

How do you handle data residency?

All client data stays in-Kingdom. We deploy to AWS Bahrain, Azure UAE-North, Google Dammam, or sovereign on-prem depending on the client's posture. Cross-border data transfer is documented in every engagement and approved per PDPL.

Can you help with SAMA submissions?

Yes. We've drafted, defended, and revised submissions for CSF self-assessment, Counter-Fraud frameworks, and OBF accreditation. Our compliance team includes ex-SAMA practitioners.

Do you replace our existing core?

Almost never. We extend it. Strangler patterns, event-sourced ledgers, and side-by-side modernization deliver outcomes faster and de-risk the path. Full replacement is a last resort, not a default.

What's the typical engagement size?

From a six-week SAMA gap study to a multi-year platform program. Median bank engagement runs 7–11 months with a blended team of 8–14, with a heavy onshore Saudi component.

How do you work with internal IT?

Build-to-transfer is the default. Co-located squads, joint roadmaps, and a deliberate runway to stand the platform up inside your team. We measure success on transition, not on year-five retainer fees.

SAMA-fluent from day one.

نتحدث لغة الجهة التنظيمية.

Sixty-minute working session with our Banking lead. Bring the latest SAMA findings, the fraud KPI you wish was lower, or the OBF deadline you're chasing. We'll come back with a one-page roadmap.