Skip to content
Case Study · Digital Banking · Saudi Arabia
D360 Bank

Compliance-Grade, Riyadh-Tested

D360 Bank — a Shariah-compliant digital bank in Riyadh — needed its mobile banking app's customer-contact stack rebuilt to Saudi Central Bank standards. NDS developers joined the build in a team-extension model, in partnership with INCAT: engineers integrated into the client's help-desk engineering team, working to a regulator's rulebook, not just a product backlog.

Staff a Regulated Build See what was rebuilt
Team extension into the client's engineering org
SAMA — Saudi Central Bank compliance delivered
Active client reference available

Delivered in partnership with INCAT · client reference: Piotr Hanusiak, CEO, INCAT.

The engagement

A Contact Module With a Regulator Watching

The unglamorous part of a digital bank is where compliance lives. Three problems defined the brief:

Regulation first

The help and contact module had to meet Saudi Central Bank requirements — national rules, not generic best practice.

A chat that couldn't operate

No session reporting, no way to close sessions, every chat opening a new dispute — support couldn't run a bank on it.

Integration edge cases

External-provider requirements down to the sharp details — including correctly blocking Apple Pay payments where required.

What was delivered

Rebuilt, Not Patched

1 · The redesignThe full contact stack

chat, messaging, bank-representative requests, feedback and contact evaluation — redesigned as one coherent module

2 · The disciplineStability over bloat

solutions designed to avoid overloading the app — reusable, maintainable, regulator-ready

3 · The outcomeCompliance met

Saudi Central Bank requirements satisfied; contact processes measurably streamlined

4 · The bonusTech debt out

early error detection at lower cost — and the legacy debt in the banking app eliminated along the way

What the client said

Chosen as a Long-Term Partner

Client testimonial · as published

"We were looking for a long-term IT partner. Our decision factors were: quick delivery time, experience, flexibility, and communication skills. We see a real value in our cooperation."

— Head of Channels Engineering

The wider Gulf story

Why This Case Travels

Riyadh engagements are run in person — leadership visits monthly — and the same regulated-delivery screening runs across our banking work:

Banking · Poland & Gulf

The banking bench

Core banking platform experience — Temenos, Mambu, Asseco, Finastra, FIS — screened for regulated-environment delivery.

Read the core banking page →
AI · Regulated

AI engineering for banks

GenAI engineers screened for production track record in environments where a model's mistake is a compliance event.

Read the AI engineering page →
Proof hub

All case studies

Every case with real numbers and an explicit naming decision — named, via partner, or anonymized.

Open the hub →
Let's talk

Building Under a Regulator's Eye?

Banking, fintech, GCC compliance — tell us the stack and the rulebook. First CVs in 48 hours, screened for regulated delivery.

Book a Discovery Call — First CVs in 48h
Talk to us

Two Ways to Start

Put a slot in a calendar, or send the brief and we will come back to you. Either way you are talking to a partner, not a queue.

Book a call

Thirty minutes, no deck. Whoever's calendar suits you — they take the call themselves.

Michał Stawski
Managing Partner
Book 30 min →
Bartłomiej Lewandowski
Managing Partner
Book 30 min →

Send a message

Roles, platform, headcount, timeline. A link to a brief is even better.

Goes straight to the partners' inbox. No newsletter, no sequence.