01Challenge · SAMA regulatory deadlines
The mandate is due and the estate isn't ready
The situation
Open banking releases, instant payments and enforcement orders each land on an integration estate that is already at capacity. Each arrives as its own program, so identity, consent, security and core connectivity are built again every time. The regulator's date does not move.
What we do
We map the requirement to your systems and owners, then deliver it on shared components: FAPI-secured open banking, ISO 20022 payment connectivity and enforcement rules held as configuration. Each later requirement becomes a tested release on the same platform.
What you receive
- Gap assessment and requirement-to-system map with owners
- Architecture blueprint for the shared platform
- Test packs, including security profile conformance
- Runbooks and SLA reporting for go-live
Products involved
- ConsentHubOpen banking platform
- PayConnectPayment integration suite
- EnforceDeskEnforcement for Tanfeeth
- DevGateAPI developer portalEarly access
Typical outcomes
- One platform and one team behind several mandates
- Later requirements ship as tested configuration releases
- Evidence for the regulator ready on request
Typical first step
An executive briefing on the mandate and its date. You leave with a written view of the gaps and the order in which to close them.
Book a briefing