Notification - API Paylater

7 min

About API Paylater Notification

NICEPAY provides push notifications via dbProcessUrl Merchant. The Merchant needs to reassure there is no Blacklist NICEPAY IP and should Whitelist NICEPAY IP to get the push notification only from NICEPAY's server.

Request Method	POST
Merchant Token	SHA256 ( iMid+ tXid + amt+ merchantKey)
IP	IP Public environtment Production: 103.20.51.34 103.20.51.33 18.98.96.50 IP Public environtment Dev: 103.20.51.39 103.20.51.40 18.98.96.54
User-Agent	User-Agent: Jakarta Commons-HttpClient/3.1

Notification Parameter Paylater Notification

When your dbProcessUrl received a notification, NICEPAY strongly recommend Merchant to verify the notification using the Status Inquiry - API Paylater.

Parameter	Type	Size	Description	Example / Notes
tXid	N	30	Transaction ID	PAYLOANTES06202212141610281704
merchantToken	AN	255	Merchant Token	0716e8cbb7bac584efa98df5021543e11fab1a520415f1382572eadcca81107f
referenceNo	ANS	40	Merchant Order Number	ord20221214161263
payMethod	N	2	Payment Method Code	06
amt	N	12	Payment Amount	25145
goodsNm	AN	100	Goods Name	Testing
matchCl	N	1	Payment Flag: Notification Match Amount Indicator	Null
status	A	1	Deposit Status: Notification Status Code 0 : Deposit 1 : Reversal	0
mitraCd	A	4	Mitra Code	KDVI
transTm	N	6	Transaction Time (HH24MISS)	155852
clientUserKey Mandatory if tokenize	AN	100	User key, must be unique for each Customer	1134431
billingNm	A	100	Buyer Name	John-Doe
transDt	N	8	Transaction date	20221214
currency	A	3	Currency	IDR
tokenizeUser	N	1	Transaction Tokenize Type	1
userToken	ANS		User Token	12345eea9-6234-6789-12r3-123re3456tt5

Additional Parameter for Others Payment Method Notification

Parameter	Type	Size	Description
mitraCd	A	4	Mitra Code
payNo	N	12	Payment Number
payValidDt	N	8	Expiry Date (YYYYMMDD)
payValidTm	N	6	Expiry Time (HH24MISS)
receiptCode	ANS	20	Authorization Number
mRefNo	AN	18	Reference Number
depositDt	N	8	Deposit Date (YYYYMMDD)
depositTm	N	6	Deposit Time (HH24MISS)

The Merchant Token received by the Notification Endpoint must compare internally to prevent fake/invalid notifications.

💡Example Case:

For example, you have a merchantKey that is used to generate a token, which is 1234. When the merchantToken generated by the Merchant is known, it is abcd, while the merchantToken obtained in the notification is abdd. Then the notification is considered fake/invalid.

Sample for Paylater Notification