---
url: >-
  https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/tokenization/oneClickPayment/bindList/index.md
description: >-
  The contract inquiry interface is used to retrieve the list of payment cards
  already bound by the user. It is suitable for application scenarios that need
  to display or manage user payment methods, supporting major regions worldwide.
  Through this API, developers can implement one-click payment functionality to
  enhance user experience. Requests must include necessary authentication
  information, and the response contains key parameters such as card type and
  partially masked card number.
---
# Contract Inquiry Interface

```apidef
endpoint: POST /v4/paymethod/bind/list
name: Contract Inquiry Interface
summary: Query APM agreements
variant: APM
tags: Tokenization, APM
```

The contract inquiry interface is used to retrieve the list of payment cards already bound by the user. It is suitable for application scenarios that need to display or manage user payment methods, supporting major regions worldwide. Through this API, developers can implement one-click payment functionality to enhance user experience. Requests must include necessary authentication information, and the response contains key parameters such as card type and partially masked card number.

## 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 |
| └─ requestId | string | M | Unique Request Number |
| └─ merchantUserId | string | M | Member ID, the user's member ID on the merchant's website |
| └─ token | string | O | Authorization Token |

### Request Example

```json
{
  "accId": "2022102018024210348883",
  "bizContent": "{\"merchantUserId\":\"1260489643332523151\",\"requestId\":\"PMT-PX9Y2695PL1716799307746\",\"token\":\"43abe73a602bedb797a89aa22b0364fd\"}",
  "clientId": "2022102018024210348",
  "sign": "FE7BBF558C09740CC2B73F9DC8CF7701FEE9955D1FCB343BC36C921D9DA45138",
  "signType": "SHA256",
  "version": "1.0"
}
```

## Response Parameters

| Parameter | Type | Description |
|--------|------|------|
| sign | string | Signature Value |
| bizContent | string | Business Content |
| └─ bindInfos | object | Binding Information |
| └─ └─ bizType | string | CodeGrant |
| └─ └─ payMethod | string | Payment Method |
| └─ └─ clientId | string | PingPong Merchant Number |
| └─ └─ token | string | Token Value |
| └─ └─ accId | string | Shop Unique Identifier |
| └─ └─ merchantUserId | string | Member ID, User's Member ID on the Merchant Website |
| └─ └─ status | string | Status ACTIVE; INVALID |
| signType | string | Signature Method |
| code | string | Result Status Code |
| description | string | Result Description |

### Response Example

```json
{
  "bizContent": "{\"bindInfos\":[{\"bizType\":\"CodeGrant\",\"payMethod\":\"Boost\",\"clientId\":\"2022102018024210348\",\"token\":\"43abe73a602bedb797a89aa22b0364fd\",\"accId\":\"2022102018024210348883\",\"merchantUserId\":\"1260489643332523151\",\"status\":\"ACTIVE\"}]}",
  "code": "001000",
  "description": "Successful request",
  "sign": "95DA1D6FA9C86B0C0D087395DEBE3B52B231AFE4E6877A1A9A01F94BBFAC011E",
  "signType": "SHA256"
}
```