---
url: >-
  https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/notify/closeNotify/index.md
description: >-
  The order closure notification interface is used to send asynchronous
  notifications to merchants when an order is automatically or manually closed
  by the system. It is suitable for scenarios that require real-time awareness
  of order status changes. Key features include support for multiple closure
  reason identifiers and provision of detailed order information, ensuring that
  merchants can respond promptly and handle related business logic.
---
# Order Closure Notification

```apidef
endpoint: POST payment.close
name: Order Closure Notification
summary: Order-close webhook
tags: Notify, Close, Payment
```

The order closure notification interface is used to send asynchronous notifications to merchants when an order is automatically or manually closed by the system. It is suitable for scenarios that require real-time awareness of order status changes. Key features include support for multiple closure reason identifiers and provision of detailed order information, ensuring that merchants can respond promptly and handle related business logic.

## Request Parameters

| Parameter | Type | Required | Description |
|--------|------|------|------|
| accId | string | M | PingPong Store Number |
| clientId | string | M | PingPong Merchant Number |
| code | string | M | Status Code |
| description | string | M | Description |
| sign | string | M | Signature, for details see the Signature Convention: /en/notes/guide/sign/ section in this article |
| signType | string | M | Signature convention, supports MD5, SHA256, for details see the Signature Convention: /en/notes/guide/sign/ section in this article, all parameters are involved in the signature |
| bizContent | string | M | Response parameters are passed as a whole, with no limit on length |
| └─ transactionTime | string | M | Transaction initiation time, timestamp |
| └─ merchantTransactionId | string | M | Website transaction serial number |
| └─ transactionId | string | M | PingPong transaction serial number |
| └─ amount | string | M | Transaction amount, the precision depends on the currency. Please refer to the appendix Transaction Currencies: /en/notes/appendix/transactionCurrency/ |
| └─ currency | string | M | Transaction currency, ISO 4217 three-letter code. For specific supported currencies, see the attachment Transaction Currencies: /en/notes/appendix/transactionCurrency/ |
| └─ notifyType | string | M | Fixed value: RECHARGE, indicating the type of closure |
| └─ status | string | M | Transaction status: Status Idempotence: /notes/zh/guide/paystatus/ CLOSED - Order closed (Note: The notification for active or passive closure will only be sent if the closure notification address is provided); |
| └─ remark | string | O | Merchant extended field, can be used to specify certain parameters, and will be returned as is in the response body |

### Request Example

```json
{
  "clientId": "2023101115545610265",
  "code": "000000",
  "bizContent": "{\"amount\":\"1000.000000\",\"transactionId\":\"2024050650046448\",\"notifyType\":\"RECHARGE\",\"merchantTransactionId\":\"PMT-K52GNL5ZY21714991465240\",\"currency\":\"USD\",\"status\":\"CLOSED\"}",
  "sign": "6DA3C7E2F07F78464150BAA7450A3A06343B1E17D8D58A0F94A442A9F4F1FA90",
  "accId": "2023101115545610265482",
  "description": "Transaction succeeded",
  "signType": "SHA256"
}
```