Mobile App Development in Saudi Arabia — mada Payments, Nafath Sign-In, ZATCA Invoicing
An app that works in Saudi Arabia differs from one built anywhere else in two places the user touches, and a third nobody sees. A buyer in Riyadh or Dammam reaches for a mada card before any other, and expects a sign-in verified against their national identity, the way government platforms have taught them. The third place is what happens after the pay button: if the purchase is taxable, the invoice has a technical shape set by the Zakat, Tax and Customs Authority, and an ordinary PDF will not satisfy it. Snaabble is an Egyptian team based in Talkha, Dakahlia. We have no office inside the Kingdom; we work with our Gulf clients fully remotely, and we settle these requirements in the discovery session before designing a single screen.
Get a quoteWhat is different in Saudi Arabia?
Payment starts with mada, not with international cards
mada, the national payment network, has been owned by the Saudi Central Bank since its launch in 1990, and covers point-of-sale terminals, ATMs and e-commerce sites through a single central switch. The mada e-commerce service runs over the 3-D Secure protocol, which adds a layer that verifies the cardholder's identity, and a mada card can be added to Apple Pay, the mada Pay wallet and the Google and Samsung wallets using tokenisation. In practice that means the payment integration needs a redirect-and-return flow for 3-D Secure, a screen that handles a failed verification, and a test plan covering mada and the wallets rather than international cards alone.
Signing in with the national digital identity: Nafath
The National Single Sign-On portal is developed and operated by the Saudi Data and Artificial Intelligence Authority. The user enters a national ID or residency number, approves the request inside the Nafath app, and reaches government and private-sector services from one entry point. The effect is direct: Saudi users now tell an ordinary account apart from an identity-verified one, and hesitate before entering sensitive details into an app that asks only for a username and password. So we shape the account model from the start so identity verification can be added later without rebuilding the user base.
E-invoicing enters the app the moment it sells
Phase two of e-invoicing began on 1 January 2023 for groups notified at least six months ahead of their wave. A tax invoice is sent as XML to the Fatoora platform through APIs for clearance; the platform adds the cryptographic stamp and the QR code and returns it, and only then may it go to the buyer. A simplified tax invoice is stamped by the invoicing solution itself using a CSID and carries a QR code holding nine tags in TLV format encoded in Base64, then is reported within 24 hours of issuance. A scanned paper invoice is not an e-invoice.
Data protection follows the user, not the server
The Saudi Personal Data Protection Law applies to any processing of personal data taking place in the Kingdom, and explicitly covers residents' data processed by any party outside it. Put plainly: a development team sitting in Egypt does not place the project outside the law. Transferring personal data abroad carries conditions: it must not prejudice national security or vital interests, an adequate level of protection must exist there, and the transfer must be limited to the minimum needed. So we start with an inventory of what the app collects, where it is stored and who can reach it.
The new riyal symbol and your price screens
The Saudi riyal sign was added to the Unicode Standard at code point U+20C1 in version 17.0, released in September 2025. Unicode notes that vendor support for a new character can only begin after it is encoded, and typically takes at least a year, often longer. The consequence is purely practical: an older phone that has not received a font update will show an empty box where the symbol belongs, on the price screen, the order receipt and the payment notification. So we embed a font carrying the symbol inside the app, set a text fallback that appears automatically on devices without it, and test both paths before release.
What we build for you
A store app that takes mada and phone wallets
Catalogue, cart and customer account, with a payment screen that passes through 3-D Secure and handles a decline or a dropped connection mid-redirect, instead of leaving the user at a blank page. We add Apple Pay and Android wallets wherever your gateway supports them, and hand over a test plan covering a mada card, a wallet and an international card, plus a log showing where each unfinished order stopped.
A booking app with upfront payment in riyals
For clinics, centres and salons: an appointment calendar with varying service durations, reminders before the slot, and an upfront payment that cuts no-shows. Prices and refunds are computed in riyals and halalas under fixed rounding rules, with a written cancellation policy shown before payment rather than after, and a desk view where staff see the day and reschedule without touching the payment record.
A subscriptions and recurring-billing app
Renewal cycles, plans, upgrades and prorated adjustments when someone switches plan mid-month, with an invoice issued for every cycle and wired to the Fatoora platform according to its type. We build the invoice log so any invoice can be resent or corrected with a credit note, and a failed report surfaces on the dashboard instead of passing silently into a log file.
A field app for reps and crews
Visits, tasks, collections and reports from the phone, working offline and syncing when the connection returns, a common situation on industrial sites and long intercity routes. Permissions per role, an audit trail showing who changed what and when, and a clear conflict rule for the moment two people edit the same record from two different devices.
An Arabic-first content and learning app
A right-to-left interface with correct Arabic typography and numerals, and a search that handles hamza and taa marbuta the way users actually type them rather than the way the database assumes. Video content, quizzes, progress tracking and subscriptions, with notifications on Kingdom time that respect the hours when a marketing alert should not arrive.
Wiring an existing app to local rails
Already running an app and need a Saudi payment gateway, an invoicing path or identity verification added? We review the existing code and write a report on what can be added without a rewrite and what genuinely deserves rebuilding, then implement the change with its tests and documentation so any team after us can carry it on.
Frequently asked questions
Do you have an office in Saudi Arabia?
No. Snaabble is an Egyptian company based in Talkha, Dakahlia. We hold no branch and no commercial registration inside the Kingdom. We work with our Gulf clients fully remotely: video meetings, staged delivery, and communication in Arabic from Sunday to Thursday between 9am and 5pm. We sign an NDA before starting, and ownership of the source code, designs and documentation passes to you on delivery, written into the contract.
Will the app accept mada cards and Apple Pay?
Yes, provided the gateway you contract with supports them. The mada e-commerce service runs over 3-D Secure, which means the user is redirected to a verification screen and returns, and that path has failure cases whose interface must be designed from the start. Apple Pay and Android wallets rely on tokenisation, and their availability varies between gateways. We help you compare the available gateways before you choose, and the contract stays directly between you and the gateway.
Does my app need to connect to the Fatoora platform?
It depends on whether you are a person subject to the E-Invoicing Regulation and on when your group falls in phase two, since the Authority notifies a target group at least six months in advance. If the app issues your sales invoices, the integration concerns the app and not only your website. In practice we build the invoicing layer separately from the app screens, so it can serve your store, your app and your points of sale from one source instead of three scattered implementations.
Where will our users' data be stored?
That decision is yours, and we lay out the options and what each one implies. What matters is that the Personal Data Protection Law applies to processing residents' data even when it happens outside the Kingdom, and that transferring it abroad is conditional on not prejudicing national security or vital interests, on an adequate level of protection existing there, and on the transfer being limited to the minimum data needed. So we begin with an inventory of the fields the app collects and drop whatever serves no live function.
What drives the cost of an app for the Saudi market?
Four items make the difference in our estimate: how many user roles there are, how deep the payment integration goes and whether it includes wallets and recurring charges, whether the app needs an invoicing layer wired to the Fatoora platform, and whether identity verification is required. We send an initial plan with a time and cost estimate within 24 hours, then hold a 30-minute discovery call, free and with no obligation. We do not publish price lists: the gap between projects is wider than one figure can carry.