---
title: Notification - API Direct Debit
slug: en/nicepay-api-non-snap-notification-api-direct-debit
description: Information about Non-SNAP Payment API - Notification - Direct Debit API available on NICEPAY system
image: https://archbee-image-uploads.s3.amazonaws.com/ZHvSjR5ZrsoxwKbJa3xmo/LDiVDMG_an-uB2ZLqksaw_microsoftteams-image.png
icon: {"faIcon":"fa-solid fa-book"}
docTags:
createdAt: 2022-12-01T07:50:35.000Z
---
# About API Direct Debit Notification
***
NICEPAY will send push notifications via the `dbProcessUrl` parameter based on the Merchant information provided in the [Registration - API Direct Debit](docId\:yfZlLpmX5PMjgr6-qcMAj). 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 Direct Debit Notification
***
:::hint{type="info"}
When your `dbProcessUrl` received a notification, NICEPAY strongly recommend Merchant to verify the notification using the [Status Inquiry - API Direct Debit](docId\:k3CQyBZOjMwER6XQaFXEt).
:::
| **Parameter** | **Type** | **Length** | **Description** | **Example / Notes** |
| ----------------------------------------------------------------------------------------- | -------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| `tXid`
Required | N | 30 | Transaction ID | TNICECP04100202210201205567417 |
| `merchantToken`
Required | AN | 255 | Merchant Token | ecd49958d29595d09cd7ccab6057e9db119dfeb83676c27fb7649d3393b911aa |
| `referenceNo`
Required | ANS | 40 | Merchant Order Number | ORD20250307130386 |
| `mitraCd`
Required | A | 4 | [Mitra Code](docId\:Tm257gq3DxgZf98uZ0l33)
| JENC |
| `payMethod`
Required | N | 2 | [Payment Method Code](docId\:IifMsRUUw7j9VMWeFJz97) | 04 |
| `payNo`
Optional | N | 20 | Payment Number | 504100002539 |
| `payValidTm`
Optional | N | 6 | CVS Expiry Time (`HH24MISS`) | null |
| `payValidDt`
Optional | N | 8 | Expiry Date (`YYYYMMDD`) | null |
| `amt`
Required | N | 12 | Payment Amount | 10000 |
| `clientUserKey`
Mandatory if tokenize
| AN | 100 | User Key, Must be Unique for Each Customer
| 1134431 |
| `userToken`
Optional | ANS | 255 | User Token | 12345eea9-6234-6789-12r3-123re3456tt5 |
| `tokenizeUser`
Optional | N | 1 | Transaction Tokenize Type
| 1 |
| `transDt`
Optional | N | 8 | Transaction Date | 20221020 |
| `transTm`
Optional | N | 6 | Transaction Time | 120803 |
| `currency`
Required | A | 3 | Currency | IDR |
| `goodsNm`
Required | AN | 100 | Goods Name | John Doe |
| `billingNm`
Required | A | 100 | Billing Name | John-Doe |
| `receiptCode`
Required | ANS | 20 | Authorization Number | 951523387713 |
| `instmntType`
Required | N | 2 | [Installment Type Code](docId\:RT2C32S9hfl_aOhYoebv5) | 2 |
| `instmntMon`
Required | N | 2 | Installment Month
`1`: 1 Month/Full Payment, if `instmntType`*:* *null/1*
`3`: 3 Months
`6`: 6 Months
`12`: 12 Months | 1 |
| `mRefNo`
Required | AN | 18 | Reference Number | 202503071335234 |
| `matchCl`
Required | N | 1 | Payment Flag: [Notification Match Amount Indicator](docId:_wBzuZhpBdoyCDEhLbBX9) | 1 |
| `status`
Required | A | 1 | Deposit Status: [Notification Status Code](docId\:UCni27UfonCK8_zTtM-mV)
`0` : Deposit
`1` : Reversal | 0 |
:::hint{type="warning"}
Merchant must compare again every Merchant Token received by the Notification 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 Direct Debit Notification
***
:::CodeblockTabs
Sample POST for Direct Debit) Notification
```none
merchantToken=ecd49958d29595d09cd7ccab6057e9db119dfeb83676c27fb7649d3393b911aa
goodsNm=John Doe
referenceNo=ORD20250307130386
transTm=133600
tXid=TNICECP04104202503071335233256
amt=10000
receiptCode=951523387713
instmntType=2
billingNm=John Doe
matchCl=1
mRefNo=202503071335234
payMethod=04
currency=IDR
instmntMon=1
transDt=20250307
status=0
```
:::