How to accept Apple Pay in Kuwait: the KNET rules, web and app setup

Accepting Apple Pay as a merchant in Kuwait has one local rule: according to payment providers' documentation, Apple Pay here is processed through KNET, so you need a payment gateway or acquirer that processes Apple Pay through KNET. Either you or that gateway also holds an Apple merchant ID and a payment processing certificate, and a website adds a merchant identity certificate and a verified domain. The KNET route changes what you can build, mainly around capture and recurring charges. This is a technical guide from a software team, not banking or legal advice, so confirm the details with your gateway before you design checkout.

How Apple Pay works for merchants in Kuwait

Kuwait adds one rule. Amazon Payment Services states that Apple Pay through KNET is a mandate for all Apple Pay transactions in Kuwait, and Checkout.com's documentation says that to process Apple Pay payments in Kuwait you must use the KNET network.

In practice, one payment looks like this:

1. The customer taps the Apple Pay button in your app or on your site and confirms with Face ID, Touch ID or the device passcode.
2. Apple returns an encrypted payment token to your app or page.
3. Your server, or your payment gateway, sends that token for processing through KNET in KWD.
4. KNET and the customer's bank approve or decline, and your gateway reports the result back to your system.

On the customer side, Apple's list of participating banks, checked on 27 September 2026, names 11 issuers for Kuwait: Al Ahli Bank of Kuwait, American Express, Boubyan Bank, Burgan Bank, Commercial Bank of Kuwait, Gulf Bank, Kuwait Finance House, Kuwait International Bank, National Bank of Kuwait, Warba Bank and Weyay Bank.

What the KNET route changes in your build

The Amazon Payment Services page on Apple Pay through KNET lists two limits. Each one has a product consequence.

The same page advises creating a new Apple merchant identifier for the KWD account when moving to KNET, because using your existing merchant ID to create the KNET payment processing certificate also affects your existing sandbox or production payments. This is a setup recommendation, not a KNET limit: Apple's documentation says most merchants need only one merchant ID.

APS also says that, for KNET Apple Pay, its merchants can only use Hosted Checkout or Custom Integration. Its mobile SDK integration is not listed for this route. If you planned a fully native checkout on that provider, check this first.

Checkout.com adds two useful details:

• You need three KNET credentials from your acquirer: Transportal ID, Transportal password and encryption key. If you already process KNET through Checkout.com, you can reuse the credentials they gave you.
• Unlike other regions, you do not convert the Apple Pay token into a card token. You send Apple's paymentData object as token_data and the paymentMethod object as payment_method_details, with the currency set to KWD. The webhooks listed for this route are payment_pending, payment_captured and payment_declined.

Other gateways may word these limits differently or build their own options on top. Ask yours, in writing, which Apple Pay operations it supports for Kuwaiti cards (purchase, refund, recurring) before you design checkout, refunds or billing around them.

What Apple Pay costs a merchant in Kuwait

Your gateway charges per transaction, and the rate can depend on the card behind Apple Pay. For example, UPayments' published pricing, checked on 27 September 2026, lists Apple Pay on a KNET card at the same rate as KNET, (0.5% + 100 fils) or (250 fils) per transaction, and Apple Pay on a credit card at 2.75% + 100 fils, on plans that also carry a one-time plan fee (KD 250 or KD 700). Ask your gateway for both figures in writing. Our guide to payment gateways in Kuwait lists the fees that providers publish.

Apple Pay on a website vs inside an iOS app

Both routes start with the same Apple setup. According to Apple's developer documentation, the merchant ID identifies your business as a merchant able to accept payments. It never expires and can be used on several websites and iOS apps. The payment processing certificate secures transaction data: Apple Pay servers encrypt payment data with its public key, and you or your payment service provider decrypt it with the private key.

The web needs two more pieces:

Domain verification on the web

Apple requires you to register and verify every top-level domain and subdomain where the Apple Pay button appears. Domains cannot sit behind a proxy or redirect, and Apple's servers must be able to reach the verification file. The URL has this form: https://yourdomain.com/.well-known/apple-developer-merchantid-domain-association. If your site redirects the bare domain to www, verify the host that actually serves the checkout page. On the web, Apple Pay runs through the Apple Pay JS API or the Payment Request API.

Letting your gateway handle the Apple side

You do not always need your own Apple Developer setup for the web. Tap Payments' Apple Pay Web SDK documentation says Tap registers the merchant's domain with Apple Pay on the merchant's behalf, and payments are processed with Tap's Apple Pay certificate, so you do not need access to the Apple Developer portal or to exchange CSR and CER files. You still host the domain association file at the .well-known path, give Tap every domain and subdomain in advance, and use the merchant ID Tap provides.

That is faster to start. The trade-off is ownership. According to Apple's documentation, each verified domain is associated with one Apple Developer Team ID, and the same domain cannot be registered under a different Team ID. Before you switch gateways, ask the old one to remove your domain from its Apple registration, then redo the Apple Pay setup with the new provider. Provider-specific steps are in our Tap Payments integration guide and our MyFatoorah integration guide.

Setting up Apple Pay via KNET with your own merchant ID

If you process through KNET with your own Apple Developer account, the Amazon Payment Services guide describes the sequence below. These are APS's steps for merchants moving existing Apple Pay processing onto KNET; other gateways may differ.

1. Log in to the KNET merchant portal. The test portal is on kpaytest.com.kw and production is on kpay.com.kw.
2. In Terminal Settings, generate and download a certificate signing request (CSR).
3. In your Apple Developer account, create a merchant identifier for the KWD account. APS advises a new one, because reusing an existing ID for this certificate also affects your existing payments.
4. Use the KNET CSR to create the payment processing certificate for that merchant ID.
5. Upload the resulting .cer file back to the KNET portal.
6. Update your application so Apple Pay transactions map to the new sub-account. APS creates a separate production sub-account for Apple Pay (KWD).

Checkout.com tells merchants to ask KNET for its Apple Pay Merchant Integration Manual and follow the section on adding the Apple Pay payment processing certificate to the payment gateway. Test with your acquirer's credentials in KNET's sandbox before going live.

For a web checkout, add the merchant identity certificate and domain verification from the section above. For an iOS app, add the Apple Pay capability in Xcode and select the merchant ID. Our KNET integration guide covers the wider KNET setup that Apple Pay sits on.

What this means for subscriptions and pre-orders

Here the KNET route matters most.

Digital subscriptions inside an iOS app

If your iOS app sells access to features or content, such as a premium tier or paid lessons, Apple's App Review Guideline 3.1.1 requires in-app purchase. On the Kuwait App Store, that means digital content is sold through in-app purchase, not Apple Pay inside the app. Guideline 3.1.3(e) points the other way: physical goods, or services consumed outside the app, must use a method other than in-app purchase, such as Apple Pay or card entry.

Subscriptions for physical goods and services

A meal-plan box, a gym membership or a monthly cleaning contract can take Apple Pay. Amazon Payment Services states that KNET Apple Pay transactions do not support recurring operations, so on that route you cannot save the Apple Pay token and charge it automatically each cycle. Ask your gateway in writing whether it offers any recurring Apple Pay option for Kuwaiti cards. Until it confirms one, three patterns work:

• Pay per cycle. Before each renewal, send a payment link or an in-app prompt, and the customer pays again with Apple Pay.
• Prepaid terms. Sell 3, 6 or 12 months up front as one payment.
• Card on file for renewals. Take the first payment with Apple Pay and offer card billing for renewals, only if your gateway confirms it supports saved-card charges in Kuwait. That is a separate product from Apple Pay.

For example, a hypothetical meal-plan business could send a renewal link three days before each cycle and pause deliveries until it is paid.

If your iOS app uses Apple Pay for recurring payments, Guideline 4.9 requires you to disclose the length of the renewal term and that it continues until cancelled, what is provided in each period, the actual charges, and how to cancel.

Pre-orders, deposits and changing totals

On a route without the Authorization command there is no "hold now, capture when it ships". The practical options:

• Charge the full amount when the order is placed, and refund if it is cancelled. Confirm how your gateway handles refunds on Apple Pay via KNET before you promise a refund timeline.
• Charge a fixed deposit now, and collect the balance as a second payment when the item is ready.
• For totals that change after checkout, such as weighed groceries or custom work, confirm the final amount before payment, or collect the difference as a separate payment.

Keeping Apple Pay working after launch

Apple Pay stops working without warning when one of these lapses. From Apple's maintenance documentation:

• The payment processing certificate expires every 25 months.
• The merchant identity certificate expires every 25 months.
• Domain verification expires when the domain's SSL certificate expires. Apple checks for a renewed SSL certificate 30, 15 and 7 days before expiry. If the SSL certificate lapses, you must verify the domain again.
• Apple emails expiry reminders to the Admin and the Account Holder of the developer account.

Three rules follow:

1. Register the Apple Developer account to the company, not to a freelancer or to an employee's personal Apple ID.
2. Put certificate and SSL renewal dates in the same calendar as your trade licence and domain renewals.
3. On the KNET route, the certificate is created from a CSR generated in the KNET portal. Plan to repeat that exchange at renewal, and confirm the exact steps with KNET or your acquirer.

Before you go live

1. Run test payments in KNET's sandbox with your acquirer's test credentials.
2. Pay on a real iPhone with a Kuwaiti card in Wallet, then run a refund.
3. Confirm the host that serves checkout (with or without www) is the one you verified.
4. In an iOS app, show all material purchase information before the sale and use Apple Pay branding and interface elements as Apple's guidelines describe (Guideline 4.9).

Choosing a route

If you are budgeting a new app, the guide to mobile app development cost in Kuwait shows where payments fit in the scope. Starting from zero? See how to start an online store in Kuwait.

How Rukn builds Apple Pay into apps and stores

We build the checkout, the server code that talks to your gateway, and the admin screens your team uses for refunds and reconciliation. Mobile apps start from KD 1,999 and websites from KD 799; the final quote depends on scope. See our mobile app development service for how we work.