Accept PayTabs
without building the integration
PayTabs is a MENA payment gateway covering the Gulf plus Egypt, Jordan and Iraq. It combines international cards with the region's local schemes and wallets — mada, KNET, STC Pay — and the instalment products such as valu and Tabby that carry real weight in Egyptian and Gulf checkouts.
- SAR
- AED
- EGP
- KWD
- OMR
- JOD
- USD
- Region
- MENA
- Methods
- 4
- Credentials
- Server-side only
- PaymentHood fee
- None
- Status
- Live
PayTabs in summary
- Coverage
-
- Saudi Arabia
- United Arab Emirates
- Egypt
- Kuwait
- Oman
- Jordan
- Iraq
Among the markets PayTabs serves — their own list is authoritative (opens in new tab).
- Currencies
-
- SAR
- AED
- EGP
- KWD
- OMR
- JOD
- USD
Among those supported. Which ones your account can charge in depends on its registered country.
- Fees
- Set and billed by PayTabs, and published on their pricing page (opens in new tab). PaymentHood adds nothing on top, at any volume.
- Official resources
- Website (opens in new tab) · Developer docs (opens in new tab)
Written against PayTabs's own documentation on . This page deliberately states no fees, no counts and no completeness claims, because those change without notice — for anything you are about to build on, PayTabs's own documentation (opens in new tab) is the authority.
What your customers can pay with
Every method below runs through the same PaymentHood checkout. Turning one on or off is a dashboard setting, not a code change.
Cards
Visa, Mastercard, American Express, mada, UnionPay and Maestro
Digital wallets
Apple Pay, Samsung Pay and STC Pay
Local methods
KNET, valu, aman and Meeza QR
Buy now, pay later
Tabby and regional instalment options
What PaymentHood handles for you
A direct PayTabs integration is not just an API call. These are the parts every team ends up rebuilding — and the parts PaymentHood ships already done.
- Credentials
- Profile ID and server key, held server-side in PaymentHood
- Webhook security
- Signed transaction callback, validated before an order is released
- Payment verification
- Server-side transaction query against the PayTabs API before fulfilment
- Idempotent charge creation, so a retried request never double-charges a customer
- Automatic failover to another configured provider when PayTabs is unreachable
- One reconciliation view across PayTabs and every other provider you run
- Provider credentials never reach the storefront or the customer's browser
- Adding or switching a provider later is a dashboard change, not a re-integration
Use PayTabs on your platform
Install the free PaymentHood plugin for your store, then enable PayTabs in your dashboard.
Connecting PayTabs takes three steps
Open your PayTabs account
Register directly with PayTabs and complete their onboarding. Funds settle from PayTabs into your own bank account — PaymentHood never holds merchant money.
Add the credentials to PaymentHood
Paste your PayTabs API credentials into the PaymentHood dashboard. They are stored server-side and never exposed to your storefront.
Enable it at checkout
Install the PaymentHood plugin for your platform, paste your PaymentHood API key, and PayTabs appears as a payment option. Test in sandbox, then switch to live.