How does a KNET payment work?
The shopper chooses KNET at checkout and is redirected to the KNET payment page. There they pick their bank, enter their card number, expiry date and PIN, submit and confirm. KNET returns the shopper to the merchant’s success or failure page, and the provider reports the final status. Card details never touch the merchant’s site.
Payments are in Kuwaiti dinars only. KWD uses three decimal places, so APIs that take amounts in minor units divide the amount by 1,000, not 100. At Checkout.com, a payment is voided automatically if the shopper tries to complete it more than seven minutes after landing on the KNET page, and a cancelled or expired payment is reported as its own status.
Providers treat KNET as a straight sale. PayTabs states that authorise-then-capture and recurring transactions are not allowed.
To accept KNET a merchant needs a merchant account with a participating KNET member bank, which issues a merchant ID and credentials. The merchant then registers those credentials with its gateway provider. At PayTabs, Kuwait-based accounts settle KNET payments directly to the merchant’s bank account.
Why does KNET matter for merchants?
KNET is how most Kuwaiti cardholders pay with a debit card. The Mastercard Gateway integration guide for KNET calls it the primary card-based payment method in Kuwait. It says all debit cards issued in the country must carry the KNET brand, and that about 80% of the 5 million cards issued are debit cards. That is roughly 4 million KNET cards.
Online use is growing. KNET reported that transaction volume through online payment gateways rose 13% in its 2024 financial year and transaction values rose 7%, while ATM cash withdrawals fell 14%. The wider market is moving the same way. The Central Bank of Kuwait said in September 2026 that non-cash transactions made up 84% of payments in the first quarter of 2026, up from about 34% in 2010.
KNET also sits under Apple Pay. To process Apple Pay in Kuwait, Checkout.com documentation says the payment must use the KNET network, with the Apple Pay processing certificate added to the KNET payment gateway. A merchant without a KNET route loses both the local card form and Apple Pay for Kuwaiti debit cards.
What can go wrong?
Foreign shoppers cannot use KNET. Providers describe it as accepting local debit cards issued by Kuwaiti member banks, so visitors and customers with foreign cards need an international card option next to it.
Redirect flows lose shoppers. A shopper who lingers hits the seven-minute limit at Checkout.com, and a closed tab can leave the merchant without a browser result. The provider’s server-side status, not the redirect, should decide whether an order is paid.
Refunds need preparation. KNET supports full, partial and multiple partial refunds, but Checkout.com says the merchant must first ask its bank to enable refunds, and the bank then asks KNET to activate the refund function. The gateway guide says refunds cannot be issued more than 90 days after the purchase date, as per KNET guidelines. Checkout.com lists chargebacks as not supported for KNET, so disputes go through the shopper’s bank and the merchant, and clear order records matter.
Sending a KWD amount as if it had two decimal places charges the wrong amount.
How would Omno handle KNET?
Omno would connect to KNET through payment providers. KNET would appear in the hosted checkout as a redirect to the KNET page, or through Direct Links for merchants with their own checkout. The order would stay pending until the shopper completes the KNET page, and the final result would arrive by webhook, which is the source of truth for releasing an order. PSP eligibility rules could send Kuwaiti Apple Pay payments only to providers that process them over KNET. Routing rules set by the merchant would choose the provider, and in the hosted checkout, if a provider is unavailable or rejects the request, the payment would move to the next provider in the rule until one accepts. The routing-decision log records which provider handled each payment.