PAN Verification FAQs | API Developer Portal

1. What is client id & secret and their use case?

Ans: They are used to verify the identity of users or applications that request access to the system. They play a crucial role in ensuring that only authorized individuals or systems can interact with the API.

2. Is different validation keys or client id & client secret required for different product?

Ans: The client id & client secret should be unique for different products until and unless the user name will be changed.

3. Does UAT validation keys are diff. from production and who will provide them?

Ans: Yes, UAT validation keys are different from the production ones. But when the products will be on-boarded or live they may be different. And the production details will be provided by iServeU.

4. What are the diff. details that will be provided for production?

Ans: The product url, client id and client secret will be provided for production.

5. How callback feature can be enabled?/ What is the callback receive time from iServeU after a transaction is completed?

Ans: For the callback feature to be enabled, you need to prepare a webhook API and share the URL with iServeU to get it configured. Once it is configured, you will receive callback for all the transactions. The format to configure the webhook API at your end is mentioned in the documentation of each product.

6. How does a retailer need to be onboarded under iServeU for doing any transactions and what checks do we have?

Ans: Only in production environment a retailer needs to be on-boarded. As per NPIC guidelines we do check & maintain negative registry, so before any retailer get onboarded we check their onboarding details. Once the data is verified, user/retailer get onboarded.
Negative registry checks:: negative PIN, PAN, ADDRESS

7. Why PAN Verification API is used?

Ans: It is used to fetch the PAN details for a particular PAN number.

8. Which Headers are used in PAN Verification API?

Ans: The same headers i.e client id and client secret which are used in other APIs and SDKs provided by iServeU, they are used in PAN Verification API.

9. What the PAN data are fetched while using PAN Verification API

Ans:
"pan": "",
"panstatus": "",
"lastname": "",
"firstname": "",
"middlename": null,
"pan-title": "Shri",
"last-update-date": "13/10/2020",

10. How do I get access to the UAT PAN Verification API?

Ans: To get access to the UAT PAN Verification API use their developer portal.

11. What are the prerequisites for using the PAN Verification API?

Ans: The only prerequisites to use the PAN Verification API are client credentials, for the UAT environment you get the credentials from the developer portal email.

12. Is there a sandbox environment for testing?

Ans: Yes, there is a sandbox environment available for testing the PAN Verification API. This allows you to simulate transactions and test your integration before going live.

13. How do I authenticate API requests?

Ans: API requests are authenticated using API keys, which are included in the request headers. This ensures secure communication between your application and the PAN Verification API.