---
description: Frequently Asked Questions by developers
---

# FAQ

## **What is the difference between Public client Id and private client id?**

Public client is not merchant specific, use the Id mentioned in this document. Public client id can be used to generate token using username and password of a merchant. Private client id is merchant specific and needs to be known to each merchant by wither checking it on dashboard or calling our support team. Private client id is used to generate token using client secret.

## **How can I get the public client id?**

Public client id is available in this document under the method 1 for authentication.

## **How can I get the private client id and client secret?**

Please get in touch with payu support team to request the same. We are working on automating this and providing the details to you on your dashboard. Watch this space for updates.

## **What is payout Merchant id and is it different from payu merchant id?**

Yes, payout merchant id is different from payu merchant id. You can view this on merchant’s payout dashboar or call support team. For using payout apis, use the payout merchant id.

## **What are refresh tokens and why are they different from ordinary tokens?**

Each token has a TTL or expiry time. Once expired you cannot use the token for authentication. This is an additional security standard followed by us to ensure your data is safe with us. To regenerate a token, you don’t need to call the authentication apis using your password or secret(since these are sensitive as well) . Hence we provide an option to regenerate a token using the previous token. Just call the refresh api to get a new token and get going.

## **Is there a UI to set webhooks?**

Yes, you can set webhooks using the payu->settings->webhooks

## **What happens if I set only a few webhooks?**

&#x20;Events will be pushed to the set webhooks and the missing webhooks events will be sent to default webhook if it has been sent. Read the section under ‘default webhooks’ for further details.

## **I get a 404 error while setting/saving webhook**

This happens when payu is not able to make a server call to validate your webhook url. Please ensure following:

&#x20;-You have an api created and hosted at your server that you are trying to save

&#x20;-If you have a ip whitelisting at your end , whitelist payu’s ip so that we can make a server call to your url

&#x20;Payu prod ip address: 180.179.168.225

&#x20;Payu test ip address: 180.179.165.250

## **I get a 403 error while setting/saving webhook**

This happens when payu is unable to “post” data to your webhook url. Please make your api is valid and is available as a post method with content type ‘application/json’ to enable posting data to it.

## **Why do I need a batch Id while initiating a transfer?**

Batch id can be used to identify a bulk transfer with a single id and later use it to check the status of the entire bulk transfer in a single go instead of individual status checks. Batch id can also be used across multiple bulk transfer requests to group different bulk transfers under a single identifier. It is a very useful concept if used properly.

