How to accept K-Net payments on a Kuwait website or app

Here is the number that surprises founders. On a 100 KWD order, one Kuwait gateway takes 150 fils from you and another takes 3.000 KWD. Same payment method, same customer, same card. Twenty times the cost.

That gap exists because K-Net is usually priced as a flat fee per transaction, while Visa and Mastercard are priced as a percentage. Most people comparing gateways carry percentage thinking over from card pricing, pick the provider with the friendliest-looking percentage, and quietly overpay on every order for years.

This is the practical version of what accepting K-Net involves: what it actually costs, how you get approved, what the bank will ask you for, and the two things K-Net simply cannot do that break builds when nobody checks first.

What K-Net is, in one paragraph

K-Net is Kuwait's national debit network. It is run by the Shared Electronic Banking Services Company, set up in 1992 in partnership with the local banks, and regulated by the Central Bank of Kuwait. Every debit card a Kuwaiti bank issues runs on it. When you buy something online in Kuwait and the site sends you to a plain page asking for your card number and PIN, that page is K-Net.

It is a debit rail, not a card scheme competing for credit business. K-Net's own gateway page says it "accepts all debit cards issued by the banks". Accepting Visa and Mastercard is a separate contract, usually with the same bank, and it costs different money.

You do not buy K-Net. A bank lets you in

This is the part that catches people out, and it comes straight from K-Net:

1. Contact a local Member Bank, and sign contract to join the service
2. On reception of the request from the Member Bank, the requesting merchant is contacted and provided with an API and documentation for the integration

* Note: KNET does not provide services directly to any merchant or customer

That asterisked note is verbatim from knet.com.kw. There is no signup page. There is no sales team you can email. A Kuwaiti member bank has to sponsor you into the network.

So you have two routes.

Go direct to a bank. NBK, Gulf Bank, Kuwait Finance House, Boubyan, Commercial Bank of Kuwait, KIB and Warba all sell a merchant payment gateway. You get the acquiring relationship and the K-Net connection. What you do not get is developer tooling. Not one Kuwaiti bank publishes API documentation, an SDK, or a plugin for any e-commerce platform. Your developer works from a PDF the bank emails over.

Go through a payment service provider. MyFatoorah, Tap, UPayments, Hesabe, PayTabs, Amazon Payment Services, Sadad and Checkout.com all sit on top of that bank relationship and hand you an API, mobile SDKs, and installable plugins for Shopify, WooCommerce, Magento and the rest. You pay a margin for it.

For most builds the second route is the right one, and it is not close. The exception is a business already doing serious volume through one bank, where a direct rate can beat the provider margin. That is a spreadsheet question, not a principle. If you want the wider view of what goes into a build like this, our website design and development page covers the rest of the stack.

What K-Net actually costs

Almost nobody publishes K-Net pricing. Every Kuwaiti bank routes you to "contact us". MyFatoorah, Tap, PayTabs and Checkout.com all decline to publish a rate. Four providers do publish, and these are their own published figures as of 13 August 2026.

Two notes before you use that table. Hesabe's page labels its column "Max Hesabe Commission" and dates the structure to 29 July 2025, so it is a ceiling rather than a quote, and you should expect to negotiate under it. UPayments prints its K-Net rate as "(0.5% + 100 fils) or (250 fils)" without ever explaining who picks, so ask them directly.

Now run it through a basket.

A flat fee does not care what you sell. A percentage cares enormously. If your average order is 200 KWD of furniture, percentage pricing on K-Net will cost you more than the gateway is worth. If you sell 3 KWD coffee, a 150 fils flat fee is 5% of the order and the percentage deal starts looking reasonable again.

Then add the fixed costs, because they flip the answer at low volume. Amazon Payment Services runs KWD 12 a month plus KWD 120 to set up. Hesabe runs KWD 50 a month plus KWD 500. At 50 orders a month those monthly fees dominate everything the per-transaction rate does.

Work out your real average basket and your real monthly order count first. Then compare. Doing it in the other order is how businesses end up on the wrong contract.

One more thing worth knowing: UPayments states that under Central Bank of Kuwait rules the business bears the transaction fee. You cannot pass a K-Net surcharge to the customer at checkout.

What the bank will ask you for

The document list is consistent across banks and providers:

• Commercial licence from the Ministry of Commerce and Industry
• Extract from the commercial registry
• Articles of association, if you are a company rather than an establishment
• Authorised signatory certificate
• Civil ID of the owner and the authorised signatory, front and back
• IBAN certificate for a Kuwaiti business account, in the exact legal name
• Disclosure of anyone owning 25% or more
• A politically exposed person declaration

UPayments additionally requires you to authenticate through Kuwait's Mobile ID app and to have at least one active social media account.

The part that delays people is not the paperwork. It is the website. Commercial Bank of Kuwait's K-Net gateway agreement lists eleven things that must already be visible on your site before they will process you, including a full description of goods and services, customer service contact details with an email address and phone number, a return and refund policy, a delivery policy, country of origin, a privacy statement, and a statement about when the customer's card is actually debited.

Read that again if you are building. Those pages have to exist and be live before you apply, not after. The same agreement gives the bank the right to send someone to audit your website and security systems, and requires a minimum of 128-bit SSL.

Two clauses in that contract are worth reading properly before you sign. You may not collect money on behalf of third parties without written approval from the bank, which quietly kills a naive marketplace model. And the bank can terminate if you go six months without a transaction, which matters for seasonal businesses.

How long approval takes

Almost nobody publishes a timeframe. The two who do:

• Tap: three business days for merchant approval
• Kuwait Finance House: five to ten business days for a bank e-payment gateway, three to seven for POS

In the builds we have run, the honest answer is that the clock starts later than founders think it does. The bank does not begin until the file is complete, and the file is not complete until the commercial licence, the IBAN certificate in the matching legal name, and a live site with real policy pages all exist together. Plan the payment application as a track that runs in parallel with the build, not as the last ticket before launch.

Two things K-Net cannot do

It cannot bill a subscription

This is the one that breaks builds. K-Net has no merchant-initiated recurring payment. Four providers state it in their own documentation:

• PayTabs: "NO Auth/Cap or Recurring transactions are allowed"
• Tap: "Recurring payments are not supported for certain local payment methods, such as KNET"
• UPayments: K-Net, Apple Pay and other methods "are automatically hidden during a subscription checkout"
• Checkout.com's capability table marks recurring payment, authorization, capture and chargeback as unsupported

K-Net does have a saved-card feature called KFAST, and this is where the confusion starts. KFAST lets a returning customer pick a card they saved on K-Net's own servers instead of typing the number again. The customer still gets redirected to K-Net, and still enters a PIN. It makes repeat checkout faster. It cannot charge a sleeping customer.

If you are building anything with a monthly plan, you need a Visa or Mastercard rail for the recurring charge, with K-Net offered alongside for one-off payments. The alternative some Kuwaiti businesses use is sending a fresh payment link each cycle and asking the customer to pay it, which works but changes your churn maths.

It cannot hold an authorization

There is no auth-and-capture split on K-Net. Every transaction is an immediate sale. Amazon Payment Services puts it plainly: "KNET transactions only support direct capture. Authorization is not supported."

If your product depends on reserving an amount and settling later, a hotel booking, a rental deposit, a marketplace that captures on shipment, that flow does not exist on K-Net. Refunds do work, including partial refunds and multiple partials, so the usual workaround is to charge in full and refund the difference.

What the integration looks like

K-Net is redirect-only. The customer leaves your site, lands on a K-Net-hosted page, enters card and PIN there, and comes back. You cannot build a custom card form and post card numbers to K-Net yourself. PayTabs states it directly: "the payment will be managed and processed on KNET side", and card details never touch the provider's servers.

For a website that is a minor design constraint. For a mobile app it is a real one, because you are handing the user out to a web view mid-flow and bringing them back. Design the return path deliberately, including what happens when the user kills the app on the K-Net page and the transaction is left in limbo. Reconcile against the provider's webhook, never against the redirect.

The rest of the technical picture:

• K-Net settles in Kuwaiti dinars only
• There is no chargeback mechanism the way Visa and Mastercard have one. The Commercial Bank of Kuwait agreement puts the merchant "solely responsible" for delivery disputes, and disclaims the bank entirely
• Settlement is fast by international standards. UPayments settles the next working day, Tap settles K-Net at two business days against five for cards, MyFatoorah within 24 business hours, and Gulf Bank advertises settlement within a day including weekends and public holidays
• Test environments exist, but KFAST is not available in sandbox on any provider, so saved-card behaviour cannot be tested before launch

Apple Pay in Kuwait is K-Net, and that is mostly good news

Worth knowing before you scope it. Accepting Apple Pay online in Kuwait routes through K-Net by mandate. Amazon Payment Services documents it as "a mandate requirement for all Apple Pay transactions in Kuwait", and Checkout.com says "to process Apple Pay payments in Kuwait, you must use the KNET network".

The good news is pricing. Both Hesabe and UPayments charge Apple Pay at the K-Net rate rather than the card rate. In Hesabe's published table that is 2.50% + 0.500 KWD instead of 3.95% + 0.500 KWD.

The catch is that Apple Pay inherits every K-Net limitation. Amazon Payment Services spells it out: K-Net Apple Pay transactions support neither authorization nor recurring operations. So Apple Pay does not give you a way around the subscription problem.

Google Pay works in Kuwait too, and Google publishes no equivalent K-Net mandate for it.

The legal bit, in plain terms

No Kuwaiti law requires you to accept K-Net. The claim gets repeated a lot and it is not true.

What the law does require is that whoever processes your payments is licensed by the Central Bank of Kuwait. Article 28 of Decree-Law No. 10 of 2026 requires providers of goods and services to offer payment options that are simple, transparent and non-discriminatory, and to engage only CBK-licensed payment service providers. Article 39 puts that among the provisions carrying imprisonment of up to a year and a fine of KWD 1,000 to 10,000.

One important qualification, because plenty of articles have it wrong: that law is not yet in force. It was published in the Official Gazette on 1 March 2026, but Article 44 gives the Minister a year to issue the implementing regulations, and Article 45 sets the law running one month after those appear. So the earliest realistic date is after March 2027, and nobody can name it yet. Article-level detail here follows GLA & Company's published analysis of the decree.

None of which is a reason to wait. The Central Bank publishes a public register of licensed e-payment service providers, and you can check any provider against it today, before you sign anything.

Read it carefully, because the list is shorter than you might expect. As of 13 August 2026 it names nine companies, including Tap, UPayments, Hesabe and Sadad. Several providers that sell into Kuwait are not on it. That does not automatically make them a problem, since there are separate registers for e-money providers and payment system operators, and some operate through a licensed Kuwaiti bank rather than holding their own licence. But if your provider is not on any of the three, ask them directly which licence they hold and which Kuwaiti bank they acquire through. Get the answer in writing.

Things people get wrong

Assuming Stripe will do. Stripe does not operate in Kuwait. Its own list of supported countries has one GCC entry, the UAE. Stripe does not support K-Net anywhere in the world and does not process Kuwaiti dinars.

Assuming PayPal covers it. A Kuwait PayPal account can receive money and withdraw to a local bank, though PayPal says that transfer can take up to seven business days. But PayPal has no Kuwaiti dinar, so you would price in US dollars to Kuwaiti customers. That is a conversion problem, a trust problem and a pricing problem in one.

Assuming Shopify handles it. Shopify Payments does not support Kuwait. The Kuwaiti dinar is a perfectly valid Shopify store currency, and K-Net comes in through a third-party app such as MyFatoorah or Hesabe. Budget for the app and check its review count before you rely on it.

Believing that Telr supports K-Net. It does not. K-Net appears nowhere on Telr's own site, and Telr publishes no Kuwait pricing. Adyen dropped K-Net entirely and now labels the page "no longer supported". Comparison articles are still recommending both.

Building the checkout before applying. The bank wants to see live policy pages. Ship those early.

Only offering K-Net. Kuwait has a real credit card population and a real expatriate population with foreign cards. Baymard Institute's research puts "there weren't enough payment methods" behind 9% of cart abandonment, though that sample is American and measures method count rather than a missing local method. Offer K-Net and cards.

Where to start

1. Work out your average order value and your monthly order count. Those two numbers decide flat-fee versus percentage before anything else does.
2. Get quotes from three providers, and make them quote K-Net separately from Visa and Mastercard. If a provider gives you one blended percentage across both, they are hiding something.
3. Check each one against the Central Bank register.
4. Write your terms, refund, delivery and privacy pages and get them live. This is the actual bottleneck.
5. Decide the subscription question now. If any part of your model bills monthly, plan a card rail from day one instead of finding out during integration.
6. Apply in parallel with the build, not after it.

The direction of travel is clear enough. K-Net's own figures for 2024 show online gateway transactions up 13% while ATM cash withdrawals fell 14%, and the World Bank's 2024 Global Findex survey puts debit card ownership among Kuwaiti adults at 70.6%. Your customers are already paying this way. The work is getting the plumbing right.

If you want a hand scoping a Kuwait build with payments in it, talk to us.