---
title: "Binding Result Notification to Merchant"
method: POST
path: "https://{api-domain}/v1.0/debit/notify"
tags: ["Merchant Notification"]
---

# Binding Result Notification to Merchant

`POST https://{api-domain}/v1.0/debit/notify`

## Request

- The document declares no server URL.
- Auth: none declared. Required headers: `X-PARTNER-ID`, `X-EXTERNAL-ID`, `X-TIMESTAMP`, `X-SIGNATURE`

## Headers

- `X-PARTNER-ID` string, required
- `X-EXTERNAL-ID` string, required
- `X-TIMESTAMP` string, required
- `X-SIGNATURE` string, required
- `Authorization-Customer` string

## Request body

- BindingNotificationRequest: Payload sent by DOKU to the merchant's binding notification URL
  - `originalExternalId` string, required: The `X-EXTERNAL-ID` value from the original binding request submitted by the merchant. Used by the merchant to correlate this notification with the original binding request.
  - `additionalInfo` BindingNotificationAdditionalInfo, required: Additional information about the binding result
    - `custIdMerchant` string, required: The merchant's customer ID, echoed from the original binding request
    - `accountType` 'WALLET', required: The type of acquirer account. Always `WALLET` for OVO.
    - `tokenId` string, required: The DOKU token ID issued for this binding. Use this value as the `tokenId` in subsequent payment or balance inquiry requests. Only meaningful when `status` is `SUCCESS`.
    - `channelId` string, required: Identifies the acquirer and API version that processed the binding. Format: `{acquirerId} {apiVersion}` — always `OVO SNAP` for this channel.
    - `status` 'SUCCESS' | 'FAILED', required: Final binding result: - `SUCCESS` — OTP verified; token is active and ready for payment. - `FAILED` — OTP failed or timed out; token has been invalidated.
    - `authCode` string: The session ID / OTP auth code from the binding flow. Corresponds to the `sessionId` of the binding session in DOKU.

## Response `200`

Notification successfully received and processed by the merchant.

- BindingNotificationResponse: Expected acknowledgement from the merchant. DOKU only requires HTTP 200 — the response body is optional. If provided, it should follow the SNAP response code format: HTTP Status (3) + Service Code `07` (2) + Case Code (2).
  - `responseCode` string: SNAP-format response code. Example: `2000700` = HTTP 200 + service `07` + case `00` (Successful).
  - `responseMessage` string: Human-readable response message

## Other responses

- `400`: Merchant could not parse or validate the notification request
- `401`: Merchant rejected the notification due to invalid or unverifiable signature
- `500`: Internal server error on the merchant side

---

[API](https://skmtc.dev/doku/apis/direct-debit-core-system-notify-binding-to-merchant-emoney-o.md) - [All operations](https://skmtc.dev/doku/apis/direct-debit-core-system-notify-binding-to-merchant-emoney-o/llms.txt) - [OpenAPI document](https://skmtc.dev/doku/apis/direct-debit-core-system-notify-binding-to-merchant-emoney-o/revisions/7887174f57bc?raw)
