Choose a Payzah Integration Method: Transit vs Direct

Payzah gives you two integration methods so you can match the checkout experience to your business needs without over-engineering. If speed-to-market matters most, the Transit Payment Page gets you live in hours. If you need full control over every pixel and payment flow, Direct Integration is the right choice.

Side-by-Side Comparison

	Transit Payment Page	Direct Integration
Setup Complexity	Low — minimal code required	Higher — each payment method configured separately
Time to Launch	Fast	Longer, proportional to customization
UI Control	Payzah-hosted, branded with your logo	Fully custom — you own the interface
Payment Methods	All methods on one page	K-Net, Credit Card, and Apple Pay integrated individually
Ongoing Maintenance	Payzah handles updates and security	You manage the integration
Best For	Quick launches, standard checkouts	Branded experiences, complex payment flows
`payment_type` value	`"3"`	`"1"` (K-Net) or `"2"` (Credit Card)

Transit Payment Page

The Transit Payment Page is a fully hosted checkout solution managed by Payzah. You initialize a payment session via the API, then redirect your customer to the returned URL — Payzah handles everything from there.

Use payment_type: "3" in your initialization request to activate the Transit Payment Page flow. The API response will include a transit_url to which you redirect the customer.

Key Features

Quick Integration

Minimal development effort required. Redirect your customer and let Payzah handle the rest.

All Payment Methods in One Page

K-Net, VISA, MasterCard, and Apple Pay (credit and debit) are all available on the single hosted checkout page.

Branded With Your Logo

Your merchant logo and business details are displayed on the payment page, maintaining customer trust.

Minimal Maintenance

Payzah manages all page updates, security patches, and compliance changes — you never need to update the checkout UI.

How It Works

Initialize the Payment

Send a POST request to the Payzah API with payment_type set to "3" along with your order details.

{
  "payment_type": "3",
  "amount": "10.500",
  "order_id": "ORD-00123",
  "currency": "KWD"
}

Receive the Transit URL

The API responds with a transit_url pointing to your customer’s hosted payment session.

{
  "transit_url": "https://checkout.payzah.com/transit/abc123xyz"
}

Redirect the Customer

Redirect your customer’s browser to the transit_url. They complete payment on the Payzah-hosted page and are returned to your site upon completion.

transit_url

string

The fully qualified URL of the hosted payment page for this transaction. Redirect the customer’s browser to this URL to begin checkout.

When to Use Transit Payment Page

Choose the Transit Payment Page when:

You want to launch quickly without building a custom checkout UI
Your checkout requirements are straightforward and don’t need deep customization
You prefer Payzah to own the maintenance and security of the payment interface
You want to offer all payment methods (K-Net, VISA, MasterCard, Apple Pay) without separate integrations

Direct Integration

Direct Integration gives you full control over the checkout experience. You integrate each payment method individually, building and owning every part of the payment UI while using Payzah’s API to process transactions.

Use payment_type: "1" for K-Net or payment_type: "2" for Credit Card (VISA/MasterCard/Apple Pay) in your initialization request. The API response will include a direct_url to which you redirect the customer for that specific payment method.

Key Features

Custom Integration

Integrate K-Net, Credit Cards, and Apple Pay individually, exactly as your application requires.

Full UI Control

You design and own the payment interface — match it precisely to your website’s look, feel, and workflow.

Detailed Configuration

Handle specific payment scenarios, conditional flows, and edge cases that a generic hosted page cannot accommodate.

Tailored Checkout

Deliver a seamless, on-brand checkout that feels native to your platform rather than a redirect to a third-party page.

How It Works

K-Net
Credit Card / Apple Pay

Initialize a K-Net Payment

Send a POST request with payment_type set to "1".

{
  "payment_type": "1",
  "amount": "10.500",
  "order_id": "ORD-00124",
  "currency": "KWD"
}

Receive the Direct URL

The API responds with a direct_url for the K-Net payment flow.

{
  "direct_url": "https://checkout.payzah.com/direct/knet/def456uvw"
}

Redirect the Customer

Redirect your customer to the direct_url to complete K-Net authentication and payment.

Initialize a Credit Card Payment

Send a POST request with payment_type set to "2".

{
  "payment_type": "2",
  "amount": "10.500",
  "order_id": "ORD-00125",
  "currency": "KWD"
}

Receive the Direct URL

The API responds with a direct_url for the Credit Card / Apple Pay flow.

{
  "direct_url": "https://checkout.payzah.com/direct/card/ghi789rst"
}

Redirect the Customer

Redirect your customer to the direct_url to complete their VISA, MasterCard, or Apple Pay transaction.

direct_url

string

The URL for the specific payment method flow selected by payment_type. Redirect the customer’s browser to this URL to initiate the direct payment process.

`payment_type` Reference

payment_type

string

required

Determines the payment flow and the type of URL returned in the response.

"1" — K-Net direct flow; response contains direct_url
"2" — Credit Card (VISA, MasterCard, Apple Pay) direct flow; response contains direct_url
"3" — Transit Payment Page (all methods); response contains transit_url

When to Use Direct Integration

Choose Direct Integration when:

You need your checkout UI to match your brand or application design system precisely
You want to present specific payment methods conditionally based on customer context
You require fine-grained control over the payment flow, error handling, and post-payment logic
You have the development resources to build and maintain individual payment method integrations

Quick Decision Guide

Not sure which to pick? Start with the Transit Payment Page. You can always migrate to Direct Integration later once you have a clearer picture of your customization requirements.

I want to…	Recommended Method
Launch as quickly as possible	Transit Payment Page
Show all payment methods on one page	Transit Payment Page
Match my site’s exact design	Direct Integration
Control each payment method separately	Direct Integration
Minimize long-term maintenance	Transit Payment Page
Handle complex, conditional payment flows	Direct Integration

Choose a Payzah Integration Method: Transit vs Direct

Side-by-Side Comparison

Transit Payment Page

Key Features

Quick Integration

All Payment Methods in One Page

Branded With Your Logo

Minimal Maintenance

How It Works

When to Use Transit Payment Page

Direct Integration

Key Features

Custom Integration

Full UI Control

Detailed Configuration

Tailored Checkout

How It Works

`payment_type` Reference

When to Use Direct Integration

Quick Decision Guide

Next Steps

Transit Payment Page Guide

Direct Integration Guide

​Side-by-Side Comparison

​Transit Payment Page

​Key Features

Quick Integration

All Payment Methods in One Page

Branded With Your Logo

Minimal Maintenance

​How It Works

​When to Use Transit Payment Page

​Direct Integration

​Key Features

Custom Integration

Full UI Control

Detailed Configuration

Tailored Checkout

​How It Works

​payment_type Reference

​When to Use Direct Integration

​Quick Decision Guide

​Next Steps

Transit Payment Page Guide

Direct Integration Guide

Side-by-Side Comparison

Transit Payment Page

Key Features

How It Works

When to Use Transit Payment Page

Direct Integration

Key Features

How It Works

`payment_type` Reference

When to Use Direct Integration

Quick Decision Guide

Next Steps