Most probably this error happened because either you are using PT1 integrations and has entered the "server key" or "client key" from the PT2 or any invalid key instead of the "secret key" which can be only retrieved from your PT1 dashboard, or you are a PT2 merchant that using old integration method and need to upgrade to the latest version. 


In this article you will be going to know about:

How to investigate the reason that caused this error?


You can investigate the reason for such an error from the "API debug log" by navigating to the Developers > Testing > API Debug Logs (within your desired profile).





Or you may get the error directly from the response payload sent from PayTabs.


eCommerce Plugins

Reason #1: Using an old eCommerce plugin


This means that you are using an old version of the plugin that was initiated only to support PT1 merchants. In this case, you will need to upgrade the eCommerce plugin you are using to the latest one depending on which eCommerce plugin you are using. You will just need to seek the "How to upgrade the PayTabs plugin to the latest version?" section on the solution article related to the plugin you are using from the "eCommerce Plugins" category section

Backend Packages 


Reason #1: Using an old backend packages


This means that you are using an old version of the backend package which was initiated only to support PT1. In this case, you will just need to switch the package to the latest one depending on which library you are using. You will just need to seek the solution article related to your backend Package from the "Backend Packages" category section.

SDK mobile

Reason #1: Using an old mobile SDK


This means that are using an old version of the mobile SDK that was initiated only to support PT1. In this case, you will just need to upgrade the mobile SDK used to the latest one depending on which mobile SDK you are using. You will just need to seek the solution article related to the mobile SDK from you are using the "Mobile SDKs" category section.

API Endpoints

Reason #1: Using PT1 API endpoints

This means either you are using PT1 integrations and has entered the "server key" or "client key" from the PT2 or any invalid key instead of the "secret key" which can be only retrieved from your PT1 merchant dashboard, and in this case, you will need to enter the exact secret key exists in your PT1 merchant account.


Or, you are using PT2 and have no PT1 account at all, and yet somehow you are using the endpoints of PT1 and passing the server/client key in the place of the secret key. In this case, you will need to use our latest endpoint which you can know more about from our fully detailed PT2 API Endpoints Documentations.