UPI API V1.9 FAQ | 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 partners?

Ans: The client id & client secret should be different for different partners 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. In dynamic QR response data how to convert the QR data into image?

Ans: The QR data is in Base64 encoded, you need to use a method to convert the Base64 data into image.

7. What is the 'requestingUserName' parameter and what should I pass in it?

Ans: In UAT environment the parameter has to be passed as 'upitestret' however, in production the retailer/merchant username will be shared by iServeU team and it needs to be passed in there.

8. What is the use of 'channeled' parameter?

Ans: It can be used to track the traffic from where the hits are coming in, whether it is Android/Web/iOS User. It is a mandatory parameter.

9. 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
get access to the UAT Payout API use their developer portal.

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

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

11. What are the prerequisites for using the UPI API?

Ans: The only prerequisites to use the UPI 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 UPI 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 UPI API.