Backend Web-Packages Integration Manuals & Supported Services
PayTabs provides you with backend packages which designed to simplify your integration with PayTabs into your business. These packages provide ready-made classes that handle various aspects of the payment process, making it easier for developers to implement secure and efficient payment solutions. These are the Laravel and Node.js
Features and Considerations
Step 1 - Setup And Activate The Integration Method
| Packages | System Requirements | How To Install | System Supported Versions | Supported Payment Methods |
|---|---|---|---|---|
| Laravel | It has specific requirements, as mentioned here. | - Composer | [5.8 , 8.x] | Based on Region, click hereto learn more. |
| Node.js | It has specific requirements, as mentioned here. | - NPM | Any | Based on Region, click hereto learn more. |
Step 2 - Configure The Integration Method
| Laravel | Node.js | |
|---|---|---|
| Allow configurations in one manual | ✔ Laravel config manual click here to learn more. | ✔ Node.js config manual click here to learn more. |
Step 3 - Initiating The Payment
This step requires you to follow the instructions on the documentation to implement your payment system workflow.
| Laravel | Node.js | |
|---|---|---|
| Manage The Payment Methods | ||
| Manage Transaction Type | ||
| Manage Transaction Class | ||
| Manage The Cart Details | ||
| Manage Shipping And Billing Details | ||
| Hide The Shipping Details | ||
| Manage The Return And Callback URLs | ||
| Manage The Payment Page Display Language | ||
| Initiate An IFramed/Embedded Payment Page | ||
| Sending Customized Parameters | ||
| Manage Tokenization | ||
| Manage Token Based Transactions | ||
| Troubleshooting Issues | ||
Step 4 - Accepting The Payment
This step is handled automatically in Packages. However, If you need to know which package is supported for transaction type, class or integration type, see the below table.
| Laravel | Node.js | ||
|---|---|---|---|
| Supported Transactions Types | Auth | ||
| Sale | |||
| Supported Transactions Class | Ecom | ||
| Recurring | |||
| Moto | |||
| Supported Transactions Type | Hosted Payment Page | ||
| Managed Form | |||
| Own Form | |||
| Invoice | |||
Step 5 - Handle The Payment Response
Since the main reason of having a response on the return page is to handle the look and feel of the return page for a better experience for your customers, the documentation is giving you the needed instructions you need to follow to verify the received response, customizing the look and feel of the return page based on the received response is something left to your call.
| Laravel | Node.js | |
|---|---|---|
| Return Page Handler | ||
| Verify The Response On The Return Page Method | ||
Step 6 - Handle The Post-Payment Response
Since the main reason of having a IPN/Callback (server-to-server call) is to continue the order workflow and update the payment and order/invoice status, the documentation is giving you the needed instructions you need to follow to verify the received response, handling the backend order related workflow based on the received response is something left to your call.
| Laravel | Node.js | |
|---|---|---|
| IPN/Callback (server-to-server Call) Handler | ||
| Verify The Response On The Return Page Method | ||
Step 7 - Manage Transactions
| Laravel | Node.js | |
|---|---|---|
| Capture Transaction | ||
| Void Transaction | ||
| Refund Transaction | ||
| Query Transaction | ||
🗃️ Laravel
7 items
🗃️ Node.js
7 items