Do Transaction

Description :

This API endpoint is used to initiate the transaction

Endpoint URL :
Request Parameters
Request Parameter Data Type Required Description
token string Yes API access token for user authentication.
[To known more about token Click Here]
customer_id integer/string Yes mobile no / bill no.
operatorcode string Yes Operator Code for operator identification
amount integer Yes Amount of transaction
refid string Yes A unique reference id generated by your application, to track the requests later.
agent_id string Optional Pass the agent id from where the transaction is requested.[Not required for Prepaid/DTH Recharge]
customer_mobile integer Optional Please pass Customer Mobile No. for every request.[It's required for bill payments]
p2 string Optional Certain billers require p2 for bill details. Please Click below MDM Biller List to see service wise list of additional parameters.
p3 string Optional Certain billers require p3 for bill details. Please Click below MDM Biller List to see service wise list of additional parameters.
p4 string Optional Certain billers require p4 for bill details. Please Click below MDM Biller List to see service wise list of additional parameters.
p5 string Optional Certain billers require p5 for bill details. Please Click below MDM Biller List to see service wise list of additional parameters.
p6 string Optional Certain billers require p6 for bill details. Please Click below MDM Biller List to see service wise list of additional parameters.
Note : This MDM Biller List will work only when your api account is login
Request Example
Responses (JSON)
  • STATUS : SUCCESS
    • Description: Transaction successfully completed.
    • 'txnid' (string): "transaction id of transaction"
    • 'status' (string): "status of transaction"
    • 'customer_id' (string): "customer id of transaction"
    • 'amount' (string): "amount of transaction"
    • 'operatorcode' (string): "operator code of transaction"
    • 'request_time' (string): "time of request of transaction"
    • 'response_time' (string): "time of response of transaction"
    • 'refid' (string): "refid of transaction"
    • 'operatorid' (string): "utr of transaction"
    • 'message' (string): "message of transaction"
    • 'remainamount' (string): "remain amount after transaction"
  • STATUS : PENDING
    • Description: Transaction under proccess.
    • 'txnid' (string): "transaction id of transaction"
    • 'status' (string): "status of transaction"
    • 'customer_id' (string): "customer id of transaction"
    • 'amount' (string): "amount of transaction"
    • 'operatorcode' (string): "operator code of transaction"
    • 'request_time' (string): "time of request of transaction"
    • 'response_time' (string): "time of response of transaction"
    • 'refid' (string): "refid of transaction"
    • 'operatorid' (string): "utr of transaction"
    • 'message' (string): "message of transaction"
    • 'remainamount' (string): "remain amount after transaction"
  • STATUS : FAILED
    • Description: A specific error message.
    • 'status' (string): "FAILED"
    • 'message' (string): "Ip not register or inactive"
Note
  • The API endpoint should be accessed via a GET 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