Gulf · EU · US

Payment rails, banking APIs,
and the rules around them.

A working reference for the payment infrastructure of three markets — how the APIs behave in code, and what the regulation actually requires. Written from integrations that shipped, not press releases.

Integration guides0 piecesHow these APIs behave once you leave the sandbox — auth flows, webhooks, idempotency, and the failure modes the vendor docs skip. Every guide ships runnable .NET code.Browse guides →Market analysis2 piecesWhat the rules actually require and what the market actually charges — open banking frameworks, scheme mandates and gateway economics across the Gulf, EU and US.Browse analysis →

Latest

Newest across both sections

AnalysisGlobal

FAPI 2.0: what compliance actually requires you to build

The MUST-level requirements of the FAPI 2.0 Security Profile, and which of your existing OAuth assumptions each one breaks.

27 July 20264 min read

AnalysisUAE

UAE open finance pricing: what the API Hub actually costs

The published UAE fee schedule, the page allowances on data sharing, and the pricing rules that quietly constrain how you build.

27 July 20266 min read

Payment rails, banking APIs, and the rules around them.

Latest

FAPI 2.0: what compliance actually requires you to build

UAE open finance pricing: what the API Hub actually costs

Payment rails, banking APIs,
and the rules around them.