A Qatar store's checkout usually grows by accident: the bank offered one gateway, a salesperson added another, a wallet arrived with a platform update. The result is not a stack but an accumulation. Compose it deliberately. Give QPay and NAPS the job of serving Qatari debit holders, with Himyan as the national card scheme inside that route. Give Sadad the breadth work — gateway, links and invoicing in one platform. Give international cards and wallets the buyers the national rails were never built for. One checkout, four roles, a planned fallback, one view of the money.
The short answer: one stack, four roles — not four competing gateways
Comparison pages rank Qatar gateways as if you must pick a winner. You do not. You are assigning jobs. The bank-led QPay route exists so Qatari debit cards on the national NAPS rails can pay online. Himyan is the national card scheme those rails carry. Sadad is a Qatar Central Bank-licensed local platform that can run the gateway and handle selling away from the checkout — links, invoices, QR and in-person acceptance. International schemes and wallets serve everyone else: visitors, expatriates on foreign-issued cards, and cross-border orders.
First filter: Qatar Central Bank licensing before any feature list
Before comparing features, check one thing: is the provider licensed by the Qatar Central Bank for the activity it is selling you? SADAD's official pages, for example, state it was licensed by the Qatar Central Bank in 2022 — verifiable against the Bank's framework for national payment systems, including NAPS, Himyan and Fawran (checked October 2026).
Apply the same test to every candidate, including your own bank's gateway. Ask for the licence basis in writing, and which legal entity will hold your merchant agreement.
The national rails: what NAPS and Himyan mean at your checkout
NAPS is Qatar's national ATM and payment switch — the rails connecting the country's banks and debit cards. Himyan is the national payment card scheme under that system: its cards are Qatari debit cards, not international scheme cards with a local label.
AlRayan Bank's official Himyan page states the relationship plainly: its Himyan debit card is issued under Qatar's national payment scheme, is accepted at ATMs and points of sale across Qatar, and is accepted by online merchants in Qatar through the QPay payment gateway, with chip, PIN and one-time-password security and contactless use (checked October 2026). That is the whole local architecture: Himyan is the card, NAPS the network underneath it, QPay the online route it travels. Fawran, the Central Bank's instant payment service, sits beside card checkout — relevant for transfers, not a substitute for card acceptance.
QPay's role: the bank-led route your Qatari debit holders already use
Online round-ups contradict each other about QPay — one describes it as a QR-code transfer tool, another as a small-business transfer service. The official sources resolve it. SADAD's own site describes itself as directly integrated with the National ATM & Payment Network, written as "NAPS – QPay", and bank card pages describe online Himyan acceptance through the QPay payment gateway. QPay is the national gateway route for local debit acceptance online.
It is also bank-led: QNB offers QPay as its ecommerce gateway, built around NAPS debit acceptance with one-time-password and PIN authentication. If most buyers are Qatar residents paying from Qatari accounts, this route is not an optional extra — it is how their cards expect to pay.
Sadad's role: local platform breadth — gateway, links and invoicing
Sadad's job in the stack is breadth inside Qatar. On its official about page (checked October 2026), the company describes a platform spanning an online gateway, payment links, online invoicing, QR payments, and POS and SoftPOS acceptance. Its published journey records the Qatar Central Bank licence in 2022, licences from Visa, Mastercard, Himyan and NAPS in 2024, and certification for clearing and settlement from Visa, Mastercard and American Express — also how a local platform can carry international cards without a second provider.
Use that breadth where it belongs. The checkout is one surface; the payment link for a phone order, the invoice a corporate customer pays against, and the shop terminal are others. Running those through one licensed platform means one onboarding and one settlement logic domestically.
International cards and wallets: serving buyers outside the national rails
The national rails serve Qatar-issued debit. They do not serve the tourist buying from a hotel, the expatriate whose account is abroad, or the customer ordering from London on a foreign-issued card. Those buyers pay on the international schemes — Visa, Mastercard and, where your audience justifies it, American Express — and increasingly expect Apple Pay or Google Pay.
Treat this as a separate role, with its own acceptance decision. Confirm which schemes and wallets your agreement enables, in which currencies you can present prices, and how refunds return to a foreign card. Do not assume local-debit strength enables every international method.
Which buyer pays which way: residents, GCC visitors, international orders
Map the roles to buyers first:
| Buyer | First route to offer | Why |
|---|---|---|
| Qatar resident, Qatar-issued debit | QPay route on NAPS, including Himyan cards | The national debit rails their bank issued the card on |
| Qatar resident, credit or premium card | International schemes via your gateway | Scheme cards run on scheme rails, not NAPS |
| GCC visitor in Qatar | International cards and wallets | Their cards were issued outside Qatar's national scheme |
| International online order | International cards and wallets | No access to Qatari debit rails |
| Phone, invoice or in-person sale | Sadad payment link, invoice, QR or POS | The sale never reaches the web checkout |
The table is a design brief: losing the QPay route loses your core resident buyers, while losing a wallet only inconveniences some international ones.
Fallback order: what happens the minute your primary route fails
A stack is designed; an accumulation is discovered — usually when the primary gateway is down on a busy evening. Plan the order in advance. First, offer the same buyer the second route that serves them: a resident whose debit attempt fails should see another local way to pay, such as a payment link or an alternative licensed gateway on the same rails, before an international card they may not hold. Second, degrade visibly — a clear message and a saved basket, never a dead end. Third, name in writing who switches the fallback on.
Diagnosing why a specific transaction declined is a different discipline; on the day, your store needs a rehearsed sequence. Our Qatar country guide covers the wider local setup.
Reconciliation: one view of money across every rail
Four roles can still produce one set of books — but only if reconciliation is designed into the stack, not left as a monthly rescue. Every rail reports differently: settlement files, refund handling and payout timing follow each provider's own logic, which is why accumulated checkouts leave finance teams matching spreadsheets.
Require a single reporting view, or a single export discipline, across all routes: one order identifier from checkout to settlement, refunds traceable to the original rail, and a daily routine that flags mismatches. If a provider cannot show its settlement reporting before you sign, expect a future argument with your accountant.
The stack audit: questions to put to every provider before signing
Put the same questions to every candidate, in writing. Are you licensed by the Qatar Central Bank for this activity, and under which entity? Which rails does your gateway actually carry — NAPS and Himyan for local debit, and which international schemes and wallets? How do refunds work on each rail, and can I see the settlement report format? What is my fallback if your route fails? What are your onboarding requirements — bank account, commercial registration and documentation — stated exactly? And how do you support Arabic checkout and receipts?
Compared side by side, the answers compose most of the stack for you. For the wider build, see our work for Qatar businesses and web development in Qatar, with platform background in our ecommerce work in Dubai and Shopify development pages. On Shopify specifically, our companion guide to setting up Shopify in Qatar with QPay, NAPS and Arabic covers the platform route.
FAQ
Is QPay a gateway, a wallet or a QR payment app?
QPay is the national gateway route for local debit acceptance online. Official bank and gateway sources describe Himyan cards as accepted by online merchants in Qatar through the QPay payment gateway, and the national switch is written as NAPS – QPay. Descriptions of QPay as a standalone QR transfer app come from secondary round-ups and conflict with those sources.
Does my store need both Sadad and QPay?
Not necessarily as two contracts. You need the QPay route for Qatari debit and a platform that can run your gateway, links and invoicing. A licensed local platform integrated with NAPS – QPay may cover both through one agreement; a bank gateway may cover the route alone.
Can Himyan cardholders pay on my website?
Yes, if your checkout carries the national rails. AlRayan Bank states its Himyan debit card is accepted by online merchants in Qatar through the QPay payment gateway. Confirm Himyan acceptance is enabled on your merchant account, not just supported by the platform generally.
Do I still need Visa and Mastercard if I have local rails?
Yes, for any buyer whose card was issued outside Qatar's national scheme — visitors, expatriates paying on foreign cards and international orders. Local debit rails and international schemes serve different cardholders; a complete stack carries both and presents each buyer the route their card belongs to.
What should I check first when choosing a Qatar payment provider?
Its Qatar Central Bank licensing, before features or pricing. Then confirm in writing which rails and schemes the agreement enables, how settlement reporting and refunds work on each rail, your fallback if the route fails, and the onboarding documents required.
Compose your Qatar payment stack before your next checkout change (CTA)
If your checkout accumulated rather than being designed, the next gateway you add will make it worse. Audit the roles first: local debit through QPay and NAPS, Himyan enabled, a licensed platform for breadth, cards and wallets for outside buyers, a written fallback order and one reconciliation view. WebStackRank builds the store around that stack — start with our ecommerce web development service, bring your gateway contracts and buyer mix, and we will map which roles are covered, duplicated or missing.
