Saudi & GCC Digital, Payment & Compliance Glossary

Apple Pay reached market-share parity with cards in major Saudi retail by 2024, driven by Saudi Arabia's unusually high iPhone share in Riyadh and Jeddah (50%+). Any Saudi consumer app or e-commerce site that omits Apple Pay leaves measurable conversion on the table.

CliQ is Jordan's instant payment system operated by JoPACC under the Central Bank of Jordan. It enables real-time bank-to-bank transfers and is the equivalent of the GCC region's instant-payment standards.

Mada is the unified Saudi national debit card scheme operated by Saudi Payments under SAMA. It is on roughly 95% of Saudi cards and is the default payment rails for any consumer transaction in the Kingdom. Online and in-app integration is non-optional for any Saudi-targeted e-commerce or mobile app.

SADAD is the Saudi national bill payment system operated by SAMA. It remains the primary rails for utilities, government fees, and most B2B billing flows. Most consumer e-commerce skips it; B2B sites do not.

STC Pay is a Saudi mobile wallet operated by stc, with widespread P2P transfer adoption and growing checkout integration. For Saudi consumer apps, STC Pay alongside Mada and Apple Pay covers the dominant payment surface area.

Tabby is one of two dominant Saudi and GCC BNPL providers (the other being Tamara). For higher-value e-commerce carts, Tabby integration measurably lifts conversion by reducing cart abandonment.

Tamara is a Saudi-founded BNPL provider regulated by SAMA. For Saudi-domestic retailers it is often the higher-trust BNPL choice; for cross-GCC retailers Tabby and Tamara are usually offered together.

ZainCash is an Iraqi mobile wallet operated by Zain Iraq. Together with AsiaPay and FastPay, it is one of the dominant payment rails for any Iraq-targeted e-commerce or service app.

Absher is the Saudi Ministry of Interior's e-government services platform. It is the underlying identity layer that Nafath sits on top of, and it provides direct integrations for permits, residency, traffic, and citizen services.

Nafath is the Saudi national digital identity, built on top of Absher, used for citizen-facing apps, government workflows, and increasingly private-sector apps that need verified identity. Integration usually requires formal access approval but is the de-facto SSO for Saudi-citizen apps.

Nusuk is the official Saudi platform for Umrah and tourist visa-linked services. Hajj and Umrah operators typically need to either integrate with Nusuk APIs or mirror its content categories so search and AI assistants resolve correctly.

Tawakkalna evolved from a pandemic-era app into a broader Saudi government super-app for permits, services, and identity verification. Integrations follow published API patterns and require formal access approval from the relevant authority.

The Communications, Space and Technology Commission (CITC; previously CST) is Saudi Arabia's telecom and digital regulator. It publishes much of the market data referenced across Saudi digital strategy (smartphone penetration, 5G coverage) and regulates digital service providers.

PDPL is Saudi Arabia's Personal Data Protection Law, enforced under SDAIA. It requires that personal data of Saudi residents be processed under tier-graded controls, typically with in-Kingdom hosting (STC Cloud, Mobily, hyperscaler Saudi region), Data Processing Agreements with sub-processors, breach notification SLAs, and explicit consent flows.

ZATCA (Zakat, Tax and Customs Authority) is Saudi Arabia's tax authority. Its Phase 2 e-invoicing requirements apply to any in-app or in-cart B2B receipt and most retail e-commerce. Integration is typically via FATOORAH, the ZATCA SDK, or a ZATCA-compliant ERP module.

The Digital Government Authority (DGA) publishes Saudi Arabia's digital government strategy, accessibility standards, and the Saudi National Design System. Government-targeted apps and websites must align with DGA standards.

The National Transformation Program (NTP) is the execution arm of Vision 2030, with KPIs distributed across ministries. Most government digital products map back to specific NTP KPIs, which is why named alignment in vendor pitches matters.

SDAIA is the Saudi Data and AI Authority. It enforces PDPL, publishes responsible-AI guidelines, and operates the National Data Bank. Any Saudi AI deployment that touches personal data sits under SDAIA-aligned engineering practices.

Vision 2030 is Saudi Arabia's national transformation agenda announced in 2016 with sector-specific programmes covering economic diversification, digital transformation, smart cities (NEOM, Qiddiya), and quality-of-life initiatives. Most digital procurement in Saudi traces back to one of its programmes.

Wa'ed is Saudi Aramco's entrepreneurship and venture arm, providing equity investment, debt financing, and accelerator programmes for Saudi tech startups. Together with Misk and Saudi Venture Capital, it is one of the major sources of capital for Vision 2030-aligned tech.

ALLaM is an Arabic-first large language model developed by SDAIA. For Saudi-targeted AI products that need strong Arabic NLP, ALLaM is one of the natural model choices alongside open-source alternatives like Falcon and Jais.

Falcon is an open-source LLM family developed by the Technology Innovation Institute (TII) in Abu Dhabi. It has been one of the leading regional models for English and Arabic and is broadly licensed for commercial use.

Jais is an Arabic-and-English LLM developed by Inception (G42) in partnership with MBZUAI and Cerebras. It has strong Arabic-language performance and is licensed for commercial use under specific terms.

Answer Engine Optimisation (AEO) is the practice of optimising web pages so that AI assistants (ChatGPT, Claude, Perplexity, Google AI Overviews) cite or proposal them when answering user queries. Core practices: schema markup, speakable selectors, entity-led answers, source-cited stats.

The Saudi National Design System is a government-wide design system used across 10++ ministries to standardise digital experiences, accessibility, and bilingual UX. Vendors building for ministry-targeted projects typically need to either consume it or build integrations that reflect it.

SpeakableSpecification is a Schema.org type that flags page sections suitable for voice readout by assistants. Pairing it with structured FAQ and entity-led answer blocks improves both voice-assistant pickup and LLM citation behaviour.