---
url: >-
  https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/tokenization/cof/unbind/index.md
description: >-
  The unbind API is used to cancel the association between a bound payment card
  and user account. It applies to scenarios that require removing or updating
  payment methods, supporting payment card operations worldwide. By calling this
  API, developers can securely and efficiently manage users' payment card
  information. Key parameters include user identifier and the token of the card
  to be unbound.
---
# Unbind API

```apidef
endpoint: POST /v4/paymethod/unbind
name: Unbind API
summary: Unbind an international card
variant: International Card
tags: Tokenization, CardOnFile
```

The unbind API is used to cancel the association between a bound payment card and user account. It applies to scenarios that require removing or updating payment methods, supporting payment card operations worldwide. By calling this API, developers can securely and efficiently manage users' payment card information. Key parameters include user identifier and the token of the card to be unbound.

## Request Parameters

| Parameter | Type | Required | Description |
|--------|------|------|------|
| accId | string | M | Unique identifier for the store, which will appear in the response message after creation; inputting it means modifying the data |
| clientId | string | M | PingPong Merchant ID |
| signType | string | M | Supports MD5 , SHA256; for details, see the Signature Specification: /en/notes/guide/sign/ section of this document |
| sign | string | M | Signature; for details, see the Signature Specification: /en/notes/guide/sign/ section of this document. All parameters participate in the signature |
| version | string | M | Version number, currently fixed at 1.0, may be adjusted with changes to the interface in the future |
| bizContent | string | M | Collection of request parameters, with no limit on maximum length. Except for common request parameters, all other request parameters must be passed within this parameter, format: JSON string |
| └─ merchantUserId | string | M | Member ID, the user's member ID on the merchant's website |
| └─ requestId | string | M | Unique request number |
| └─ notificationUrl | string | M | Merchant notification address.
URL recommendation: use a complete URL with a publicly reachable domain name. Standard web ports are recommended (HTTPS defaults to 443 and HTTP defaults to 80). Ensure the URL can reliably receive PingPongCheckout asynchronous notifications. |
| └─ token | string | M | Authorization token |

### Request Example

```json
{
  "accId": "2022102018024210348883",
  "bizContent": "{\"merchantUserId\":\"12604896432523150\",\"requestId\":\"PMT-FTP2Z512691717055099734\",\"notificationUrl\":\"https://test-acquirerpay.pingpongx.com/qa/result.html\",\"token\":\"97b4e5b9fb4e53727ef7cbf0b25a3d42\"}",
  "clientId": "2022102018024210348",
  "sign": "CC99F6BCE0DB36D8F05C7BD95FCF21C11392490D8BA62D5E290F742D520262BD",
  "signType": "SHA256",
  "version": "1.0"
}
```

## Response Parameters

| Parameter | Type | Description |
|--------|------|------|
| code | string | Result status code, see the appendix Status Code Table: /en/notes/appendix/successCodeList/ |
| description | string | Result description |
| sign | string | Signature; for details, see the Signature Specification: /en/notes/guide/sign/ section of this document. All parameters participate in the signature |
| signType | string | Supports MD5 , SHA256; for details, see the Signature Specification: /en/notes/guide/sign/ section of this document |
| bizContent | string | Business response parameters |
| └─ token | string | authorization token |
| └─ merchantUserId | string | user id |
| └─ status | string | status, INVALID |

### Response Example

```json
{
  "bizContent": "{\"token\":\"97b4e5b9fb4e53727ef7cbf0b25a3d42\",\"merchantUserId\":\"12604896432523150\",\"status\":\"INVALID\"}",
  "code": "001000",
  "description": "Successful request",
  "sign": "394A51CD4D9DCEA3266988AAEBDDE113074A88D5B0BC964B8F45E474E0C1E694",
  "signType": "SHA256"
}
```