Online stores with KNET payments · Tech Labs

KNET integration for your online store in Kuwait: the practical guide

Most people who ask about KNET integration think of it as a single step. In practice it is two tracks: a short technical track, and an administrative and paperwork track that decides the real timeline. Here we explain both, and what we do for you.

• We connect KNET through a Kuwaiti payment provider
• Arabic and English store
• Admin panel

No website yet? See how to create a KNET payment link: what it is, who can get one, and the steps.

Why KNET specifically?

KNET is the shared payment network of the Kuwaiti banks, and it accepts debit cards issued by the member banks inside Kuwait. It is the main payment method for most online shoppers in Kuwait. In practice, this means a store that does not accept KNET loses a large share of local buyers, however good its design is.

Two routes: through a bank, or through a payment service provider?

This is the first decision, and it affects cost and timeline more than any technical choice that follows.

	Directly through a member bank	Through a payment service provider
Contract	With the bank, then receiving the documents and modules from KNET	With the provider only
Activation speed	Slower: bank procedures	Usually faster
Technical effort	Higher	Lower: APIs and ready-made modules
Fees	Often lower in the long run	A fee per transaction
Best for	Large, stable sales volume	A quick launch and new stores

Well-known payment service providers in the Kuwaiti market include Tap Payments (licensed as an electronic payment service provider by the Central Bank of Kuwait), MyFatoorah and UPayments. Choosing between them comes down to fees, settlement terms and the quality of support, and those change, so ask for an up-to-date offer rather than relying on old published figures.

Paperwork requirements

• A valid commercial licence and company documents. Unlicensed or home-based businesses may face rejection or tougher conditions.
• A bank account in the business's name to receive settlements.
• A clear description of the business and its products; the providers review the nature of the business before approval.
• A website that actually works, and usually privacy policy, terms of use and refund policy pages.

Technical requirements

• HTTPS on port 443 and a valid SSL certificate. This is a basic requirement that cannot be skipped.
• A fixed domain owned by the business; no free trial domains.
• Clear success and failure pages, and correct handling of the "payment not completed" case.
• Recording the transaction reference in the database before redirecting the customer to the gateway, not after.
• Verifying the transaction result on the server side; never rely on what comes back in the browser alone.

Implementation steps, in order

1. Choose the route (bank or payment service provider).
2. Submit the application and documents, and get a merchant account.
3. Receive the integration details and the test keys.
4. Do the integration and test every case in the sandbox: success, failure, cancellation, interruption.
5. Move to production once the tests are approved.
6. Run a real transaction with a token amount before launching to the public.

How long it takes

The programming part through a payment service provider is usually completed within a few working hours to a few days, depending on how complex the store is. The approval and paperwork period varies from one provider to another and is outside the developer's control. That is why we do not promise a final activation date: we commit to the part we control, and we are honest about the rest.

Payment gateway or payment link: what is the difference?

A payment gateway is the service that passes a KNET or card transaction between your customer and the bank, whether you connect it to your store or use it without a website. A payment link is the simplest form of it: a link for a set amount that you send to the customer on WhatsApp; they open it and pay with KNET.

Payment links in short

You open a merchant account with a payment service provider or bank (they usually ask for a valid commercial licence), and once it is active you create a link for a set amount from its dashboard and send it to the customer. See the step-by-step payment link guide.

When is a payment link enough, and when do you need a store with a payment gateway?

If you have few orders and they come through WhatsApp or Instagram, a payment link is enough to start. Once you have many products and daily orders, a store connected to a payment gateway saves you sending links by hand, and every order is recorded with its status in the admin panel. Details are on the online store design page.

Common mistakes we see

• Relying on the payment result as it comes back in the browser, without server-side verification: a loophole that lets unpaid orders be confirmed.
• Not handling the case where the customer closes the page during payment, so the order stays pending with no clear status.
• Not recording the transaction reference before the redirect, which makes reconciling settlements later difficult.
• Testing only the success case and ignoring failure and cancellation.
• Leaving the checkout page without clear Arabic messages, so the buyer hesitates at the last moment.

Prefer a call back?

Leave your number and we will call you during working hours, with no commitment.

Your WhatsApp or mobile number

Call me back

Note: fees and activation terms change between providers and over time. This guide explains the general mechanism and is not a substitute for an up-to-date official offer from the bank or payment service provider.