You can start using the Collections files of the "Postman" program, which allows you to more easily perform the tests of the services published by PayTR.
You can view the Postman page where the Collections files are located via this link.
In STEP 1, which is the first step of the integration phase, the hash calculation should be made and included in the request block. With the values in the request block, hash calculations are made on the service again. The hash value transmitted and the hash value obtained as a result of the calculation are compared and it is confirmed that the request came directly from the store.
You can view Hash Calculation page via this link.
Token errors generally occur due to the reasons in the list;
1) Incorrect use of information such as merchant_key, merchant_salt,
2) The data used in the paytr_token account has a different value in the POST content,
3) The data used in the paytr_token account is not added end to end in the correct order,
4) Not adding all the necessary data in the paytr_token account or including the unnecessary data in the account.
You can calculate the correct hash with your values on the Hash Calculation page.
Service Response Monitoring
In the 2nd STEP of the integration phase, there is the notification/callback side. Except for the information services in the PayTR structure (eg status inquiry), the Notification of the relevant transaction is sent to your URL address with the POST method in the 2nd STEP of all payment APIs. You can access the sample response returned by PayTR from the Service Response Observation area. Responses to your notification URL page are indicated on the page under the phrase "Response to your Notification URL defined by PayTR". You can access "Successful" or "Failed" responses on the page by using the form structure or JSON field on the page.
You can view Service Response Monitoring page via this link.