Payment Casher

Tips

• All requests are Post requests, and the data format is json

Brief Description

This section introduces the API endpoint for creating a payment link.

Request URL

• /v1/paypro/paymentLink

Request Method

• POST

Headers

Header	Required	Type	Description
merchantNo	Yes	string	Merchant number

Body

Parameter	Required	Type	Description
sign	Yes	string	The sign field is generated by sorting all fields except sign in alphabetical order and concatenating them as key1=value1key2=value2. Use app secret as salt for MD5 encryption. The sign field should be in lowercase.
timestamp	Yes	long	Timestamp (e.g. 1715941383720)
tradeNo	Yes	string	Unique transaction number (recommended format: yyyymmddhhmmss + random number)
amount	Yes	float	Amount (no decimal support)
mobile	Yes	string	User's mobile number (Indonesian phone number starting with 08 or 628, total 10-13 digits)
email	Yes	string	Email address
username	Yes	string	User's name
channelCode	No	string	Payment channel code for limiting the displayed payment channels at the cashier. If not specified, all channels will be displayed. Options: QRIS, EWALLET, VA
wayCode	No	string	Payment method code. Refer to the WayCode appendix for details. Note: If using wayCode, channelCode is required; otherwise, wayCode is invalid.
notifyUrl	Yes	string	Asynchronous callback URL
returnUrl	No	string	URL to redirect the customer to after successful authorization
remark	No	string	Remarks (will be returned as is)

Request Body Example

{
  "sign": "363b4674a1c1772e8a50295dc19d6727",
  "timestamp": "1732988442913",
  "tradeNo": "0b4ece82fa9749e8b8e57fa64931b7f8",
  "username": "kevin",
  "amount": 1000000,
  "channelCode": "EWALLET",
  "wayCode": "DANA",
  "email": "[email protected]",
  "mobile": "6281245907765",
  "notifyUrl": "https://google.com",
  "returnUrl": "http://abc.com/callback_page",
  "remark": "test"
}

Response

Parameter	Required	Type	Description
msg	Yes	string	Request result (success only indicates successful request, not for merchant logic judgment)
code	Yes	string	Request response code (0000 indicates successful request, not for merchant logic judgment). For specific error codes, refer to the business error code enumeration
timestamp	Yes	string	Transaction time
success	Yes	string	Transaction result
data	Yes	Object	Response object
data.tradeNo	Yes	string	Merchant transaction number
data.platFormTradeNo	Yes	string	Unique transaction number
data.status	Yes	string	Request result. Merchants can use it for logic processing. 0000 indicates successful transaction, 0001 indicates partial payment, 0015 indicates processing, others are error codes indicating failure
data.desc	Yes	string	Error description
data.remark	Yes	string	Returned content of the request (as is)
data.paymentUrl	Yes	string	Cashier URL
data.qrString	No	string	QR code information

Successful Response Example

{
	"msg": "success",
	"code": "0000",
	"timestamp": 1728609277476,
	"success": true,
	"data": {
		"tradeNo": "428c430ce59b47138674c971ff07a711",
		"platFormTradeNo": "c167o1itir0fypid",
		"status": "0015",
		"desc": "Paying",
		"remark": "11111",
		"paymentUrl": "http://paypro.tech/cashier/dsfjlsdkjflksdfjlkfs",
		"qrString": "00020101021226670021ID/.HTTPS://CFSUKSESS011893600922376110100202097611010020303UMI51440014ID.CO.QRIS.WWW0215ID20243249690030303UMI520465335802ID5902CF6015 JAKARTA SELATA610512760540550000530336062360525db913be449be4568b21c4b19e0703A0163041909"
	}
}