đŸ’»
Payouts Integration
  • Introduction
  • Functional overview
  • Onboarding
  • Postman Collection
  • Authentication
  • Authentication Token
    • API to Generate Token using username/password
    • API to Generate Token using private client id
  • Refresh Tokens
    • Refresh Token API
  • IP Check
  • API Integration
  • Testing Credentials
  • API Flow Diagram
  • Beneficiary Management
    • View Beneficiary Detail
    • Beneficiary Creation / Registration
  • Core Payouts API
    • Get Account Details API
    • Cancel Transfer API
    • Check Transfer Status API
    • Initiate/Schedule Transfer API
  • Verification
    • Verify Account / Penny Test
    • Validate Vpa
    • IFSC Details
  • smart send
    • Feature
    • Smart Send API
      • Cancel Smart Send
      • Smart Send Status
    • Smart Send V2 API
      • Create Smart Send Link
      • Smart Send Status
      • Cancel Smart Send
      • Extend Expiry Date
    • Bulk Smart Send
      • Bulk File Upload
      • Bulk Process File
    • Smart Send Error Codes
    • Fetch masked Vpas
  • Webhooks
    • What are Webhooks?
    • Default Webhooks
    • Creating Webhooks
    • Set Webhook API
    • Types of webhooks
  • Settings
    • Disable queued Payout
  • FAQ
Powered by GitBook
On this page
  • Request Params
  • Example
  • Response Params

Was this helpful?

  1. Authentication Token

API to Generate Token using username/password

Generate a token by using the payout merchant username and password

PreviousAuthentication TokenNextAPI to Generate Token using private client id

Last updated 5 years ago

Was this helpful?

Request Params

Key

Description

Data type

Mandatory

Possible Values

client_id

This is a public client id to be used by all payouts merchants.

Please note: you can use the same client id mentioned under ‘possible values’ column depending on the environment

String

yes

Production client_id : ccbb70745faad9c06092bb5c79bfd919b6f45fd454f34619d83920893e90ae6b Test client_id : 6f8bb4951e030d4d7349e64a144a534778673585f86039617c167166e9154f7e

grant_type

Constant value

String

yes

password

username

Registered mobile or email

String

yes

password

Registered Account password

String

yes

scope

Constant value

String

yes

create_payout_transactions

public client id does not vary from merchant to merchant, use the id mentioned above and get going

Example

Sample Request (in test env):

curl -X POST \
 https://uat-accounts.payu.in/oauth/token \
 -H 'cache-control: no-cache' \
 -H 'content-type: application/x-www-form-urlencoded' \
 -d 'grant_type=password&scope=create_payout_transactions&client_id=6f8bb4951e030d4d7349e64a144a534778673585f86039617c167166e9154f7e&username=payouttest4%40mailinator.com&password=Tester%40123&='

Pro Tip: Remember to have the Content-Type set as x-www-form-urlencoded to avoid “invalid request” errors

Sample Response :

{
 "access_token": "581b0657b38a56bb4296f774852f208f6d84a23d8f1bf61c63c15de60d43ee76",
 "token_type": "Bearer",
 "expires_in": 7199,
 "refresh_token": "ff8e094ecfa11fb390931f779ae62c0836f97bbaedcf5551c88eff826da3239a",
 "scope": "create_payout_transactions",
 "created_at": 1585216027,
 "user_uuid": "11e8-5a8f-05faaaa4-84a5-020d245326e4"
}

Response Params

Key

Description

access_token

This is the security token. This will be used in further api calls

token_type

Type of token

expire_in

This is the TTL, Access token will get expired in return seconds.

refresh_token

This will be used to refresh the access_token. Api detail is given below

scope

Allowed scopes in generated security token eg the generated token can be used only for payout api requests

created_at

Time of creation in milliseconds

user_uuid

You will learn more about refresh token soon

Unique identifier for the user. Read more about uuid

https://accounts.payu.in/oauth/token
https://uat-accounts.payu.in/oauth/token
here