Industries
Financial software that passes the audit before it ships.
Banks and fintechs in the Kingdom work under SAMA frameworks, tight security reviews and customers who expect a banking app to feel as fast as a messaging app. We build the integrations, wallets and apps that sit between your core systems and your customers, with the controls documented from the first sprint.
What this removes.
Core banking systems that do not talk to anything new
Today
Every new product needs a custom bridge into a core platform that was designed long before open APIs, so launches wait on one overloaded integration team.
With the system
A clean API layer in front of the core. New products plug into it instead of into the core itself.
Security reviews that restart the project
Today
Penetration findings and control gaps surface at the end, and a build that looked finished goes back for weeks of rework.
With the system
Controls mapped to your security framework from sprint one, with evidence collected as we build rather than assembled afterwards.
Payment journeys that lose customers at the last step
Today
Card, mada and wallet flows are stitched together by different vendors, and a failed callback leaves the customer unsure whether they paid.
With the system
One payment orchestration layer with clear states, retries and reconciliation, so every transaction ends in a known outcome.
Apps that treat Arabic as an afterthought
Today
Mirrored layouts break, numerals mix, and statements print with text running the wrong way.
With the system
Arabic and English designed together, right to left from the first wireframe.
What actually applies.
SAMA Open Banking Framework
SAMA has published an open-banking framework that defines how licensed parties exchange account information and initiate payments through standardised APIs, with customer consent at the centre. We build integrations aligned with its consent, data-sharing and API-design expectations. Licensing itself stays between you and SAMA.
SAMA Cyber Security Framework
Regulated financial institutions are expected to meet SAMA's cybersecurity framework across governance, operations and third-party risk. For any software we deliver, we map design and testing to the relevant domains, document the controls and support your internal assessment. We do not certify anything on SAMA's behalf.
Personal data and PDPL
Account and transaction data is personal data under the Personal Data Protection Law. Consent records, retention rules and data-subject requests are designed into the schema, not added later.
Delivered through these services.
Asked before signing.
Can you build to SAMA requirements, and do you hold a SAMA licence?
We are a software partner, not a licensed institution. We build to the requirements of the SAMA frameworks that apply to you and document the controls, while licences and regulatory approvals remain yours to obtain from SAMA.
How long does a payment or open-banking integration take?
A single payment gateway integration with reconciliation typically takes 4 to 8 weeks. An open-banking API layer with consent flows and testing usually runs 10 to 16 weeks, depending on how many core systems sit behind it.
Where will the system be hosted?
Financial data usually has to stay inside the Kingdom. We design for in-Kingdom hosting, either in your own environment or with a local cloud region you choose, and we confirm residency before build starts.
Do we own the source code?
Yes. Code, infrastructure definitions and documentation are handed over under your ownership at each release, so your security team can review it and another vendor could take over if you ever chose that.
Bring us the integration that is stuck in review.
Send us the architecture diagram and the security findings. In one working session we will tell you what to change, what to keep and how long the rest should take.