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.
PayTabs is a Saudi-founded payment company that has grown from a hosted checkout into what it now positions as a payment orchestration platform for the Middle East and North Africa.
The distinction matters more than the marketing suggests. A payment gateway takes a card number and gets it authorised. An orchestration platform sits above several acquirers and payment methods and decides where each transaction should go — routing by card scheme, by country, by cost, or away from a processor that is currently declining more than it should. PayTabs sells both: a straightforward gateway for a merchant with one storefront, and an orchestration layer it markets at banks and fintechs processing above USD 100 million a year.
For a Saudi merchant, the practical shape of the product is this. You get a hosted payment page or a direct API integration, a merchant dashboard, tokenisation for saved cards, repeat billing for subscriptions, payment links and invoicing for businesses that sell over WhatsApp and Instagram, and a PCI DSS certified environment behind it. PayTabs also runs Paymes, a social-commerce SuperApp launched in 2022 aimed at micro-merchants and freelancers who do not have a website at all.
The company is regulated in Saudi Arabia under the Saudi Central Bank (SAMA) framework and operates across nine MENA markets. That combination — a single contract that reaches from Riyadh to Cairo to Amman — is the strongest argument for choosing PayTabs over a domestic-only competitor, and it is the lens we used for the rest of this review.
This is the part of the review that will decide it for most readers, so we will be blunt: PayTabs does not publish pricing for its payment gateway. Every rate you will be offered comes out of a sales conversation.
What PayTabs does publish sits on one product line. Its public pricing page lists Paymes, the SuperApp aimed at Saudi micro-merchants, at SAR 49 per month standalone, with a SoftPOS add-on at a further SAR 20 per month, a mada card rate of 1% and a credit card rate of 2.25% + SAR 1. Those figures come with an explicit disclaimer on the page itself: the prices are part of a testing phase and are subject to change. We would not build a financial model on them. The gateway and orchestration tiers carry no numbers at all — both route to a sales contact.
| Line Item | Published Price | What It Covers |
|---|---|---|
| Paymes SuperApp (KSA) | SAR 49 / month | Standalone social-commerce app for micro-merchants. Page notes prices are in a testing phase and subject to change. |
| SoftPOS add-on | +SAR 20 / month | Turns an NFC phone into a card acceptance terminal alongside Paymes. |
| mada card rate (Paymes) | 1% | Applies to the published Paymes tier only — not a quoted gateway rate. |
| Credit card rate (Paymes) | 2.25% + SAR 1 | Applies to the published Paymes tier only — not a quoted gateway rate. |
| Payment Gateway | Not published | Quote only. Rate depends on volume, merchant category code and country. |
| Payment Orchestration | Not published | Positioned at banks and fintechs processing above USD 100m a year. Sales-led. |
| Setup fee | Not published | PayTabs does not state one publicly. Third-party trackers cite a figure; treat it as unverified and get it in writing. |
Search for PayTabs fees and you will find confident-sounding rates — 2.25%, 2.65%, 2.85%, plus a fixed fee of anywhere between SAR 0.30 and SAR 1. These come from comparison sites, not from PayTabs. They contradict each other, which is exactly what you would expect from quote-driven pricing collated by third parties. We are not going to repeat them as fact. Assume your rate will land somewhere in the low-to-mid 2% band for international cards and materially lower for mada, and treat everything else as negotiable.
Quote-driven pricing is not automatically bad. If you process serious volume, a negotiated PayTabs rate can beat any published rate card, because published rates are set for the average merchant and you are not the average merchant. The problem is asymmetry: a small business with no leverage and no benchmark walks into that conversation blind. If you are processing under roughly SAR 100,000 a month, the time cost of running a competitive tender may exceed the saving, and a gateway with a public rate card becomes the rational choice.
We scored PayTabs on the six things that actually determine whether a gateway works for a MENA merchant. These are our editorial judgements, weighted for a Saudi business selling online.
Close to best-in-class. mada, Apple Pay, Samsung Pay, STC Pay, urpay, KNET, OmanNet, Tamara, Tabby, Visa, Mastercard, Amex and UnionPay all sit behind one integration.
Nine MENA markets and 160+ currencies under a single contract. Very few competitors reach Egypt, Jordan and the GCC without a second relationship.
The weakest area by a distance. No published gateway rate, no published setup fee, and the one public rate card carries a testing-phase disclaimer.
A documented REST API, SDKs, hosted payment pages and maintained plugins for Shopify, WooCommerce, Magento, Salla and Zid. Solid rather than delightful.
Next-day SAR settlement is advertised; independent trackers describe real-world cycles closer to T+1 to T+3, and some merchants report delays.
Aggregated merchant reviews split sharply — proactive account managers for larger accounts, slow ticket cycles for smaller ones.
This is where PayTabs earns its place on a Saudi shortlist. Payment method coverage in this region is not a checkbox exercise — get it wrong and you lose the majority of your checkout.
mada is the non-negotiable one. It is the Saudi domestic debit scheme and it carries a very large share of card transactions in the Kingdom, so a gateway without proper mada acceptance is not a Saudi gateway. PayTabs supports mada, and documents mada activation as a distinct step in its merchant workflow rather than assuming it comes on by default — worth knowing, because it means mada is something you activate and confirm, not something you can take for granted on day one.
Beyond mada, the supported list is unusually long: Visa, Mastercard, American Express, UnionPay and Maestro on cards; Apple Pay, Samsung Pay, STC Pay, urpay and PayPal on wallets; and a wide set of local and alternative methods including KNET in Kuwait, OmanNet in Oman, SADAD, Meeza in Egypt, and buy-now-pay-later through Tamara, Tabby, valu, aman, forsa, halan and souhoola. For a merchant selling across the GCC and Egypt, that breadth removes several separate integration projects.
Apple Pay deserves a specific mention because it now materially affects conversion in Saudi Arabia. Apple Pay checkout removes card entry and 3-D Secure friction on iPhone, and iPhone share in the Kingdom is high enough that its absence shows up in your abandonment numbers. PayTabs supports it. Confirm during onboarding that it is enabled on your specific merchant account and domain — Apple Pay requires domain verification, and that step is a common cause of a wallet button that never appears in production.
Settlement is where payment reviews usually go vague. It is also the number that determines your working capital, so it deserves a straight answer.
PayTabs markets next-day settlement in SAR for Saudi merchants — mada, cross-border cards, wallets, instant transfer and BNPL all settling under one contract. Independent trackers describe real-world settlement in the T+1 to T+3 band, which is competitive for the region but not the same as next-day. Both statements can be true at once: settlement cycles vary by payment method, by merchant risk profile and by whether a weekend or public holiday sits in the path. Card scheme funds and BNPL provider funds do not arrive on the same clock.
Our advice is procedural rather than rhetorical. Before you sign, ask for your settlement cycle per payment method, in writing, in the contract — not in an email from a sales representative. Ask specifically what happens to mada versus international cards versus Tamara and Tabby settlements, ask whether a rolling reserve applies to your merchant category, and ask what triggers a hold. Merchants who report settlement pain are usually merchants who discovered a reserve or a risk hold after the fact.
On currency, PayTabs supports 160+ currencies, which matters if you sell into Europe or Asia from a Gulf base. But multi-currency acceptance and multi-currency settlement are different things. Accepting a euro payment while settling in SAR means an FX conversion, and the spread on that conversion is a real cost that rarely appears in the headline rate. If cross-border is more than a rounding error in your revenue, make the FX margin an explicit line in the negotiation.
PayTabs is straightforward to integrate. It is not the most elegant developer product in the market, but it is well documented and it reaches the platforms Saudi merchants actually use.
The plugin coverage is the practical headline. Shopify, WooCommerce and Magento are supported, and — more usefully for this market — so are Salla and Zid, the two dominant Saudi e-commerce platforms. If your store runs on Salla or Zid, a native connector saves you an integration project and, more importantly, saves you from maintaining one. Payhip, Uteach and a long tail of SaaS platforms also ship PayTabs connectors, which is a reasonable proxy for how established the gateway is.
For custom builds, PayTabs exposes a REST API with SDKs and a technical portal documenting hosted payment page flows, repeat billing agreements for subscriptions, and the supported payment method identifiers. Tokenisation is available, so you can store a customer's card as a token and charge it again without touching card data yourself — which is what keeps your PCI DSS scope manageable. Repeat billing lets you push scheduled invoices weekly, monthly or annually, so subscription businesses do not need a separate billing engine for simple cases.
Where we would set expectations: this is a payments API from a regional processor, not a developer-experience showpiece. Sandbox behaviour and error handling reward reading the documentation carefully rather than guessing from method names, and the hosted payment page gives you less design control than an embedded field-level integration. Budget a proper engineering sprint for a direct API integration, and use the hosted page or a plugin if your team is small.
Onboarding a SAMA-regulated payment provider is a documentation exercise, not a signup form. Here is what the process actually looks like and where it stalls.
A valid Saudi commercial registration (CR) is the entry requirement for essentially every SAMA-regulated gateway, PayTabs included. No CR, no merchant account. Freelancers without one should look at freelance-licence-friendly products such as Paymes instead.
Expect national ID or passport for owners and signatories, bank account details in the business name, and a description of what you sell. High-risk merchant categories face additional scrutiny and, sometimes, a rolling reserve as a condition of approval.
Your site is checked for refund, shipping, privacy and terms pages, working contact details, and pricing shown in the currency you will charge. A missing refund policy is one of the most common causes of a rejected or delayed application.
Once approved you integrate, verify your Apple Pay domain, activate mada explicitly, and run live test transactions. Do not schedule a campaign against a go-live date until you have processed a real transaction end to end and seen it settle.
Realistic timelines depend almost entirely on how complete your paperwork is when you submit it. Merchants with a clean CR, a compliant website and a low-risk category can move quickly; merchants who submit incrementally spend weeks in back-and-forth. Aggregated reviews cite slow onboarding responses as a recurring complaint, so front-load your documents and nominate one person to own the thread.
No gateway is uniformly good, and a review that does not say where a product hurts is not a review. These are the six things we would want a prospective merchant to weigh honestly.
The gateway has no published rate and no published setup fee. You cannot model your cost of acceptance before speaking to sales, and you have no public benchmark to negotiate against. Smaller merchants carry the whole cost of that asymmetry.
Aggregated merchant reviews describe a sharp split — attentive account management on larger accounts, slow ticket cycles on smaller ones. Ask what support tier your contract actually entitles you to and whether a named contact is included.
Next-day settlement is marketed; T+1 to T+3 is what independent trackers report, and some merchants report longer. Get the cycle written into the contract per payment method rather than relying on the marketing figure.
Fee clarity is the single most common complaint theme in negative reviews. Before signing, ask for the full schedule: chargeback fee, refund fee, FX margin, monthly minimum, PCI fee and any dormancy charge.
The hosted payment page is fast to deploy but limits how closely checkout can match your brand. A fully branded checkout means a direct API integration and the engineering time that comes with it.
Gateway, orchestration, SoftPOS and Paymes are different products with different economics. A small merchant can end up in an orchestration-shaped conversation they do not need. Be explicit about which product you are buying.
PayTabs competes with a strong local field. The honest summary is that most of these providers also decline to publish rates — which makes the ones that do publish disproportionately valuable to a small merchant.
| Provider | Best For | Coverage | Public Pricing | Rating |
|---|---|---|---|---|
| PayTabs | Multi-country MENA merchants | 9 MENA markets, 160+ currencies | Not published (Paymes tier only) | 4.2 |
| Tap Payments | GCC-wide launch speed | GCC-focused | Not published | 4.3 |
| Moyasar | Saudi SMEs wanting certainty | Saudi Arabia | Published rate card | 4.4 |
| HyperPay | Enterprise and high volume | Saudi Arabia + regional | Not published | 4.1 |
| Geidea | Omnichannel POS plus online | Saudi Arabia, 100+ currencies | Not published | 4.0 |
The closest direct competitor for a merchant whose priority is the GCC rather than the wider MENA region. Tap is well established across the Gulf, supports mada, Apple Pay and KNET, and has a strong reputation for getting merchants live quickly with a clean developer integration.
The natural head-to-head against PayTabs if your footprint is GCC-only. Run both quotes side by side — neither publishes rates, so the only way to compare is to make them compete.
The Saudi gateway most often cited for publishing its rates openly, which removes the sales-negotiation step entirely for smaller merchants. Third-party comparison articles quote conflicting figures for its mada rate, so verify on Moyasar's own pricing page rather than trusting a roundup.
The rational default for a Saudi-only SME that values a knowable cost of acceptance over a negotiated one. Coverage stops at the Saudi border, so it is not a PayTabs replacement for regional sellers.
A long-established regional processor with a strong enterprise footprint in Saudi Arabia. Like PayTabs, pricing is quote-driven, and the value tends to appear at volume where a negotiated rate and dedicated account management justify the procurement effort.
Worth including in a tender if you process serious volume. Less compelling for a small store that simply wants a rate and a working checkout this week.
A SAMA-supervised Saudi payments company whose distinguishing feature is breadth across channels: payment gateway, payment links, SoftPOS, physical terminals and point of sale, with customisable payment pages, recurring billing, fraud tools and support for over 100 currencies.
The strongest pick if you sell in a physical store and online and want one provider across both. Overkill if you are purely e-commerce.
Our VerdictPayTabs is a genuinely capable regional payment platform with one structural weakness. Whether that weakness disqualifies it depends entirely on your leverage.
If you sell into more than one MENA market, this is the strongest case on the list. Nine countries, 160+ currencies, mada through to KNET and Meeza, on one contract and one integration. That consolidation is worth accepting an opaque rate card for.
If you are a Saudi-only SME and you want to know your cost of acceptance before you commit, a gateway with a public rate card beats a negotiation you have no leverage in. Verify current rates on their own pricing page.
For a GCC-focused merchant, Tap is the direct alternative to put beside PayTabs. Neither publishes rates, so request both quotes on the same day with the same volume assumptions and let them compete.
If your business has a shop floor as well as a checkout page, a provider that covers terminals, SoftPOS and online under one relationship removes a reconciliation problem that a pure gateway will never solve for you.
PayTabs does not publish gateway transaction fees. The only rates on its public pricing page belong to Paymes, its SuperApp for micro-merchants — SAR 49 per month, a 1% mada rate and 2.25% + SAR 1 on credit cards — and that page states the prices are part of a testing phase and subject to change. For the payment gateway you will receive a quote based on your volume, merchant category and country. Comparison sites quote figures ranging from roughly 2.25% to 2.85% plus a fixed fee, but these come from third parties and contradict each other, so treat them as a negotiating reference rather than a price.
Yes to both. mada support is documented as a specific activation step in the PayTabs merchant workflow rather than something enabled automatically, so confirm it is live on your account before launch. Apple Pay is supported alongside Samsung Pay, STC Pay, urpay and PayPal. Apple Pay also requires domain verification during setup — an unverified domain is the usual reason the Apple Pay button never appears on a production checkout.
PayTabs markets next-day settlement in SAR for Saudi merchants across mada, cards, wallets, instant transfer and BNPL. Independent trackers describe real-world settlement cycles in the T+1 to T+3 range, and some merchants report delays beyond that. Settlement timing varies by payment method and merchant risk profile, so ask for your cycle per payment method to be written into the contract, and ask specifically whether a rolling reserve applies to your merchant category.
PayTabs operates across nine MENA markets — Saudi Arabia, the UAE, Kuwait, Bahrain, Oman, Qatar, Jordan, Egypt and Palestine — and supports more than 160 currencies. That regional reach on a single contract is its clearest advantage over Saudi-only gateways. Note that accepting 160+ currencies is not the same as settling in them; if you sell cross-border, ask about the FX margin applied when a foreign-currency payment is converted to your settlement currency.
It depends on your footprint. PayTabs wins on multi-country MENA coverage, reaching Egypt, Jordan and Palestine alongside the GCC. Tap Payments is the closer comparison for a GCC-only merchant and is similarly quote-driven, so the only real way to choose is to run both quotes at once. Moyasar wins for a Saudi-only SME that values published pricing over a negotiation, since it removes the sales step entirely — but its coverage stops at the Saudi border, so it cannot replace PayTabs for a regional seller.
Get weekly expert recommendations, honest comparisons, and exclusive guides — tailored for the Middle East market.
