How to Choose a Payment Gateway for an Online Store in Oman

Most Omani online stores accept payments through one of four routes: a locally licensed fintech gateway such as Thawani Pay or Amwal Pay, their bank's e-commerce merchant service, a regional or international gateway that supports Omani companies and OMR, or an orchestration layer that sits on top of several gateways. Pick based on which cards your customers carry, the total cost on your real basket mix, how settlement works, and how cleanly the gateway connects to your store.

digital-payment

Key takeaways

  • Shortlist two or three providers and get written quotes covering every fee line: setup, percentage, fixed fee, refunds, chargebacks, settlement and reserves.
  • Before you apply, confirm the provider is licensed or authorised by the Central Bank of Oman. Check the CBO's own website, not only the provider's marketing.
  • Use a hosted or embedded checkout unless you have a strong reason not to. It keeps card data off your servers and shrinks your PCI DSS scope.
  • Have your developer store amounts in baisa (OMR has three decimals), confirm payments by server-side webhook rather than the browser redirect, and test refunds before launch.
  • If you sell across the GCC, look at orchestration or a regional gateway early so you don't have to rebuild checkout when you expand.

The short answer: four ways to take online payments in Oman

An Omani online store can take card and local payments in four main ways:

  1. A locally licensed fintech gateway. Thawani Pay is one example. A third-party partner announcement describes it as a fintech founded in 2016 and regulated by the Central Bank of Oman, offering online payments, bill payments and other digital payment services (MoneyHash).
  2. Your bank's e-commerce merchant service. Here the bank you already use acts as acquirer and provides or partners on the gateway.
  3. A regional or international gateway. This only works if the provider currently onboards Omani entities and settles in OMR. Confirm both directly before you plan around one.
  4. A payment orchestration layer. This is one integration that routes payments to one or more gateways. In April 2026, the orchestration platform MoneyHash announced a partnership with Thawani Pay that gives merchants access to Omani gateway providers through a single layer (MoneyHash).

A store selling only inside Oman usually starts with one local gateway. A brand selling in Oman, Saudi Arabia and the UAE should think about orchestration or a regional provider from day one.

Gateway vs acquiring bank vs aggregator: who does what?

The gateway moves the payment data, the acquirer holds the merchant account and pays you, and an aggregator bundles both under its own account. Knowing who is who tells you who you sign with, who pays you and who handles disputes.

RoleWhat it doesWhy it matters to you
Payment gatewayCaptures card details securely, sends the authorisation request and returns the result to your storeDecides your checkout experience and developer effort
Acquiring bankHolds your merchant account, receives funds from the card networks and settles them to your bank accountDecides settlement timing, reserves and chargeback handling
Aggregator / payment facilitatorOnboards you under its own master merchant account, so you get gateway and acquiring in one contractUsually simpler onboarding, but you're bound by its risk rules
Orchestration layerSits above several gateways and routes each transaction by country, card type or costUseful for multi-country GCC sellers or anyone who wants a backup provider

Some providers play more than one role. Ask each one plainly: "Who is the acquirer, and who settles funds to my account?"

Which payment gateway options can Omani businesses use?

You can choose from local fintechs, bank merchant services, regional or international providers, and orchestration. Each suits a different stage of business.

OptionBest fitWhat to verify before signing
Local licensed fintech (e.g. Thawani Pay or Amwal Pay)Oman-focused stores that want local onboarding and supportCBO licence status, accepted card types, settlement terms, plugins for your platform
Bank merchant / e-commerce serviceBusinesses with an existing banking relationship and steady volumeWhether an online gateway is included or added through a partner, integration options, developer documentation
Regional or international gatewayBrands selling across several GCC marketsWhether it onboards Omani companies today, OMR settlement, local card support
Orchestration platformMulti-gateway or multi-country setups, or redundancyWhich Omani and GCC gateways it connects to, extra platform fees

Local cards matter. Omani shoppers don't only use Visa and Mastercard. Ask every provider whether it accepts cards on OmanNet, the local network. If you sell across the GCC, also ask about each market's local scheme, such as mada in Saudi Arabia, KNET in Kuwait and Benefit in Bahrain. A gateway that only takes international cards can quietly lose you a share of checkouts.

Apple Pay, Google Pay and other wallets vary by provider. Ask, and get the answer in writing.

How are payment gateway fees structured?

Most providers charge some mix of setup or subscription fees, a percentage per transaction, a fixed fee per transaction, and charges for refunds, chargebacks and settlement. The headline percentage is only one line, so compare the total cost on your own order mix.

Fee componentWhat it isWhat to ask in writing
Setup / onboardingOne-off fee to open the accountIs it waived? Does it include integration support?
Monthly or annual feePlatform or account feeAny minimum monthly volume or minimum fee?
Percentage per transaction% of each successful paymentIs it different for local cards, international cards and wallets?
Fixed fee per transactionFlat amount per paymentIs it charged on failed attempts too?
Refund feeCost of issuing a refundIs the original transaction fee returned when you refund?
Chargeback feeCharged when a customer disputes a paymentHow much, and what evidence process applies?
Settlement / payoutHow and when money reaches your bankSettlement frequency, payout fees, minimum payout
Currency conversionFee when the customer's card currency differs from OMRWho sets the rate, and is there a markup?
Rolling reserveShare of revenue held back as securityPercentage, duration, conditions for release
Contract termsLock-in period and exitEarly termination fees, notice period, data export

For where payment costs sit in your overall launch budget, see our website cost breakdown for Oman.

What are the steps to set up a payment gateway?

Setup takes seven steps: prepare your documents, apply, pass the risk review, build in the sandbox, test, go live and reconcile. Approval mostly depends on two things: how complete your paperwork is and how ready your website looks.

  1. Get your company paperwork in order. Providers generally ask for proof of a registered business, owner or signatory identification and company bank account details. The exact list varies by provider, so ask for it in writing. Check any e-commerce licensing requirements with the Ministry of Commerce, Industry and Investment Promotion.
  2. Request quotes and documentation from two or three providers. Read the developer docs before you sign, not after.
  3. Prepare the site for risk review. Reviewers look at your live or staging site. Have visible prices in OMR, clear product descriptions, and refund, delivery, privacy and terms pages, plus a contact page with a physical address, all in Arabic and English.
  4. Get sandbox credentials and build the integration against the test environment.
  5. Test every path: successful payment, decline, 3-D Secure challenge, abandoned payment, timeout, full refund, partial refund and webhook retries.
  6. Go live. Swap to production keys, make a small real purchase, refund it, and check that both appear correctly in your dashboard and your store.
  7. Reconcile the first settlements against your orders before you scale up marketing.

What does a developer need to build for payments?

Your developer needs to build a checkout flow, server-side payment confirmation, a clear set of order states, refunds and correct OMR amount handling, in both languages.

Checkout type. A hosted checkout sends the customer to the provider's payment page. An embedded form keeps them on your site but loads card fields from the provider. A direct API integration means your servers handle card data. For most stores, hosted or embedded is the right choice.

Webhooks, not redirects. Mark an order as paid only after your server receives and verifies the provider's webhook, or after it queries the payment status itself. Customers close tabs and lose signal mid-redirect, so the browser return URL can't be trusted alone.

Order states. Model at least: pending, authorised, paid, failed, cancelled, refunded, partially_refunded and disputed. Every transition should be logged with the provider's transaction ID.

Idempotency. Webhooks can arrive twice. Use idempotency keys and unique transaction IDs so a retry never ships an order twice or refunds it twice.

OMR has three decimals. One rial is 1,000 baisa. Many gateways expect amounts in the currency's smallest unit, so OMR 12.345 is sent as 12345, not 1234. Developers used to two-decimal currencies often multiply by 100 by mistake. Store money as integers in baisa, round once at a defined point, and read each provider's docs for the expected format.

Price: OMR 12.345
Stored as: 12345 (baisa, integer)
Sent as: 12345 if the gateway expects minor units
Wrong: 1234 or 1235 (two-decimal assumption)

Arabic and English checkout. Pass the customer's language to the gateway if it supports one. Make sure error messages, receipts and confirmation emails exist in both languages, and that the payment step displays correctly in right-to-left layout. Our bilingual Arabic–English website checklist covers the wider details.

Refunds and reporting. Let staff issue full and partial refunds from your admin rather than logging into the gateway. Export a reconciliation report that matches orders, payments, fees and settlements.

Security and compliance: PCI DSS, 3-D Secure and the Central Bank of Oman

Use a PCI DSS-compliant provider, enable 3-D Secure, and confirm the provider's regulatory status with the Central Bank of Oman. These three checks cover most of your risk.

  • PCI DSS is the card industry's security standard for handling card data. With a hosted or embedded checkout, card data never touches your servers, which greatly reduces your compliance scope. Your provider will tell you which self-assessment applies to you. MoneyHash's announcement states that Thawani holds PCI DSS certification (MoneyHash). That claim comes from a partner, so confirm it, and any provider's certification, by asking for the current attestation.
  • 3-D Secure adds a verification step from the customer's bank, such as an OTP or app approval. It cuts fraud, and in many cases it shifts liability for fraud-related chargebacks away from you. Check that your checkout handles the challenge screen smoothly on mobile.
  • Central Bank of Oman. The CBO regulates payment service providers in Oman. Ask each provider for its licence or authorisation details and check them against the CBO's official website.

Checklist: questions to ask payment providers

Ask every shortlisted provider these questions and get the answers in writing:

  1. Are you licensed or authorised by the Central Bank of Oman? Under what name?
  2. Who is the acquirer, and who settles funds to my account?
  3. Which cards and methods do you accept: Visa, Mastercard, OmanNet, wallets, GCC local schemes?
  4. Do you settle in OMR to an Omani bank account? How often?
  5. What is the full fee schedule, including refunds, chargebacks, reserves and minimums?
  6. What documents do you need, and what does your risk review check on my website?
  7. Do you offer a hosted checkout, an embedded form, an API, and plugins for my platform?
  8. Is the checkout available in Arabic, and does it render correctly right-to-left?
  9. How do webhooks work, and how are retries and signatures handled?
  10. Can I issue partial refunds through the API?
  11. What PCI DSS level do you hold? Can you share your attestation?
  12. What support do you offer in Oman, and in which hours?
  13. What are the contract length, notice period and exit terms?

How AbuData can help

Choosing a gateway is half commercial and half technical, and checkout is where small mistakes cost real orders. AbuData is a Muscat-based studio that designs and builds bilingual Arabic–English e-commerce stores and web platforms. We can help you compare provider documentation, plan the integration and build a checkout that handles OMR, both languages and every refund case correctly. Get in touch to talk through your store.

Frequently asked questions

Can an Omani company use an international payment gateway?

Sometimes, but it depends on whether the provider currently onboards companies registered in Oman and settles in OMR to an Omani bank account. That changes over time, so ask the provider directly and get it in writing. If it doesn't, consider a local gateway, or an orchestration layer that connects to local providers.

Do I need a commercial registration to accept card payments online?

Payment providers generally require a registered business, owner identification and a company bank account before approving you. Requirements differ by provider, so ask each one for its document list. Check any e-commerce licensing rules with the Ministry of Commerce, Industry and Investment Promotion.

How long does payment gateway approval take in Oman?

It varies by provider and depends heavily on how complete your documents and website are. We haven't verified typical timelines, so ask each provider for its current estimate. Leave buffer time before launch, and have your refund, delivery and contact pages live in both languages when you apply.

Should I build my own card form or use a hosted checkout?

Most stores should use a hosted or embedded checkout supplied by the gateway. It keeps card data off your servers, which reduces PCI DSS scope, and the provider handles 3-D Secure. A fully custom direct API integration only makes sense if you have strong security resources and a clear business reason.

Why are my order totals off by a factor of ten?

This is almost always the three-decimal problem. OMR has 1,000 baisa to the rial, so a gateway expecting minor units needs OMR 12.345 sent as 12345. Code written for two-decimal currencies multiplies by 100 instead, which sends one-tenth of the price.

Can one integration cover Oman, Saudi Arabia and the UAE?

Yes, if you use a payment orchestration platform or a regional gateway that supports each market and its local cards. Check that coverage country by country before signing. Planning for this early saves you rebuilding checkout when you expand.

Sources

  1. MoneyHash Advances Its Payment Infrastructure in Oman with Thawani Pay
About the author

AbuData Creative Studio

Digital product studio, Muscat

The AbuData team designs and builds bilingual websites, apps and SaaS platforms for businesses and government entities in Oman and the GCC.

Planning a website, app or platform?

Tell us what you are building. We reply within one business day with next steps and a ballpark.