Accept Tap Payments
without building the integration
Tap Payments is a Gulf-focused payment gateway offering the local methods that dominate the region's checkouts — mada in Saudi Arabia, KNET in Kuwait, Benefit in Bahrain, Fawry in Egypt — alongside international cards. In these markets local schemes carry more volume than global cards, which is why a card-only checkout underperforms there.
- SAR
- KWD
- AED
- BHD
- QAR
- OMR
- EGP
- USD
- EUR
- GBP
- Region
- MENA
- Methods
- 4
- Credentials
- Server-side only
- PaymentHood fee
- None
- Status
- Live
Tap Payments in summary
- Coverage
-
- Saudi Arabia
- Kuwait
- United Arab Emirates
- Bahrain
- Qatar
- Oman
- Egypt
Among the markets Tap Payments serves — their own list is authoritative (opens in new tab).
- Currencies
-
- SAR
- KWD
- AED
- BHD
- QAR
- OMR
- EGP
- USD
- EUR
- GBP
Among those supported. Which ones your account can charge in depends on its registered country.
- Fees
- Set and billed by Tap Payments, 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 Tap Payments'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, Tap Payments'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.
Local schemes
mada, KNET, Benefit and Fawry
Cards
Visa, Mastercard and American Express
Digital wallets
Apple Pay and Google Pay
Buy now, pay later
Tabby and regional instalment providers
What PaymentHood handles for you
A direct Tap Payments integration is not just an API call. These are the parts every team ends up rebuilding — and the parts PaymentHood ships already done.
- Credentials
- Secret API key, held server-side in PaymentHood
- Webhook security
- Signed charge notification, validated before an order is released
- Payment verification
- Server-side charge status re-check against the Tap API before fulfilment
- Idempotent charge creation, so a retried request never double-charges a customer
- Automatic failover to another configured provider when Tap Payments is unreachable
- One reconciliation view across Tap Payments 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 Tap Payments on your platform
Install the free PaymentHood plugin for your store, then enable Tap Payments in your dashboard.
Connecting Tap Payments takes three steps
Open your Tap Payments account
Register directly with Tap Payments and complete their onboarding. Funds settle from Tap Payments into your own bank account — PaymentHood never holds merchant money.
Add the credentials to PaymentHood
Paste your Tap Payments 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 Tap Payments appears as a payment option. Test in sandbox, then switch to live.