Payment gateway integration in Qatar, linked to your orders and invoices
Akwad Programming connects the payment gateways used in Qatar, from QPay (Qatar Central Bank), the QNB Payment Gateway and Doha Bank to SkipCash, MyFatoorah and Sadad, to your website, mobile app and ERPNext, so every payment lands on the right order, from checkout to refund.
What our payment gateway integration covers
A payment integration is more than a checkout button. We handle the whole process, from the customer pressing "Pay" to the entry your accountant reviews.
Website checkout
Credit and debit card payments on your website, through the gateway's secure payment page.
In-app payments
Apple Pay, Google Pay and card payments inside your iPhone and Android apps.
Confirmation and status
Successful, failed and cancelled payments handled, with status checks for late confirmations.
Refunds
Refunds sent back through the gateway, where the provider supports them.
Saved cards
The gateway keeps the card safely, so returning customers pay without typing their details again.
Linked to ERPNext
Each payment recorded against its order or invoice, ready for reconciliation.
Why choose Akwad Programming for payment integration in Qatar?
Akwad Programming has connected the QNB Payment Gateway, QPay (Qatar Central Bank), MPGS via Doha Bank, SkipCash, MyFatoorah and Sadad for clients in Qatar, built into their websites, mobile apps and ERPNext.
- Bank gateways delivered: the QNB Payment Gateway (through CyberSource) for Visa and Mastercard, QPay from Qatar Central Bank for debit cards and MPGS (Mastercard Payment Gateway Services) via Doha Bank
- Wallets: Apple Pay and Google Pay
- Local payment providers: SkipCash, MyFatoorah and Sadad
- Built into websites, mobile apps and ERPNext
Which payment gateway should we choose in Qatar?
The right gateway is usually the one your bank or payment provider can give you a merchant account for, that supports the payment methods your customers use, and that works with your platform. In Qatar, the options are bank gateways, local payment providers and digital wallets, and many businesses use more than one.
These are the integrations we have delivered:
| Type | Gateways and wallets |
|---|---|
| Bank gateways | QNB Payment Gateway (Visa and Mastercard through CyberSource), QPay from Qatar Central Bank (debit cards), MPGS (Mastercard Payment Gateway Services) via Doha Bank |
| Local payment providers | SkipCash, MyFatoorah, Sadad |
| Wallets | Apple Pay, Google Pay |
We connect the gateway to your online store, mobile app or ERPNext accounts. If you already bank with one of them, that is often the quickest place to start. If you’re not sure, tell us your platform and the payment methods you need, and we’ll go through the options with you. Our guide to payment gateways in Qatar compared by an integrator explains what each one is and who offers it. Other systems we have connected, from government platforms to messaging, are on our integrations page.
How do you integrate QPay, SkipCash, Sadad or MyFatoorah into a website or app?
Akwad Programming connects each gateway through its secure payment page and API: you open the merchant account, we build and test checkout, status checks and refunds, then go live. We have added QPay to shopping apps, MyFatoorah to CS-Cart apps, and Sadad and SkipCash to Frappe apps.
The steps are the same whichever gateway you choose. We set up the gateway’s test account in your system, build the checkout on your website or app, connect each payment to its order or invoice, and test the cases that go wrong. When your provider activates the live account, we switch over and check the first payments with you.
Why do online payments go wrong, and how do you prevent it?
Most payment problems happen between the customer’s bank and your system, not on the payment page itself: the customer pays, but the confirmation arrives late, or the customer closes the page before returning to your site. The fix is to check each payment’s real status with the gateway, not rely on the customer’s browser.
These are the cases that cause trouble for finance teams:
- Paid but shown as unpaid: the money is taken, but the order still shows unpaid because the confirmation never reached your system.
- Interrupted payments: the customer closes the app or loses signal in the middle.
- Double payments: a customer taps “Pay” twice after a slow response.
- Unclear failures: the bank declines a card, and the customer doesn’t know why.
We handle successful, failed and cancelled payments, and add status checks for late confirmations, so an order is updated when the gateway confirms the payment, even if the customer never came back to the site. Before go-live, we test each of these cases on purpose.
How do payments reach our ERPNext and accounts?
Each payment is recorded against its order or invoice in ERPNext as soon as the gateway confirms it, so your finance team doesn’t match payments to orders by hand. The gateway’s reference is kept with the payment, ready for reconciliation.
Without this link, someone downloads the gateway report, opens the bank statement and searches for each order number. With it, your accountant sees which invoices were paid online, which payments are still pending and which were refunded, all in one place. When the bank settles the money to your account, matching it with the recorded payments is a short check, not a day’s work.
This works the same whether the payment comes from your website, your mobile app or a payment request sent from ERPNext, for example as a payment link sent to the customer by SMS. Order updates and reminders can go out on the WhatsApp Business API.
Is it safe to take card payments on our website and app?
Yes, when the card details are entered on the gateway’s secure payment page rather than on your own servers. That way, your system never stores full card numbers, and most of the card-security burden stays with the gateway, which is certified for it.
A few things add to this:
- Bank verification: the customer’s bank may ask them to confirm the payment with a code or in their banking app (3-D Secure).
- Saved cards: for returning customers, the gateway stores the card and gives your system a token instead of the card number, so customers can pay again without retyping their details.
- Apple Pay and Google Pay: the customer confirms with Face ID, a fingerprint or a PIN, and the card number is not shared with your system.
Your website and app still need to be kept secure, with HTTPS and up-to-date software, because they send customers to the payment page.
What do we need from our bank before a payment gateway integration?
You need a merchant account application with your chosen bank or provider, and the test and live credentials they issue once it’s approved. We can start building and testing with the test credentials while the live account is being activated.
Before we start, we ask for:
- Your platform: website, mobile app, ERPNext, or all three.
- Your chosen bank or provider, and the status of your merchant account.
- The payment methods you want: cards, Apple Pay, Google Pay, saved cards.
- How refunds should work, and who in your team approves them.
The live step depends on your provider. Once they activate the merchant account, we switch to live payments and check the first transactions with you.
How do refunds work through a payment gateway?
Refunds are sent back through the same gateway, from your system, where the provider supports it, and the refund is recorded against the original order. Your team doesn’t need to log in to a separate bank portal or transfer the money by hand.
That keeps your records straight: the order, the payment and the refund sit together, and your accountant can see exactly what was returned and when. For Widam Food, we built checkout through the QNB Payment Gateway (CyberSource) for Visa and Mastercard and through QPay (Qatar Central Bank) for debit cards, with refunds, plus Apple Pay and Google Pay. For General Product Trading, the shopping apps take QPay payments with refunds, and the QNB Payment Gateway. More examples are in our retail and delivery software.
Once you’re live, our support team in Doha helps you by email at support@akwad.qa or on +974 4143 7777, Sunday to Thursday, 8:30 am to 5:30 pm Qatar time.
How we connect your payment gateway in 3 steps
- 01
Choose the gateway
We review your platform, your bank or provider and the payment methods you need, and agree the checkout flow.
- 02
Build and test
We build the integration and test successful, failed, cancelled and interrupted payments.
- 03
Go live
Once your provider activates the merchant account, we switch to live payments and check the first transactions with you.
Payment integrations we’ve delivered in Qatar

Widam Food: Retail & delivery · Payments
- General Product Trading
General Product Trading: Retail · Mobile commerce
Shopping apps with QPay payments and refunds, and the QNB Payment Gateway
Related guides
- Payment Gateways in Qatar Compared by an Integrator
Payment Gateways in Qatar Compared by an Integrator: Guide · Payments
Payment gateway integration in Qatar: common questions
How much does payment gateway integration cost in Qatar?
The cost of payment gateway integration depends on your platform, the gateways and payment methods you need, and features such as refunds, saved cards or the link to ERPNext. We give you a fixed quote after a short review of your needs.
Who pays the payment gateway's fees?
Your bank or payment provider sets its fees in your merchant agreement and charges them to you directly. Our integration work is separate and set out in your quotation.
Can you add QPay or Apple Pay to our mobile app, not only the website?
Yes. Akwad Programming has added QPay, Apple Pay and Google Pay to shopping apps, and each payment is recorded against its order like a website payment. We test the in-app payment with your provider before it goes live.
Can we use more than one payment gateway at the same time?
Yes. Many businesses offer a bank gateway next to wallets, for example cards through a bank gateway and Apple Pay. Customers choose the method at checkout, and every payment is still recorded against the same order, whichever gateway it came through.
Can you add a payment gateway to our existing CS-Cart store or app?
Yes. We have added payments such as MyFatoorah to CS-Cart-based apps, and the same approach works for other gateways your provider supports. We test the new payment method with your existing orders and accounts before it goes live.
Can we send customers a payment link instead of a checkout?
Yes, where your gateway supports payment links. We have sent payment links to customers by SMS, and a link can also go by email. The payment is recorded against the right order or invoice when it's completed.
Can we accept Apple Pay on our website, not only in the app?
Yes, if your gateway supports it. Apple Pay on the web needs a few extra steps, such as registering and verifying your website's domain with Apple, which we handle with you.
Need to take payments online?
Tell us your platform and your bank or provider. We'll come back with a clear plan.