This article may contain affiliate links. If you purchase through these links, we may earn a commission at no extra cost to you. This helps support our independent reviews.
HyperPay is a Riyadh-headquartered payment service provider that sits between a Saudi merchant's checkout and the acquiring bank — routing card, wallet and local payment method transactions, handling the security burden, and delivering a merchant dashboard on top.
The category matters, because 'payment gateway' is used loosely in this market. HyperPay is not an acquiring bank; your money still settles through an acquirer under a merchant agreement. It is not a full-stack processor in the Stripe sense, where the same entity underwrites you and holds the funds. It is a payment technology layer and payment services provider — the piece that takes a card number from a browser or an app, authenticates it, routes it, tokenises it, screens it for fraud, and hands the result to the bank that actually moves the money.
Its footprint is regional rather than Saudi-only. Alongside the Kingdom, HyperPay lists operations in the UAE, Jordan, Oman, Qatar, Iraq, Lebanon and Bahrain, which is the practical argument for choosing it over a single-country provider: one integration, one contract structure and one support relationship across a Gulf expansion, rather than a new gateway procurement in every market you enter.
The company was founded by Muhannad Ebwini, who remains chief executive, and has been in the market long enough to be treated as an incumbent rather than a startup. In 2023 it publicly signalled an intention to list on the Saudi exchange; we have not been able to confirm a completed listing, so treat the IPO story as ambition rather than fact. What is verifiable — the SAMA licence and the National Payment Gateway certification — matters far more to a merchant than the capital markets narrative anyway.
For a Saudi merchant, the acceptance list is the single most commercially important thing about a gateway. Get it wrong and you lose the sale at the last screen.
mada is the non-negotiable one. It is the domestic debit scheme, it is what most Saudi consumers reach for by default, and a checkout that only offers international credit cards will quietly bleed conversion. HyperPay supports mada, including pre-authorisation, which matters for hotels, car rental, delivery and any business that needs to hold an amount before capturing a final figure. Alongside it sit Visa, Mastercard, American Express and UnionPay.
The wallet and alternative-method layer is where HyperPay has invested visibly. Apple Pay is supported, and in 2023 HyperPay announced support for mada Apple Pay recurring payments — a genuinely useful capability for subscription businesses, because it lets a Saudi customer pay for a recurring service with a domestic debit card inside Apple Pay rather than forcing them onto an international credit card they may not hold. STC Pay and SADAD are covered, and Tabby appears on HyperPay's supported list for buy-now-pay-later. PayPal is available for cross-border consumers.
Two honest caveats. First, we could not verify Tamara support from HyperPay's own material; if Tamara is commercially important to you, get it confirmed in writing rather than assuming BNPL coverage is uniform. Second, acceptance lists published by gateways describe what the platform can do, not what your specific merchant account has been enabled for. Every scheme and wallet has to be switched on for your MID by the acquirer. Ask for your enabled method list as part of the contract, not after go-live.
Underneath the acceptance list, HyperPay is selling a control surface: a dashboard, a set of risk tools and a small number of operational features that decide how much your finance team suffers each month.
The core of it is a merchant control panel for monitoring transactions, an accompanying mobile app, business intelligence reporting, and an anti-fraud layer the vendor describes as AI-based. There is smart routing for merchants running more than one acquiring relationship, tokenisation so returning customers do not re-enter card details, and recurring billing for subscription models. HyperPay also markets HyperTap, a tap-to-phone product that turns an ordinary smartphone into a contactless acceptance device — first launched in the UAE — for merchants who want in-person acceptance without buying terminals.
The feature that deserves a specific mention is no-redirection payment. With the COPYandPAY widget, the card form renders inside your own page and the sensitive data goes straight from the shopper's browser to HyperPay's platform. The customer never bounces to a bank-branded page and back. That is worth real conversion percentage points on mobile, where a redirect chain is the most common place a Saudi checkout loses the sale — and it is achieved without your servers ever touching a raw card number.
This is the part of the evaluation where HyperPay is strongest, and also the part where the marketing copy needs a second look.
The regulatory position is solid. HyperPay is licensed by the Saudi Central Bank — the licence was granted to its Saudi entity to operate digital payment services — and in February 2026 the company announced it had achieved SAMA's National Payment Gateway certification, which validates its integration with the Kingdom's national payment infrastructure. For a Saudi merchant, using a SAMA-licensed provider is not a nice-to-have. It is the baseline that keeps your acquiring relationship, your mada acceptance and your regulatory exposure clean.
On the technical security side, HyperPay states it holds PCI DSS Level 1 — the highest merchant-services tier — along with ISO 27001 for information security management and ISO 27701 for privacy information management. That trio is a credible stack. But HyperPay's own site describes its certification as PCI DSS Level One 'version three', and version 3 of the standard was retired in favour of version 4. That is almost certainly stale website copy rather than a lapsed certification, and we would not read it as a red flag — but it is exactly the kind of detail worth resolving by asking for the current Attestation of Compliance with its date, rather than trusting a marketing page.
A gateway lives or dies on how the integration goes, because the cost of a payment provider is never only the transaction fee — it is also the two weeks of engineering nobody budgeted for.
HyperPay offers three routes in. COPYandPAY is a JavaScript widget that renders the payment form on your page and posts card data directly to HyperPay, keeping your servers out of the card data path. The server-to-server API gives you full control of the flow for teams that want to own the front end entirely and orchestrate the backend themselves. And there are native mobile SDKs for iOS and Android for in-app payments. Documentation lives on a dedicated developer site, and there are community-maintained wrappers for Flutter and React Native — a decent signal that real teams are shipping on this platform rather than only enterprise integrators.
The pattern most teams use is straightforward: your backend requests a checkout token, the frontend renders the widget or opens the SDK against it, the customer pays, and then your backend independently verifies the outcome against the status API rather than trusting the client. That last step is not optional and it is where sloppy integrations go wrong — never mark an order paid on a browser callback alone.
The concrete limitation to know about before you scope the work is documented in HyperPay's own FAQ: the SDK supports card payments only, and SADAD is not available through it. If your Saudi mobile app needs SADAD, you are building a separate flow for it rather than getting everything through one native integration. There is also a WordPress plugin, but it is distributed through a support email rather than the public plugin directory, so a WooCommerce merchant should confirm the version, its maintenance status and its compatibility before assuming a five-minute install.
Cash flow is where payment decisions get expensive, and it is the area where HyperPay is least forthcoming in public.
HyperPay does not publish settlement timings. Its FAQ says the settlement process is the same across payments processed between HyperPay and the acquiring bank, and is governed by your merchant agreement — which is an accurate description of how a PSP model works, but it also means the answer to 'when do I get paid' is not on the website. It is in a contract you have not seen yet. Third-party comparison articles assert a T+1 schedule; we could not verify that against vendor material and would not plan working capital around it.
Onboarding follows the same shape. The documentation requirements depend on the acquiring bank and the country of company registration rather than being a fixed HyperPay checklist. In practice a Saudi merchant should expect to produce a commercial registration, VAT registration, bank account details in the trading entity's name, and website or app evidence including published refund and privacy policies. HyperPay's positioning skews toward established medium and large businesses rather than a founder testing an idea on a weekend, so budget for a relationship-managed onboarding rather than a self-service signup.
A review that only lists strengths is a brochure. These are the six things that would slow down our purchase, or send a particular business elsewhere.
HyperPay's site and FAQ decline to state rates, saying costs vary by country and directing you to business development. Competitors including Moyasar and Tap put figures in public. Opaque pricing is not automatically bad pricing, but it does mean you cannot compare without entering a sales process, and it shifts the negotiating advantage to the vendor.
Comparison sites variously quote 2.5% plus SAR 0.75, 2.75% plus SAR 1, and a range of 2.5% to 3.5% for the same product. These cannot all be right. Do not build a business case on any of them — treat them as evidence that public figures for this vendor are unreliable.
Search for HyperPay reviews and you will land on hyperpay.tech, a cryptocurrency wallet with a substantial volume of negative reviews and no relationship to the Riyadh payment gateway. Anyone doing a quick reputation check risks pricing in the wrong company's problems. Ask for merchant references in your own sector instead.
For a business with thin working capital, the difference between next-day and weekly settlement is more consequential than half a percentage point on the rate. HyperPay defers this to the merchant agreement, so you cannot evaluate it during shortlisting without a sales conversation.
HyperPay's own FAQ states the SDK carries card payments only and does not support SADAD. If SADAD is part of your Saudi mobile payment mix, that is additional engineering rather than a configuration toggle, and it should be scoped before you sign.
The whole model — enterprise sales, account managers, acquirer-dependent onboarding, no public rate card — is built for established merchants. A small Saudi store that wants to be live this week and does not have negotiating volume will get a faster, cheaper answer from a self-service provider.
We will be direct: HyperPay publishes no prices, so what follows is a map of the claims in circulation with their evidentiary status attached, not a rate card. Anyone presenting these numbers as HyperPay's pricing is guessing.
| Cost Item | Figure Quoted by Third Parties | Vendor-Published? | What It Actually Depends On |
|---|---|---|---|
| Setup fee | Around SAR 1,500 (one Saudi guide) | No | Acquirer, merchant category and whether setup is waived as part of a volume commitment |
| Monthly fee | Around SAR 250 (same source) | No | Plan, included features, and whether HyperTap or additional MIDs are attached |
| mada transaction | 1.5% + SAR 1 (unverified — see below) | No | The acquirer's regulated merchant service charge plus any separate gateway margin |
| Credit card transaction | 2.5%–3.5% + SAR 0.75–1 across sources | No | Card type, issuing region, merchant category code, volume and risk profile |
The mada figure deserves scrutiny, because it almost always circulates without saying which rail it applies to. SAMA regulates mada economics on both, but at different levels. For card-present transactions at a terminal, the acquiring bank is limited to a merchant service charge of 0.80% of purchase value, capped at SAR 40 per transaction. For card-not-present e-commerce, SAMA Circular 391000075005 of 18 March 2018 sets a separate ceiling: a maximum merchant service charge of 1.75%, with 0.70% interchange inside it. A quoted 1.5% for online mada therefore sits legally beneath the e-commerce ceiling — holding it against the 0.80% in-store cap compares two different rails, not a fair price against an unfair one. The real trap sits elsewhere: the regulated percentage binds only the acquiring bank's charge. A gateway's own margin and any fixed per-transaction fee fall entirely outside it, which is why a headline of 1.5% + SAR 1 on a SAR 20 basket is an effective 6.5%. So the correct question to put to any Saudi gateway is not what is your mada rate, it is show me the acquirer merchant service charge and your own fee as two separate lines, and tell me which rail each applies to. Vendors that will not split them are telling you something.
The second thing to price is what sits outside the headline rate. Ask specifically about the chargeback fee per case, the refund fee and whether the original transaction fee is returned on a refund, international and cross-border card surcharges, currency conversion margin if you sell outside SAR, any minimum monthly processing commitment, the contract term and its early-exit terms, and the 15% Saudi VAT treatment on gateway service fees. On a real merchant's statement these items routinely add more than the difference between two providers' advertised percentages.
Finally, a note on how to use this section. It is not evidence that HyperPay is expensive — it may well be competitive at volume, and enterprise negotiations in this market regularly land below public rate cards. It is evidence that you cannot know without asking. Get a written quote, put the same transaction mix in front of two or three providers, and compare the total cost of a representative month rather than the two numbers on the front of the proposal.
HyperPay belongs on a Saudi shortlist, but never alone. These are the providers we would put beside it, with the same caveat applied to all of them: published figures in this market go stale quickly and vary by merchant, so confirm everything in your own quote.
| Platform | Best For | mada | Setup Cost | Settlement | Rating |
|---|---|---|---|---|---|
| HyperPay | Established merchants scaling across MENA | Supported, with pre-auth | Not published — quote only | Per merchant agreement; unpublished | 4.2 |
| Tap Payments | GCC-wide merchants wanting fast developer onboarding | Supported, below card rates | Reported as free | Confirm in your agreement | 4.4 |
| Moyasar | Saudi-only merchants who want published rates | Supported; simplest onboarding | Reported SAR 0–1,500 by package | T+1 on mada per third-party reports | 4.3 |
| PayTabs | Regional merchants with multi-currency needs | Supported | Administrative fee on registration | Confirm in your agreement | 4.0 |
| Geidea | Merchants needing terminals and online together | Supported across POS and online | Varies by hardware package | Confirm in your agreement | 4.2 |
A GCC-native payment provider with a strong developer reputation, broad regional coverage and a self-service onboarding path that gets a merchant testing in hours rather than weeks. Card rates reported by third parties sit at the higher end of the Saudi range, with mada priced below cards.
The better pick if your engineering team wants to be live quickly and you value a documented, self-serve integration over a negotiated enterprise contract.
A Saudi-focused gateway whose differentiator is simplicity: straightforward mada onboarding and an unusually clean API. It publishes no rate card either, so the comparison against HyperPay is quote against quote, and its own documentation describes settlement as a twice-weekly batch on Monday and Thursday rather than the T+1 that third-party roundups report.
The strongest counter-offer to HyperPay for a Saudi-only merchant — the one to benchmark against precisely because its numbers are visible before you talk to sales.
A SAMA-licensed provider that spans physical terminals, SoftPOS tap-to-phone acceptance and online payments, which makes it the natural comparison for a merchant whose volume is split between a shop floor and a website rather than being purely e-commerce.
Worth a proposal if in-person acceptance is a material share of revenue and you would rather reconcile one provider than two.
Our VerdictHyperPay is a serious, properly regulated regional payment provider with genuinely good payment coverage and a real developer platform — wrapped in a commercial model that tells you almost nothing until you enter a sales process. It is a strong candidate for an established merchant and a poor fit for anyone who needs to be live next week.
mada with pre-authorisation, the major international schemes, Apple Pay including mada recurring, STC Pay, SADAD and Tabby — with tokenisation and inline checkout that keeps the shopper on your domain.
SAMA-licensed with National Payment Gateway certification announced in February 2026, plus PCI DSS Level 1, ISO 27001 and ISO 27701. Marked down only for stale version references in the public compliance copy.
COPYandPAY, a server-to-server API and native iOS and Android SDKs cover the realistic integration patterns. The documented SDK gap on SADAD, and a WordPress plugin distributed by email, keep this from full marks.
No published rates, no published settlement schedule, and third-party figures that contradict each other. Competitors put numbers in public; HyperPay makes you ask, and that costs you comparison leverage.
Our recommendation is procedural rather than binary. If you are an established Saudi or Gulf merchant with volume worth negotiating over, put HyperPay in a three-way tender against Moyasar and Tap, insist on a written quote that separates the acquirer's merchant service charge from the gateway fee, and get settlement timing, chargeback fees and contract term in the same document. If you are a smaller store that needs to accept mada this month, the honest answer is that a provider with published pricing and self-service onboarding will get you there faster and you will find out what it costs before you commit.
HyperPay does not publish its pricing. Its own site and FAQ state that costs vary by country and direct prospective merchants to a business development contact. Third-party comparison articles quote figures such as a SAR 1,500 setup fee, roughly SAR 250 per month, and per-transaction rates between 2.5% and 3.5%, but these sources contradict each other and none are vendor-confirmed. Treat every published figure as unverified and price from a written quote.
Yes. HyperPay supports mada, Saudi Arabia's domestic debit scheme, including pre-authorisation for businesses that need to hold an amount before capturing a final charge. It also supports mada through Apple Pay, and announced support for mada Apple Pay recurring payments in 2023, which allows subscription billing against a domestic debit card. Confirm that mada is enabled on your specific merchant ID as part of onboarding rather than assuming platform support equals account support.
HyperPay is licensed by the Saudi Central Bank and announced in February 2026 that it had achieved SAMA's National Payment Gateway certification. It states that it holds PCI DSS Level 1 certification along with ISO 27001 and ISO 27701. One caveat worth resolving directly: the public site still describes its PCI certification as version three, and that version of the standard has been superseded by version four, so request the current dated Attestation of Compliance.
HyperPay does not publish a settlement schedule. Its FAQ states that settlement follows the process agreed between HyperPay and the acquiring bank as set out in your merchant agreement, which means the timing is contract-specific rather than a standard product term. Some third-party sources claim T+1, but we could not verify that against vendor material. Get the exact schedule, daily cut-off times and weekend or holiday behaviour written into your contract before signing.
Because most of them are not about this company. The heavily reviewed hyperpay.tech is a cryptocurrency wallet with no connection to the Riyadh-headquartered payment gateway at hyperpay.com, and review aggregators routinely conflate the two. Genuine merchant feedback on the Saudi gateway is comparatively thin: positive comments tend to cite the technology and 24/7 support, while critical ones cite slow resolution of escalated issues. Ask the vendor for two merchant references in your own sector and call them.
Get weekly expert recommendations, honest comparisons, and exclusive guides — tailored for the Middle East market.
