Paytabs provides you with a collection of API endpoints which used to process all payments, regardless of if they are through either your own payment pages, the managed payment pages, or if you are using the hosted payment pages.
If you have a transaction that you want to fetch its details and know more about its status, type, etc... you can use the query transaction endpoint, as it will return the details of the requested transaction. In this article, we walk you through how to use and manage the mentioned endpoint.
For the best practice , we highly recommed that you use the IPN or the call back to get the status of your transactions
Through out the article we will use the transaction types clarified in our What is "tran_type"? solution article. .
In this article, you will be going to know about:
- The Endpoint and Related Postman Collection
- The Minimum Required Parameters
- Sample Request Payloads
- Sample Response Payloads
The Endpoint and Related Postman Collection
In this tutorial, we will rely on the PayTabs Query Transaction API Endpoint, mentioned on the PayTabs API endpoints postman collection, which you can access from here. The endpoint will need to be accessed with a POST request on the below-mentioned URL
Post | {{domain}}/payment/query |
Please note that not using the proper endpoint URI {{domain}} will lead to authentication issues within your responses. To find the your proper domain you can read our What Is My (Region)/(endpoint URL)? solution article.
The Minimum Required Parameters
To initiate a query payment request, there are minimum required parameters that need to be passed with valid information. The specification of these required parameters is clarified below according to the query type:
Query via Transaction Reference
In this type, you can initiate query transaction requests using your "profile_id" and the requested "tran_ref". You will receive a response object of this specific transaction you referred to. Kindly check the request parameters' specifications below:Parameter
Sample Response
Nullable
Purpose
TST2234701408580
✔
Indicates the Transaction Reference on the Paytabs side
check details on [Response Parameters | tran_ref]81784
✔
Indicates the profile that created the transaction.
check details on [Request Parameters | profileId]Query via Cart ID
As for this type, you can initiate query transaction requests using your "profile_id" and a "cart_id", and you will receive an array of all the transactions that match this specific cart_id.Kindly check the request parameters' specifications below:Parameter
Sample Response
Nullable
Purpose
81784
✔
Indicates the profile that created the transaction.
check details on [Request Parameters | profileId]STRING
✔
Indicates the cart/order id at the merchant end to easily relate the transaction to
To know more about this parameter please click here.
Sample Request Payloads
The below sample request payload will show you how you can pass the above-mentioned parameters, which are needed to be passed with valid values to perform a request.
Query via Transaction Reference
Query via Cart ID
Sample Response Payloads
Query via Transaction Reference
Query via Cart ID
⌂ To get familiar with the whole process and the other steps, kindly navigate to our "The PT2 API Endpoints Integration Manual" solution article.
⇦ And to get familiar with the rest of the steps regarding the current step "Step 7 - Manage Transactions" kindly click here.
⇦ And to navigate to the previous step in the integration process "Step 6 - Handle the post payment responses" kindly click here.