SADAD Payments in Saudi Arabia (2026): How It Works for Businesses

What SADAD Actually Is

SADAD is the national electronic bill presentment and payment system for Saudi Arabia. It is owned by the Saudi Central Bank, and it sits alongside mada and sarie as one of the three rails that most money in the Kingdom eventually touches.

It is worth being blunt about the category, because SADAD gets described wrongly more often than almost any piece of Saudi financial infrastructure. It is not a payment gateway. It is not a wallet. It is not a card scheme, and it does not compete with mada. It is a clearing layer for bills: an entity that is owed money registers once, publishes what is owed, and every bank in the country can then present and collect that amount through its own channels without a bilateral integration.

On the founding date, the public record genuinely disagrees and we are not going to pretend otherwise. SAMA's own system page states that SADAD was launched in 2004. The English Wikipedia entry, and several write-ups that follow it, give a launch of 7 June 2007. The most plausible reading is that 2004 marks the establishment of the project and 2007 the live go-date, but no source we found states that reconciliation explicitly, so treat any single year you see quoted with mild suspicion.

The same caution applies to the size numbers. Wikipedia enumerates roughly 151 registered entities across telecom, government, education, finance and transport. Industry analyses put the figure above 300. At least one practitioner guide claims more than 600. SAMA does not publish a live public count that we could locate, so the honest answer in 2026 is somewhere in the hundreds and growing, and anyone quoting a precise figure is quoting somebody else.

How a SADAD Payment Actually Moves

The flow matters more than the branding, because it explains every constraint you will run into later: why settlement is not instant, why refunds are awkward, and why nobody can quote you a fee.

SADAD is a hub-and-spoke design. Before it existed, a utility that wanted its customers to pay through their banks had to build and maintain a connection to each bank individually, and most bills were still settled in cash at a branch counter. SADAD replaced that mesh with one connection each: the biller integrates with SADAD, every bank integrates with SADAD, and the combinatorial problem disappears.

The consequence that catches finance teams out is in the gap between steps four and six. Your customer's account is debited in seconds and their receipt says paid. Your bank balance does not change until the following settlement cycle. If your operations team releases goods on the strength of a customer screenshot, you are extending credit for a day whether you meant to or not.

The upside of the same architecture is coverage that no commercial provider can match. SAMA lists ATMs, internet banking, telephone banking, mobile applications, points of sale and licensed digital wallets as SADAD channels. You do not integrate with any of them. You integrate once, and your bill becomes payable from a banking app your customer already has and already trusts.

Two Different Things Are Called SADAD

Most confusion about SADAD comes from the fact that the name covers more than one product, and the two behave nothing alike from a merchant's point of view.

The first and by far the largest is the bill service: the biller code and reference model described above, built for obligations that already exist. It is asynchronous by design. You publish an amount, and the payer settles it whenever they get around to opening their banking app. There is no checkout, no session and no conversion funnel.

The second is the SADAD Account, which SAMA's rulebook describes as a service provided through the SADAD payments system to develop e-commerce in the Kingdom. It is a non-card, account-to-account method: the consumer's bank account is debited and the merchant credited, without a card scheme in the middle. A related online payment capability has been described by banks as a real-time debit for online merchants. If you have ever seen SADAD offered as a checkout option next to mada and Apple Pay, this is the family of services you were looking at, not the bill rail. SAMA has also had to intervene here: a circular directs banks to treat a SADAD Account according to the status of the customer's main current account, because some banks were freezing SADAD Accounts independently while the underlying account remained perfectly active.

How a Business Becomes a Biller

This is the question we get asked most and the one with the least published documentation, so here is what can actually be established, and where the trail goes cold.

SADAD is not self-serve. There is no signup page where you enter a commercial registration number and receive a biller code. Onboarding runs through a sponsoring bank, which holds the relationship and the collection account, or through a payment service provider that already holds biller status and can expose SADAD to you as a method. In practice you start the conversation with your corporate bank, not with SADAD.

What you will be asked for follows the shape of any regulated Saudi onboarding: a valid commercial registration, your entity and ownership documentation, a corporate account with the sponsoring bank, and a description of the billing use case and expected volumes. Beyond that, we are not going to invent a checklist. SAMA and SADAD do not publish a public biller application form, a documentation list or a service level for approval, and every timeline circulating online is somebody's anecdote. If a consultant quotes you a fixed number of weeks, ask them which published document it comes from.

The SADAD Number: Biller Code Plus Reference

Everything your customer touches comes down to two identifiers, and getting the second one right is entirely your problem.

The biller code identifies the organisation. It is issued to you once, it is numeric, and it is what your customer selects from the biller list in their banking channel. The reference number identifies the specific obligation: an account, a subscriber, a case, or a single invoice. Customer-facing communications often merge the two into what people casually call a SADAD number, which is why support calls about it are so confusing.

The design decision that will cost or save you the most is what your reference number represents. Bind it to a customer account and the same reference is reused forever, which is friendly for recurring utility-style billing but useless for matching a specific invoice. Bind it to an individual invoice and reconciliation becomes trivial, but your customer has to fetch a fresh number every time. Neither is wrong. Choosing without thinking about your reconciliation process is.

One warning that is not really about SADAD at all. A SADAD reference is a payment identifier, not a tax document. It has nothing to do with ZATCA Phase 2, which governs how your invoice is generated, cryptographically stamped and cleared through the Fatoora platform. We have watched businesses assume that because a payment cleared through a national system, the invoicing side was somehow handled. It is not. The two obligations are separate and you owe both.

Settlement, Reconciliation and Refunds

For a finance team, this section is the whole article. SADAD behaves like a batch clearing system, because that is what it is.

At the end-of-day cut-off, SADAD assembles a clearing file, calculates multilateral net settlement positions across participating banks and billers, and submits those positions to SARIE, the Kingdom's interbank settlement system, for the next settlement cycle. The practical effect for a biller is next business day availability of funds in the normal case. Weekends and Saudi public holidays extend it, and a Thursday evening payment is not a Friday morning balance.

Alongside settlement, billers receive daily reconciliation reports breaking down every transaction SADAD processed on their behalf. SAMA also describes refund processing on paid invoices, automatic payment notifications, invoice status updates and an electronic portal for tracking transactions and managing disputes. Note the word processing rather than instant: a SADAD refund is a workflow you initiate through your biller relationship, not a one-click reversal like a card refund, and you should size your customer service expectations accordingly.

Where SADAD Falls Short

SADAD is excellent infrastructure aimed at a specific job. Most of the complaints we hear come from businesses trying to use it for a different one.

Fees and Limits: What Is Actually Published

We went looking for a SADAD fee schedule for billers. There is not one. Here is exactly what we could and could not establish, with the sourcing stated so you can weigh it yourself.

The absence of a published rate card is not sloppiness. SADAD is national infrastructure, and its commercial layer deliberately lives with the banks. That is defensible policy and genuinely inconvenient for a business trying to build a payment cost model in a spreadsheet before committing.

The practical move is to make the bank compete on the same terms you would make a gateway compete. Ask for the per-transaction biller fee in writing, whether it is flat or tiered by bill value, what the setup cost is, what the settlement cut-off actually is, and what a refund costs you operationally. Get all five in the proposal, because none of them will be on a website.

On limits, the same discipline applies. Any per-transaction ceiling you encounter is far more likely to come from your customer's own bank channel policy than from SADAD itself, and it will differ between an ATM, a mobile app and a branch. If large single payments are core to your model, test them on the actual channels your customers use before you promise anything.

How to Accept SADAD: Four Routes

There is more than one door. Which one you should walk through depends almost entirely on your billing volume and whether you have engineering capacity to spend.

Frequently Asked Questions