Holidiapay

How the data is requested: Request gateway:https://payapi.hoolidiapay.in/

All interface messages are post requests, and the answer parameters are json string
header header: content-type:application/x-www-form-urlencoded; charset=UTF-8
Digital signature: Signature original string: Whether requested or answered, the original string of signatures is assembled into strings as follows:

all business parameters are sorted from small to large by the ascii code of the field name, using the QueryString format (i.e. key1-value1-key2-value2...). Stitched together, empty values also participate in signatures. Note: Sign parameters do not participate in signing
Signature algorithm: MD5 is a summary generation algorithm that performs MD5 operations by adding the contents of the merchant communication key after signing the original string, and then lowercase conversion, resulting in a summary string that is the signature result.
MD5 signature calculation formula:

Signature original string: key1-val1-key2-val2-key3-val3...sign=strtolower (signature original string-key-merchant keyy)) Note: Merchant key contact the developer for request or self-generated on the platform

pay

Payment request (Random Reduce)

Basic information

Path： /api/holidiapay/holidiaPayRandomReduce

Method： POST

Interface description:

Request the parameters

Headers

The name of the argument	The parameter value	Required	example	remark
Content-Type	application/json	be

Body

name	type	Required	remark	Additional information
merchant_appid	string	Yes	Payment method appid	mock: The system is assigned to the merchant
out_trade_no	string	Yes	Merchant order number	mock: Up to 32 bits, and guaranteed uniqueness, the merchant generates itself
amount	string	Yes	The transaction amount	mock: Greater than zero
timestamp	string	Yes	The request time	mock: Timestamp
firstname	string	Yes	name	mock: Customer name
phone	string	Yes	Cell phone number	mock: Customer phone
email	string	Yes	email	mock: Customer mail
cus_reg_ip	string	Yes	cus_reg_ip	mock: Customer Register IP
upi_vpa	string	No	UPI VPA
sign	string	Yes	signature

Returns data

name	type	Required	remark	Additional information
code	string	Yes	0 Success -1 failed	mock: 0 Success -1 failed
msg	string	Yes	The response message
result	object	Yes	The result of a successful service call is a nested String-type JSON object that is valid only if code is 0
├─ trans_no	string	Yes	Platform single number
├─ pay_url	string	Yes	Pay for the connection
sign	string	Yes	signature

Pay for asynchronous callbacks

Basic information

Path： /pay_async_url

Method： POST

Interface description:

After the payment parameters are submitted successfully, the platform will send the callback parameters to the payment callback asynchronous notification address, after receiving the notification, the receiver output SUCCESS indicates that processing, otherwise the server will periodically re-issue notifications of the same order, a maximum of 20 notifications.
Note: Duplicate orders need to be processed in case both notifications handle the same business and result in losses. Pay callback asynchronous notification address Please manage the background configuration, the configuration process can consult the appropriate developer. Answer code, answer message, signature: Do not participate in the signature

Request the parameters

Headers

The name of the argument	The parameter value	Required	example	remark
Content-Type	application/json	be

Body

name	type	Required	The default	remark	Additional information

Returns data

name	type	Required	remark	Additional information
code	string	Yes	0 Success -1 failed	mock: 0 Success -1 failed
msg	string	Yes	The response message
result	object	Yes	The result of a successful service call is a nested String-type JSON object that is valid only if code is 0
├─ trans_no	string	Yes	Platform single number
├─ out_trade_no	string	Yes	Merchant's single number
├─ amount	string	Yes	The order amount	mock: Rupee
├─ status	string	Yes	Payment status	mock: 0 to pay 1 payment success 2 payment in 3 payment certification 4 refunded - 1 payment failure
sign	string	Yes	signature

Check the order status

Basic information

Path： /api/pay_order_deal/queryOrderByNo

Method： POST

Interface description:

Request the parameters

Headers

The name of the argument	The parameter value	Required	example	remark
Content-Type	application/json	be

Body

name	type	Required	remark	Additional information
merchant_appid	string	Yes	Merchant appid	mock: Platform assignment
trans_no	string	No	System order number	trans_no and out_trans_no cannot be empty at the same time
out_trans_no	string	No	Merchant order number	trans_no and out_trans_no cannot be empty at the same time
sign	string	Yes	signature

Returns data

name	type	Required	remark	Additional information
code	string	Yes	0 Success -1 failed	mock: 0 Success -1 failed
msg	string	Yes	The response message
result	object	Yes	The result of a successful service call is a nested String-type JSON object that is valid only if code is 0
├─ trans_no	string	Yes	Platform single number
├─ out_trade_no	string	Yes	Merchant's single number
├─ amount	string	Yes	The order amount
├─ email	string	Yes	mail
├─ phone	string	Yes	Phone
├─ firstname	string	Yes	name
├─ order_time	string	Yes	Order time	mock: Timestamp
├─ pay_time	string	Yes	Payment time	mock: There is after payment
├─ status	string	Yes	Payment status	mock: 0 to pay 1 payment success 2 payment in 3 payment certification 4 refunded - 1 payment failure
sign	string	Yes	signature

Payment

Payout for asynchronous callbacks

Basic information

Path： /payout_async_url

Method： POST

Interface description:

After the payment parameter is submitted successfully, the platform will send the callback parameter to the payment callback asynchronous notification address, after receiving the notification, the receiver output SUCCESS indicates that processing, otherwise the server will periodically re-issue the notification of the same order, a maximum of 20 notifications.
Note: Duplicate orders need to be processed in case both notifications handle the same business and result in losses. Pay callback asynchronous notification address Please manage the background configuration, the configuration process can consult the appropriate developer. Answer code, answer message, signature: Do not participate in the signature

Request the parameters

Headers

The name of the argument	The parameter value	Required	example	remark
Content-Type	application/json	be

Body

name	type	Required	The default	remark	Additional information

Returns data

name	type	Required	remark	Additional information
code	string	Yes	0 Success -1 failed	mock: 0 Success -1 failed
msg	string	Yes	The response message
result	object	Yes	The result of a successful service call is a nested String-type JSON object that is valid only if code is 0
├─ trans_no	string	Yes	Platform single number
├─ out_trade_no	string	Yes	Merchant's single number
├─ amount	string	Yes	The amount paid
├─ bank_user_name	string	Yes	The payee's exact name
├─ bank_number	string	Yes	Bank card number
├─ payout_status	string	Yes	Payment status	mock: 0 Waiting for 1 payment success 2 payment in progress 3 payment failure
├─ completed_change	string	Yes	completed change status	mock: 0 Normal 1 Reversed after success 2 Failure after success
sign	string	Yes	signature

Initiate a payout

Basic information

Path： /api/holidiapayouts/applyPayout

Method： POST

Interface description:

Request the parameters

Headers

The name of the argument	The parameter value	Required	example	remark
Content-Type	application/json	be

Body

name	type	Required	remark	Additional information
merchant_appid	string	Yes	Payment method appid	mock: The system is assigned to the merchant
out_trade_no	string	Yes	Merchant order number	mock: Up to 32 bits, and guaranteed uniqueness, the merchant generates itself
amount	string	Yes	The transaction amount	mock: 1 or more
timestamp	string	Yes	The request time	mock: Timestamp
bank_user_name	string	Yes	The payee's exact name
phone	string	Yes	The payee's phone
email	string	Yes	The payee's email
address	string	Yes	The payee's address
bank_name	string	No	Bank name
bank_ifsc	string	Yes	Line card identification
bank_number	string	Yes	Bank card number
upi_vpa	string	Yes	UPI VPA
sign	string	Yes	signature

Returns data

name	type	Required	remark	Additional information
code	string	Yes	0 Success -1 failed	mock: 0 Success -1 failed
msg	string	Yes	The response message
result	object	Yes	The result of a successful service call is a nested String-type JSON object that is valid only if code is 0
├─ trans_no	string	Yes	Platform single number
├─ out_trade_no	string	Yes	Merchant's single number
├─ amount	string	Not required	The amount paid
├─ bank_user_name	string	Yes	The payee's exact name
├─ bank_number	string	Yes	Bank card number
├─ payout_status	string	Yes	Payment status	mock: 0 Waiting for 1 payment success 2 payment in progress 3 payment failure
sign	string	Yes	signature

Query Payout order status

Basic information

Path： /api/pay_order_deal/queryOrderByNo

Method： POST

Interface description:

Request the parameters

Headers

The name of the argument	The parameter value	Required	example	remark
Content-Type	application/json	be

Body

name	type	Required	remark	Additional information
merchant_appid	string	Yes	Merchant appid	mock: Platform assignment
trans_no	string	No	System order number	trans_no and out_trans_no cannot be empty at the same time
out_trans_no	string	No	Merchant order number	trans_no and out_trans_no cannot be empty at the same time
sign	string	Yes	signature

Returns data

name	type	Required	remark	Additional information
code	string	Yes	0 Success -1 failed	mock: 0 Success -1 failed
msg	string	Yes	The response message
result	object	Yes	The result of a successful service call is a nested String-type JSON object that is valid only if code is 0
├─ trans_no	string	Yes	Platform single number
├─ out_trade_no	string	Yes	Merchant's single number
├─ bank_user_name	string	Yes	The payee's exact name
├─ bank_ifsc	string	Yes	Line card identification
├─ bank_number	string	Yes	Bank card number
├─ amount	string	Yes	The Payout order amount
├─ email	string	Yes	Email
├─ phone	string	Yes	Phone
├─ address	string	Yes	address
├─ order_time	string	Yes	Order time	mock: Timestamp
├─ payout_time	string	Yes	Payout time	mock: There is after payment
├─ status	string	Yes	Payment status	mock: 0 to pay 1 payment success 2 payment in 3 payment certification 4 refunded - 1 payment failure
sign	string	Yes	signature

Holidiapay interface documentation

Holidiapay

pay

Payment request (Random Reduce)

Basic information

Request the parameters

Returns data

Pay for asynchronous callbacks

Basic information

Request the parameters

Returns data

Check the order status

Basic information

Request the parameters

Returns data

Payment

Payout for asynchronous callbacks

Basic information

Request the parameters

Returns data

Initiate a payout

Basic information

Request the parameters

Returns data

Query Payout order status

Basic information

Request the parameters

Returns data