KNET via Checkout.com

Accept KNET payments with Checkout.com as the payment service provider (PSP).

Supported workflows

Before you begin

Complete these steps before you send your first KNET payment through Checkout.com:

Set up a Checkout.com integration in your workspace. Follow the Checkout.com integration setup guide if you don’t have one yet.
Ask Checkout.com support to enable KNET on your Checkout.com account.
In the Payrails Portal, go to Settings → Integrations, open your Checkout.com integration, select KNET under Payment methods, and save.
Add KNET as a payment option in your workflow.

Request fields for Checkout.com

KNET needs no method-specific fields beyond the standard authorize fields, including the returnInfo URLs for the redirect. Required fields must be present for the payment to succeed. Payrails sends Optional fields to the PSP when you include them.

Field	Status	Description
`meta.clientContext.language`	Optional	Sets the language of the KNET bank page. A value that starts with `ar` selects Arabic. Any other value, or no value, selects English.
`meta.customer.name`, `meta.customer.lastName`	Optional	Sent to Checkout.com as the customer name.
`meta.customer.email`	Optional	Sent to Checkout.com as the customer email.
`meta.customer.phone.countryCode`, `meta.customer.phone.number`	Optional	Sent to Checkout.com as the customer phone.
`meta.customer.country.code`	Optional	Sent to Checkout.com as the customer country.

Authorize a KNET payment

Call authorize a payment with knet as the paymentMethodCode. The response includes the redirect to the KNET bank page.

Authorize request

{
  "amount": {
    "value": "10.000",
    "currency": "KWD"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "knet",
      "amount": {
        "value": "10.000",
        "currency": "KWD"
      }
    }
  ],
  "meta": {
    "clientContext": {
      "language": "ar"
    },
    "customer": {
      "email": "yousef.alsabah@example.com",
      "name": "Yousef",
      "lastName": "Al-Sabah"
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}

After the customer confirms the payment, they return to your success or error URL. Confirm the result through webhook notifications or the execution status before you fulfill the order.

How Checkout.com handles KNET

Payrails creates the KNET payment through the Checkout.com Payment Setup API. Checkout.com needs no payment token for KNET.
The KNET bank page accepts English (en) or Arabic (ar). Payrails picks the language from meta.clientContext.language.
If Checkout.com doesn’t return a redirect for a pending KNET payment, Payrails fails the payment, because the customer can’t complete it.
Each KNET payment is a new customer-initiated payment.

Getting Started

Payment Orchestration

Token Vault

Analytics & Reporting

Fraud Management

Chargebacks

Monitoring

Resources

Use Cases

Supported workflows

Before you begin

Request fields for Checkout.com

Authorize a KNET payment

How Checkout.com handles KNET

​Supported workflows

​Before you begin

​Request fields for Checkout.com

​Authorize a KNET payment

​How Checkout.com handles KNET

Supported workflows

Before you begin

Request fields for Checkout.com

Authorize a KNET payment

How Checkout.com handles KNET