PayTabs adopts four types of integration. Each is meant to serve a specific need. These integration types are the Hosted Payment Page, the Managed Form, the Own-Form, and finally, the invoices. Each of these types can be initiated through our API endpoints mentioned here.

In this article, we will guide you through the differences between these four integration types, which will help you choose the most suitable integration type for your business:

Payment Workflow

Integration Type
Payment Workflow
Hosted Payment Page (HPP)
  • The Hosted Payment page uses a Transaction API request, which will return a response with a payment page link.

  • The merchant should navigate/redirect the customers to this previous payment page link, which he will have its URL in the response, in order to complete the payment.
  • Once the payment is completed, PayTabs will redirect the customer back to the merchant’s website, to the return URL that the merchant specified in the API request, and the payment results will be posted to that URL. 

Finally, click here to learn more about the Hosted Payment Page payment workflow.


  • You will have to create the invoice with valid information.
  • Then you will need to send this Invoice Link to the customer by any suitable communication.
  • Once the invoice activation date comes, and before the expiration date, the customer will be able to pay the invoice by navigating to the invoice link and clicking on the “Pay Now” button.

  • The customer will be redirected to the Payment Page to proceed with the payment.

  • Only if the invoice is paid successfully, the customer will be redirected to the successful page, and the invoice can not be paid again.

  • Merchants can view all invoices via the Merchant Dashboard.

Finally, click here to learn more about the Invoices payment workflow.

Managed Form 

  • Your website will display its own card entry form. However, key fields will be managed by the PayTabs gateway. You will need to include a script that replaces the sensitive card data with a payment token.
  • When the form is submitted, the paylib.js script file will first send the card details to the PayTabs server for storage and to create a temporary payment token. Then, this token is inserted into the form data before submitting it to your server. 
  • After receiving the token payment details from your payment page, you must send a payment request using the transaction API. You will need to include the token details you have within the payment request itself.
  • Your server will not receive the sensitive card details, and these will be removed from the form.

Finally, click here to learn more about the Managed Form payment workflow.
Own Form 
  • Your website will display its own card entry form and will ensure that you capture the required details, including the card number, expiry date, and security code. When the customer completes the form, the details will be submitted to your own servers.
  • Your servers then must send a payment request to the PayTabs gateway and the customers' card details must be included in this request.
    • In case the card used is 3DS enrolled, the API response will return a redirect URL, which you must navigate to the cardholder to complete his payment. Otherwise
    • In case the card used is non-3DS, the payment result will be returned in the API response itself.

Finally, click here to learn more about the Own Form payment workflow.

Features and Considerations

Kindly ntoe that all the marks written below (X,✔, etc..) are clickible, you can click on them to get redirected to the solution article clarifying the mentioned point in more detail.

Managed Form
Own Form
Integration Manual

The Integration Manual

The Integration Manual  The Integration Manual 
The Integration Manual  
Payment Page Hosted on PayTabs server

Payment Page Manged by PayTabs


(Hosted on the merchant server, but managed and secured by PayTabs)

Merchant has access to the card details


Merchants customize the payment page theme*

(As the merchant is creating the payment form)

(As the merchant is creating the payment form)

Merchants customize  the payment form (Fields and ordering)*

One Page Checkout (Iframe mode)*

(As the merchant is creating the payment form)

(As the merchant is creating the payment form)
PCI Requirements* 


SAQ D-Merchant

Supported payment methodsAll

Card payments only

Card payments only

Token based transactions

Return response

Post Payment response

Follow-up transactions (Refund, Capture, etc...)

Cancel before the actual payment 

Send via email & SMS

Donation mode 

Card discount

Card filter

User-defined parameters

Payment methods filter


(*) Note that if you are not PCI certified, we highly recommend you to use our Hosted Payment Page, and for not redirecting the customer out of your system to the payment page, you may use our embedded hosted payment page as well. 

You also can customize the payment form to have the "Look & Feel" of your business as clarified below:
1- In the Hosted Payment Page/Invoices themes you will be able to customize the colors and labels only by following the stesps in our How to customize the PayPage (Hosted Payment Page) UI? solution article.

2- In the Managed form, since you are creating the form yourself, you will have the ability to customize everything in the UI of the payment page along with the customizing the fields order and shape, but you will not be able to change the fields name

3- And finally for the Own Form, you will have full control over the payment form, so you will be able to customize everything in it.