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 do I get access to the UAT Payout API?

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

7. What are the prerequisites for using the Payout API?

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

8. Is there a sandbox environment for testing?

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

9. 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 Payout API.

10. What payment methods are supported?

Ans: The methods supported are IMPS and NEFT.

11. Can I schedule payouts in advance?

Ans: Yes, you can set up a cron job at a scheduled time and can run it to trigger the payout transactions.

12. What are the compliance requirements for using the Payout API?

Ans: Compliance requirements typically include adhering to KYC (Know Your Customer) norms, AML (Anti-Money Laundering) regulations, and other relevant financial regulations. Specific requirements can be obtained from the service provider.

13. What should I do if a payout fails?

Ans:In case of a failed payout, you should check the error message or status code returned by the API. You may also contact customer support for further assistance.

14. How can I monitor the status of my payouts?

Ans:You can monitor the status of your payouts through the API's response messages or by using the dashboard provided by iServeU which tracks transaction statuses.

15. To whom do I should contact for support?

Ans:For support, you can contact the customer support team of iServeU through their provided contact details on the website.

16. What are the fees associated with using the Payout API?

Ans: The fees associated with using the Payout API are specified in the pricing section of iServeU. These fees may vary based on the volume and frequency of transactions.

17. How are fees billed?

Ans: Fees are typically billed on a monthly basis, and you will receive an invoice detailing the charges based on your usage of the Payout API.

18. How can I integrate the API into my application?

Ans:Integration steps:

Obtaining API credentials from iServeU.
Configuring API endpoints and headers for secure communication.
Implementing the API methods for initiating and managing payouts.

19. Is the API platform-independent?

Ans: Yes, the API can be integrated into applications developed in any programming language that supports HTTPS requests (e.g., Python, Java, PHP, etc.).

20. How can we debug issues during API integration?

Ans: Refer to the detailed API documentation for error handling and debugging tips. For complex issues, contact the iServeU technical support team.

21. Can the API handle bulk payouts?

Ans: Yes, the API supports bulk payouts through file uploads or batch processing methods.

22. How can I check the status of a payout?

Ans: The API provides methods for real-time transaction status retrieval using unique transaction IDs.

23. Does the API store any sensitive customer data?

Ans: No, sensitive data like account numbers and IFSC codes are encrypted during transmission and not stored on iServeU servers.

24. Can the API handle multi-currency transactions?

Ans:No, the API currently supports transactions in Indian Rupees (INR) only.

25. Is there a limit on the transaction amount?

Ans: Limits depend on the payment method:

IMPS: ₹2,00,000 per transaction.
NEFT/RTGS: No upper limit but depends on your bank agreement.
UPI: ₹1,00,000 per transaction (varies by bank).