Reseller Client Credentials Token

The Reseller Client Credentials Token API obtains an access token for a reseller using the OAuth client_credentials grant. Use this token to call the payment and verify-payment APIs on behalf of merchants linked to the reseller. This avoids the per-merchant authorization-code flow.

HTTP Method: POST

Environment

Request parameters

Header parameters

Body parameters

Using the Reseller Token

Pass the returned token in the Authorization header when calling both /partner/payments and /partner/verifyPayment:

Authorization: Bearer <RESELLER_ACCESS_TOKEN>

The system validates the token against the reseller portal and verifies that the merchant_id supplied in the request body is linked to the reseller before processing the request. If the merchant is not linked, the request is rejected with an authentication failure.

Token usage and prerequisites

Use the reseller client credentials token when the merchant is already linked to the reseller and the reseller wants a single server-to-server token for multiple linked merchants. The token is not the per-merchant authorization-code token described elsewhere in the integration guide.

Before requesting the token, ensure that:

• The merchant is linked to the reseller.
• The OAuth application has appropriate scopes, subject to the scope note above.

Sample Request

curl --location 'https://uat-accounts.payu.in/oauth/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'client_id=<RESELLER_CLIENT_ID>' \
--data-urlencode 'client_secret=<RESELLER_CLIENT_SECRET>' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'scope=partner_payment_links partner_payments'

Sample Response

Success scenario

{
"access_token": "<RESELLER_ACCESS_TOKEN>",
"token_type": "Bearer",
"expires_in": 3600,
"scope": "partner_payment_links partner_payments"
}

Response parameters