How to integrate the KNET payment gateway into Kuwaiti websites and apps

How the KNET payment flow works

KNET is Kuwait's shared debit card network. Checkout.com describes it as a method that lets customers pay with local debit cards issued by Kuwait's member banks. Whichever bank or provider you use, the flow on a website or app has the same shape:

1. The customer picks KNET at checkout. Your server creates a payment request with the amount in KWD, your order reference and two return addresses: one for success and one for failure.
2. The response contains a redirect link. Your checkout sends the customer's browser to that KNET-hosted page.
3. The customer enters their card details and completes the payment on the KNET page. Your site never sees the card number.
4. KNET sends the customer back to your success or failure address.
5. Your server confirms the final status, through a webhook or a status call, and only then marks the order as paid.

Step 5 is the step weak integrations skip. The return address is a browser redirect, so a customer can close the tab, lose signal or land on the success page twice. Treat the webhook or server-side status check as the truth, and make the handler safe to run more than once for the same payment.

Payments also expire. In Checkout.com's KNET implementation, if the customer tries to complete payment more than seven minutes after landing on the KNET page, the payment is voided and a payment_expired webhook is sent. A customer who cancels triggers payment_canceled. Your order model needs a "pending payment" state that can time out cleanly and release reserved stock.

What KNET supports and what it does not

KNET behaves differently from Visa or Mastercard. The table below comes from Checkout.com's KNET feature table and its API-only guide. Other providers can differ: Tap's KNET documentation says authorization is now supported, so ask your provider which of these apply to your account.

Two details are easy to miss. First, Checkout.com says you must contact your bank and ask it to enable refunds before you can process them. Second, KFast does not solve the lack of recurring payments. KFast is KNET's fast-checkout option. In Checkout.com's integration, you pass a card_token with the payment request, and the customer can choose to register for KFast on the KNET page; registration needs a one-time password sent to the mobile number registered with their bank. Checkout.com describes it as a way to speed up returning customers; it does not let you charge them without their involvement.

Apple Pay in Kuwait goes through KNET

According to Checkout.com, to process Apple Pay payments in Kuwait you must use the KNET network. You need three credentials from your acquirer (the Transportal ID, the Transportal password and the encryption key) and an Apple Pay payment processing certificate configured in the KNET portal, following the merchant integration manual KNET provides. Amazon Payment Services calls Apple Pay through KNET a mandate for all Apple Pay transactions in Kuwait and states that these transactions do not support the Authorization command or recurring operations, so the KNET limits above apply to Apple Pay too. Our Apple Pay integration guide covers the web and in-app setup step by step.

KWD has three decimal places

The ISO 4217 currency list gives the Kuwaiti dinar (code KWD, number 414) three minor units, so KD 1 is 1000 in minor units. Code written for dollars or euros usually assumes two decimals, and that assumption breaks KWD amounts.

Checkout.com divides the amount you send for KWD by 1000, so 12750 means KD 12.750. Before you go live, check four places: the amount you send to the gateway, the amount you store on the order, the amount you show on invoices and emails, and any rounding you apply to discounts or delivery fees. If one of them assumes cents, a KD 12.750 order shows up as KD 1.275.

The 5 June 2026 checkout change

KNET announced in May 2026 that from 5 June its payment page would no longer start with a list of banks. According to the Arab Times report of 4 May 2026, KNET said the change would reduce the partial account details the bank list could expose, address the rare cases where card numbers at different banks look alike, keep pace with global developments in digital payments, and make it possible to add foreign banks later. It also said CBK-licensed digital wallets could follow, though officials said there was no concrete timeline.

Kuwait Times reported on 6 June 2026 how the new page works: the customer types the first digits of their card, picks it from a list of matching bank cards with bank logos that narrows as they type, then enters the remaining digits and the expiry date.

Neither report described a change to merchant APIs, but the change affects everything around the payment page:

• Help text, FAQs or screenshots on your site that tell customers to "select your bank" first are now wrong.
• Automated end-to-end tests that click through the KNET page need updating.
• Customer support scripts should match the new screen.

Direct KNET or a CBK-licensed provider

There are two ways to reach KNET: a KNET gateway contract with a Kuwaiti bank, or a CBK-licensed payment provider that offers KNET alongside cards and Apple Pay.

Commercial Bank of Kuwait publishes its KNET gateway contract (version 1.0, March 2022). Other banks' terms may differ, but it shows what a direct relationship involves:

• The merchant may only sell goods and services it owns, and may not collect payments on behalf of other parties (clause 3.7). A marketplace paying out to many sellers does not fit this model.
• Collected funds are transferred on the day after the payment (appendix, item 12).
• Fees and commissions are set in the application form, and the bank can change them with at least one month's written notice (clause 5.1).
• The merchant is responsible for securing any stored card data to the PCI DSS standard, and the bank may have the website and its security reviewed.
• The contract runs for a year and renews automatically, and it can be terminated if no transaction passes through the KNET gateway for six months (clause 10.1.5).

What a direct bank integration looks like

With a direct contract, your bank issues a Tranportal ID, a Tranportal password and a terminal resource key. (Checkout.com's Apple Pay guide spells these "Transportal" and calls the key an encryption key.) KNET runs a test endpoint, kpaytest, separate from the production endpoint, kpay. Your server builds the payment request with these credentials and redirects the customer. When the payment finishes, KNET sends a POST to your response URL; gateway or processing errors go to your error URL instead. A successful payment comes back with the result CAPTURED, and anything else is a failure.

These details come from an unofficial open-source .NET port of KNET's PHP sample, which its author describes as a proof of concept. Use the official merchant kit your bank provides as the reference.

The provider route

A provider trades some control for speed and breadth. CBK keeps separate registers. Its e-payment services providers register lists nine companies, of which Tap Payments, UPayments and Hesabe are classed as large providers. MyFatoorah appears on CBK's e-money services providers register as a large e-money service provider, and we cover the MyFatoorah integration on its own page. KNET itself is the only entry on CBK's register of e-payment services operators.

KNET fees are not standardised. Banks set them in each merchant's application form (clause 5.1 above), and providers price by plan. Some publish their rates: on 27 September 2026, UPayments' pricing page listed KNET at "(0.5% + 100 Fils) OR (250 Fils) per Transaction" on its Single Merchant and Multi Merchant plans, which also carry a one-time plan fee (KD 250 and KD 700). Our guide to payment gateways in Kuwait lists the licensed providers and the fees they publish. Get the full schedule in writing and model it on your expected order volume.

What your website needs before approval

The same contract lists what must be clearly shown on the merchant's website, a good pre-launch checklist whichever route you take:

• An accurate description of each product or service
• Full contact details, including email and phone numbers
• Return, refund and cancellation policies
• Delivery policy
• Country of origin and any export restrictions
• A privacy policy and a statement on how cardholder data is protected
• When the card will be charged and how orders are fulfilled
• A note encouraging customers to keep their transaction receipt

Kuwait's digital commerce rules add their own requirements. Our digital commerce law website checklist maps them to pages and features. This page is a technical guide, not legal advice.

KNET on Shopify, WooCommerce, Magento or Salla

On an off-the-shelf store you rarely write KNET code yourself. You install the plugin or app of a licensed provider that offers KNET, then enter that provider's keys. For example, Tap's developer docs list plugins for WooCommerce, Magento and OpenCart, plus two Shopify apps (a native one and a redirect one), and Salla's help centre documents a KNET connection through Tap. Check your chosen provider's own plugin list.

A custom build makes sense when you need your own order logic, a mobile app on the same checkout, or orders that start in WhatsApp. Our guide on how to start an online store in Kuwait compares both paths.

KNET in mobile apps

KNET's redirect flow works inside an app, but it needs care. Open the KNET page in an in-app browser rather than a bare web view where possible, send the customer back to the right screen through a deep link or universal link, and confirm the result on your server before showing "payment successful". If the customer switches apps mid-payment, the app should check the order status when it returns to the foreground instead of assuming failure.

Amazon Payment Services' documentation applies the KNET requirement to all Apple Pay transactions in Kuwait, so plan for Apple Pay inside an iOS app to be processed over KNET too. Check with your provider how it supports this in apps: Amazon Payment Services' documentation, for example, lists Hosted Checkout and Custom Integration for Apple Pay via KNET, and does not list its mobile integration.

KNET payment links in WhatsApp

If your customers already order through WhatsApp, a KNET payment link fits that conversation: the customer confirms the order in chat, opens the link, pays on the KNET page, lands on your confirmation page and goes back to the chat.

Waslo, Rukn's own messaging platform, takes the order in the chat and sends a KNET payment link from the business's own licensed gateway account; the funds settle directly to the business, never through Rukn. Its AI agent answers from the business's own knowledge base. As a hypothetical example, a restaurant taking 40 WhatsApp orders a night could send a KNET link for each confirmed order instead of collecting cash on delivery. Our WhatsApp Business API integration guide explains the messaging side.

Testing KNET without real money

Each route has its own test data, and providers can change it:

• Direct bank integrations: your acquiring bank issues test Tranportal credentials for KNET's test environment (kpaytest).
• Checkout.com: your account manager or integrations engineer must activate KNET in your sandbox, and its KNET API guide lists the sandbox test card to use. According to the same guide, KFast registration cannot be tested in the sandbox because it needs a real one-time password.
• Tap Payments: see Tap's testing cards reference.
• MyFatoorah: see MyFatoorah's test cards page.

Test the unhappy paths as hard as the happy one: a cancelled payment, an expired payment, a customer who closes the tab, a double webhook and a partial refund.

Common KNET integration mistakes

• Marking the order paid from the browser return alone, without a server-side check.
• Sending amounts with two decimals, or formatting KD prices as KD 12.75.
• Promising "pay later" or pre-authorization holds before your provider confirms it supports them for KNET.
• Launching before the refund, delivery and privacy pages the bank expects are live.

How we build KNET checkouts

Rukn is a Kuwait-based team. When we build a KNET checkout, we design the pending-payment state, server-side confirmation, three-decimal amounts, refunds from the admin panel and bilingual receipts from the start, not as a patch after launch. Our website development service covers the full build, from checkout to hosting. Websites start from KD 799, and the final quote depends on scope. If you already have a bank or provider account, send us your checkout requirements and we will map the flow before quoting.