Add Beneficiary

Endpoint URL :
Request Parameters
Request Parameter Data Type Default Value Required Description Change Date Change Description
mobile_no integer Yes Remitter mobile number
name string Yes Enter account holder name
bank_id integer Yes Please pass the bank id
For Bank List Api Click Here
account_no integer Yes Bank account number
ifsc_code string Yes IFSC Code of the branch
dob string Yes Date of Birth of remitter (YYYY-MM-DD)
state_id integer Yes State id of the remitter
For State List Api Click Here
address string Yes Address of the remitter
pincode integer Yes 6 digit pincode of the remitter
Request Example [JSON]
Responses (JSON)
  • status_code (integer): The status code of the response.
  • status (string): Indicates whether the operation was a success or a failure.
  • message (string): A message describing the result of the operation.
  • data (object): An object containing details of the beneficiary.
    • beneficiary_id (string): The unique identifier of the beneficiary.
    • bank_id (string): The unique identifier of the bank.
    • bank_name (string): The name of the bank where the beneficiary holds an account.
    • beneficiary_name (string): The name of the beneficiary.
    • account_no (string): The account number of the beneficiary.
    • ifsc_code (string): The IFSC code of the beneficiary's bank branch.
    • is_verified (string): Indicates whether the beneficiary is verified ('Y' for Yes, 'N' for No).
  • status_code (integer): 2
  • message (string): "A specific validation error message."
  • status (string): "FAILED"
  • status_code (integer): 0
  • message (string): "Unable to proccess your request"
  • status (string): "FAILED"
Note
  • The API endpoint should be accessed via a POST request.
  • All requests must include a Bearer Token in the Authorization header to authenticate the request.
  • Please always update your transaction with status key and SUCCESS, PENDING, FAILED value.
  • Implement proper error handling on the client side to display user-friendly error messages based on the 'status' and 'message' fields in the response.
© Redpay.
Design & Develop by Redpay Payments Private Limited