Short answer first. To accept K-Net you need a Kuwaiti commercial licence and a Kuwaiti business bank account, plus a contract with either a Kuwaiti bank or a payment gateway that sits on top of one (Tap, UPayments, Hesabe, MyFatoorah and a few others). Approval takes three business days to a couple of weeks once your paperwork is complete. Fees run from 0.150 KWD flat to 2.50% plus 0.500 KWD per order, depending on who you sign with.
That last number is where most businesses lose money. On a 100 KWD order, one gateway takes 150 fils and another takes 3.000 KWD. Same customer, same card. Twenty times the cost.
Below is the full version: the two routes in, what it really costs, what the bank will ask for, how it works inside a mobile app, and the two things K-Net cannot do that break builds when nobody checks first.
What you need before you start
- A commercial licence from the Ministry of Commerce and Industry
- A Kuwaiti business bank account, with an IBAN certificate in the exact legal name on the licence
- A website or app with real policy pages already live (more on this below, it is the usual bottleneck)
- A decision on who you sign with: a bank directly, or a gateway
If you are missing the first two, stop here and sort those out. Nothing else moves without them.
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 with the local banks and regulated by the Central Bank of Kuwait. Every debit card a Kuwaiti bank issues runs on it. When you pay online in Kuwait and land on a plain page asking for your card number and PIN, that page is K-Net. Visa and Mastercard are a separate contract, usually with the same bank, at a different price.
You don't sign up for K-Net. A bank lets you in
This is the part that surprises people, and it comes straight from K-Net's own payment gateway page: you contact a local member bank and sign a contract, the bank passes your request on, and only then do you get the API and documentation. The page ends with a note in plain words: "KNET does not provide services directly to any merchant or customer".
There is no signup form and no sales team. A Kuwaiti bank has to sponsor you. That leaves two routes.
Route 1: directly through 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. You do not get developer tooling. None of the Kuwaiti banks publish API docs, an SDK or a plugin. Your developer works from a PDF the bank emails over.
Route 2: through a payment gateway
Tap, UPayments, Hesabe, MyFatoorah, PayTabs, Amazon Payment Services, Sadad and Checkout.com hold the bank relationship and hand you an API, iOS and Android SDKs, and plugins for Shopify and WooCommerce. You pay a margin for that. Checkout.com is worth a note: its K-Net page says "Gateway only. Direct contract with local provider required", so you still end up signing with a Kuwaiti acquirer.
For most builds the gateway route wins, and it is not close. The exception is a business already doing real volume through one bank, where a direct rate can beat the gateway margin. That is a spreadsheet question, not a principle. If you are still picking the store platform itself, our breakdown of Shopify, WooCommerce or custom for the GCC covers which ones have decent K-Net plugins.
Can you accept K-Net without a Kuwaiti company?
No, and this is one of the most searched versions of the question. K-Net only admits merchants through a Kuwaiti member bank, the bank settles in Kuwaiti dinars to a Kuwaiti business account, and that account has to match the legal name on your commercial licence. Tap's own support page says it flatly: K-Net "is only available for merchants based in Kuwait".
A foreign business has two honest options. Set up a Kuwaiti entity, or sell through a Kuwaiti business that holds the contract. The second one has a catch: Commercial Bank of Kuwait's K-Net agreement bans collecting money on behalf of third parties without the bank's written approval. So "my Kuwaiti partner takes the payments for me" needs the bank's sign-off, not a handshake.
What K-Net really costs
Almost nobody publishes K-Net pricing. Every Kuwaiti bank says "contact us". So do MyFatoorah, Tap, PayTabs and Checkout.com. Four providers do publish, and these are their own figures, rechecked in September 2026.
| Provider | K-Net rate | Setup | Monthly |
|---|---|---|---|
| Amazon Payment Services | KWD 0.150 per transaction | KWD 120 | KWD 12 |
| UPayments | 250 fils per transaction, or 0.5% + 100 fils | KWD 250 | not published |
| Sadad Kuwait | 350 fils per transaction, or 1.75% + 100 fils | not published | not published |
| Hesabe | up to 2.50% + 0.500 KWD | KWD 500 | KWD 50 |
Two notes on that table. Hesabe labels its column "Max Hesabe Commission", so treat it as a ceiling and negotiate under it. UPayments prints "(0.5% + 100 fils) or (250 fils)" without saying who picks, so ask them.
Now run it against real order sizes:
| Order value | Amazon PS | UPayments | Sadad | Hesabe |
|---|---|---|---|---|
| 3 KWD | 0.150 | 0.250 | 0.350 | 0.575 |
| 20 KWD | 0.150 | 0.250 | 0.350 | 1.000 |
| 100 KWD | 0.150 | 0.250 | 0.350 | 3.000 |
| 300 KWD | 0.150 | 0.250 | 0.350 | 8.000 |
A flat fee doesn't care what you sell. A percentage cares a lot. Sell 200 KWD sofas and percentage pricing on K-Net will eat you. Sell 3 KWD coffee and a 150 fils flat fee is 5% of the order, so the percentage deal starts to look fine.
Then add the fixed costs, because at low volume they flip the answer. At 50 orders a month, Hesabe's KWD 50 monthly fee costs you a dinar per order before a single transaction fee.
So work out two numbers first: your average order value and your monthly order count. Compare gateways after that, never before.
One more rule: UPayments notes that under Central Bank of Kuwait rules the business pays the transaction fee. You can't add a K-Net surcharge at checkout.
What the bank will ask you for
The document list is close to identical across banks and gateways:
- Commercial licence
- Commercial registry extract
- Articles of association, if you're a company rather than an establishment
- Authorised signatory certificate
- Civil ID of the owner and the signatory, front and back
- IBAN certificate in the licence's legal name
- Disclosure of anyone owning 25% or more
- A politically exposed person declaration
UPayments also wants you to verify through Kuwait's Mobile ID app and to have at least one active social media account.
The paperwork rarely causes the delay. The website does. Commercial Bank of Kuwait's K-Net gateway agreement lists eleven things that must already be visible on your site before they'll process you: a full description of what you sell, customer service contact details with email and phone, a return and refund policy, a delivery policy, country of origin, a privacy statement, and a line explaining when the customer's card is actually charged, among others. The bank can also audit your site and security, and requires at least 128-bit SSL.
Read that as a build requirement. Those pages go live before you apply, not in launch week.
Two more clauses to read before signing. The third-party collection ban above quietly kills a naive marketplace model. And the bank can end the contract after six months with no transactions, which matters if you're seasonal.
How long K-Net approval takes
Only two providers publish a figure:
- Tap: three business days for merchant approval
- Kuwait Finance House: five to ten business days for a bank e-payment gateway
The code is rarely the slow part. On the Kuwait builds we've shipped, the delay comes from the clock starting later than the founder expected. Nobody at the bank starts until the file is complete, and the file isn't complete until the licence and matching IBAN certificate sit alongside a live site with real policy pages. So run the payment application alongside the build, not as the last ticket before launch. Our guide on how long a website takes to build in Kuwait shows where it fits in the full schedule.
K-Net on a website vs in a mobile app
K-Net is redirect-only. The customer leaves your checkout, lands on a page K-Net hosts, enters card and PIN there, and comes back. You cannot build your own card form and post card numbers to K-Net. PayTabs puts it simply: "the payment will be managed and processed on KNET side".
On a website that's a small design constraint. In a mobile app it's a bigger one, because you hand the user to a web view mid-purchase and have to bring them back. Plan for the ugly cases: the user kills the app on the K-Net page, or loses signal halfway. If your app decides success from the return screen, some of those orders will show as failed when the money has already moved.
The fix is one rule: trust the gateway's server notification, never the redirect. In practice it looks like this.
// Pattern only. Field names differ by gateway, check your provider's docs.
// 1. The redirect back to your site/app just shows a "checking payment" screen.
app.get("/payment/return", (req, res) => {
res.render("checking-payment", { orderId: req.query.orderId });
});
// 2. The gateway's webhook is the only thing that marks an order paid.
app.post("/payment/webhook", verifyGatewaySignature, async (req, res) => {
const { orderId, status, amount } = req.body;
const order = await Orders.find(orderId);
if (status === "CAPTURED" && amount === order.total) {
await order.markPaid();
}
res.sendStatus(200);
});
A few other things change the build:
- K-Net's page changed on 5 June 2026. Customers no longer pick their bank from a list, they type the card number straight in. If your help pages or QA scripts still say "select your bank", update them.
- K-Net settles in Kuwaiti dinars only.
- Settlement is fast. UPayments pays out the next working day, Tap settles K-Net in two business days against five for cards, MyFatoorah within 24 business hours.
- There's no chargeback system like Visa and Mastercard have. Commercial Bank of Kuwait's agreement makes the merchant "solely responsible" for delivery disputes.
- Every gateway offers a test environment, but KFAST saved cards don't work in any sandbox, so that flow can't be tested before launch.
If you're still choosing how to build the app itself, see React Native, Flutter or native for Kuwait.
Two things K-Net cannot do
It can't bill a subscription
This is the one that breaks builds. K-Net has no merchant-started recurring payment, and four providers say so in their own docs:
- 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 marks recurring payment, authorization, capture and chargeback as unsupported
KFAST, K-Net's saved-card feature, is where people get confused. It lets a returning customer pick a card saved on K-Net's servers instead of typing it again. They still get sent to K-Net and still enter a PIN. Faster repeat checkout, yes. Charging a customer while they sleep, no.
Anything with a monthly plan needs a Visa or Mastercard rail for the recurring charge, with K-Net offered next to it for one-off payments. Some Kuwaiti businesses send a fresh payment link each cycle instead. It works, but it changes your churn numbers.
It can't hold an authorization
Every K-Net transaction is an immediate sale. Amazon Payment Services: "KNET transactions only support direct capture. Authorization is not supported."
So a hotel deposit, or a marketplace that charges on shipment, has no K-Net version. Refunds do work, including several partial refunds on one payment, so the usual workaround is to charge in full and refund the difference.
Apple Pay in Kuwait runs on K-Net
Worth knowing before you scope checkout. Apple Pay online in Kuwait goes through K-Net by mandate. Amazon Payment Services calls it "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 upside is price. Hesabe and UPayments both charge Apple Pay at the K-Net rate rather than the card rate. On Hesabe's published table that's 2.50% + 0.500 KWD instead of 3.95% + 0.500 KWD.
The downside is that Apple Pay inherits every K-Net limit, so no subscriptions and no authorizations through Apple Pay either.
Is K-Net required by law?
No Kuwaiti law requires you to accept K-Net. That claim gets repeated a lot and it's wrong.
What the law requires is that your payment provider is licensed by the Central Bank of Kuwait. Article 28 of Decree-Law No. 10 of 2026 says sellers may only use CBK-licensed payment service providers, and Article 39 attaches up to a year in prison and a KWD 1,000 to 10,000 fine. The law isn't in force yet: Article 44 gives a year for implementing regulations and Article 45 starts the clock a month after those appear, so the earliest date is after March 2027. Article-level detail follows GLA & Company's analysis.
You don't need to wait for it. The Central Bank publishes a register of licensed e-payment service providers and you can check any gateway against it today. When we checked in August 2026 it named nine companies, including Tap, UPayments, Hesabe and Sadad. Some gateways that sell into Kuwait aren't on it, which isn't automatically a problem: there are separate registers for e-money providers and payment system operators, and some gateways work through a licensed bank. If yours is on none of them, ask which licence they hold and which Kuwaiti bank they acquire through, and get the answer in writing.
Mistakes we see on Kuwait checkouts
Assuming Stripe will do it. Stripe doesn't operate in Kuwait, doesn't support K-Net anywhere, and doesn't process Kuwaiti dinars.
Assuming Shopify Payments covers it. Shopify Payments doesn't operate in Kuwait. KWD works fine as a store currency, and K-Net comes in through an app such as MyFatoorah or Hesabe. Check the app's reviews before you rely on it.
Using PayPal instead. A Kuwaiti PayPal account can receive money, but PayPal has no Kuwaiti dinar, so you'd be charging Kuwaiti customers in US dollars.
Trusting old comparison articles. Telr doesn't support K-Net, and Adyen now marks it "no longer supported". Plenty of 2024 listicles still recommend both.
Building checkout before applying. The bank wants live policy pages. Ship those in week one.
Offering K-Net only. Kuwait has a large expat population with foreign cards, plus plenty of local credit card users. Offer K-Net and cards.
Where to start this week
- Write down your average order value and monthly order count. Those two numbers decide flat fee versus percentage.
- Get quotes from three gateways, with K-Net priced separately from Visa and Mastercard. A single blended percentage across both is a red flag.
- Check each gateway against the Central Bank register.
- Get your terms, refund, delivery and privacy pages live.
- Decide the subscription question now. If anything bills monthly, plan a card rail from day one.
- Apply while the site or app is being built, not after.
Your customers already pay this way. K-Net's own 2024 figures show online gateway transactions up 13% while ATM cash withdrawals fell 14%. The job is getting the plumbing right the first time.
If you're planning a Kuwait website or app with payments in it and want someone who has wired K-Net before, talk to us.
Frequently asked questions
How do I accept K-Net payments on my website?
Sign with a payment gateway such as Tap, UPayments, Hesabe or MyFatoorah, or directly with a Kuwaiti bank. The gateway route gives you an API, mobile SDKs and plugins for Shopify and WooCommerce. Either way you need a Kuwaiti commercial licence, a Kuwaiti business bank account and live refund, delivery and privacy pages before you apply.
Can I accept K-Net without a Kuwaiti company or bank account?
No. K-Net only admits merchants through a Kuwaiti member bank, and the bank settles in Kuwaiti dinars to a Kuwaiti business account in your company's legal name. Tap states K-Net is only available for merchants based in Kuwait. A foreign business needs a Kuwaiti entity, or has to sell through a Kuwaiti business that holds the contract.
How long does K-Net integration take?
Approval is the slow part, not the code. Tap publishes three business days for merchant approval and Kuwait Finance House publishes five to ten business days for a bank e-payment gateway. The clock only starts once your licence and bank certificate are in and your policy pages are live, so apply while the site is being built.
How much does K-Net cost per transaction?
As of September 2026 four providers publish a K-Net rate. Amazon Payment Services charges KWD 0.150, UPayments 250 fils, Sadad 350 fils, and Hesabe up to 2.50% plus 0.500 KWD. Banks, MyFatoorah, Tap and PayTabs quote privately. Under Central Bank of Kuwait rules the merchant pays the fee, not the customer.
Does K-Net work in mobile apps?
Yes. Gateways such as Tap and MyFatoorah provide iOS and Android SDKs. K-Net is redirect-only, so the app opens K-Net's hosted page, the customer enters card and PIN there, and returns. Confirm the payment from the gateway's server-side notification, never from the app's return screen.
Does K-Net support subscriptions or recurring billing?
No. PayTabs, Tap, UPayments and Checkout.com all state in their documentation that K-Net does not support recurring payments. The saved-card feature KFAST still sends the customer to K-Net to enter a PIN. A subscription business in Kuwait needs a Visa or Mastercard rail for the recurring charge.