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.
Ans: The client id & client secret should be unique for different products until and unless the user name will be changed.
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.
Ans: The product url, client id and client secret will be provided for production.
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.
Ans: The PennyDrop API is used in iServeU to facilitate seamless and secure financial transactions. The reasons like identity verification, bank account verification, seamless integration etc.
Ans: No, this is not mandatory. But it is suggested to use Penny Drop API before doing transaction to check the beneficiary.
Ans: Yes. You can use Penniless Beneficiary Verification method with iServeU's Penny drop API.
Ans: Yes. I can pass the master IFSC code for doing Beneficiary Verification using Penny drop API. But it varies upon different banks. Some banks don’t allow to pass the master IFSC code for doing Beneficiary Verification using Penny drop API.
Ans: To get access to the UAT Penny Drop API use their developer portal.
Ans: The only prerequisites to use the Penny Drop API are client credentials, for the UAT environment you get the credentials from the developer portal email.
Ans: Yes, there is a sandbox environment available for testing the Penny Drop API. This allows you to simulate transactions and test your integration before going live.
Ans: API requests are authenticated using API keys, which are included in the request headers. This ensures secure communication between your application and the Penny Drop API.