---
url: >-
  https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/checkout/api/getCapture/index.md
description: >-
  The pre-authorization capture query API is used to obtain the confirmation
  status of payment pre-authorization. It is suitable for scenarios that need to
  verify whether the pre-authorization was successful, supporting payment
  methods worldwide. When calling, attention should be paid to performing it
  after synchronous return to avoid query exceptions. Request responses use JSON
  format, containing key parameters such as transaction ID, ensuring accurate
  tracking of each transaction's status.
---
# Pre-authorization Capture Query

```apidef
endpoint: POST /v4/capture/query
name: getCapture
summary: Query capture status
tags: Query, Capture
```

The pre-authorization capture query API is used to obtain the confirmation status of payment pre-authorization. It is suitable for scenarios that need to verify whether the pre-authorization was successful, supporting payment methods worldwide. When calling, attention should be paid to performing it after synchronous return to avoid query exceptions. Request responses use JSON format, containing key parameters such as transaction ID, ensuring accurate tracking of each transaction's status.

## 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 |
| └─ merchantCaptureId | string | M | Merchant website pre-authorization capture transaction number, globally unique |
| └─ merchantTransactionId | string | M | Original transaction number of the merchant website |

### Request Example

```json
{
  "accId": "2018092714313010016291",
  "clientId": "2018092714313010016",
  "signType": "SHA256",
  "sign": "898A3CBE981B3E2BF4E2B8D1A817D7E23EF93BC4293993EE545E36F4C87F2E79",
  "version": "1.0",
  "bizContent": "{\"merchantCaptureId\":\"2023070750000647\",\"merchantTransactionId\":\"202307075000324\"}"
}
```

## Response Parameters

| Parameter | Type | Description |
|--------|------|------|
| accId | string | Unique store identifier, which will appear in the response message after being added; inputting it means modifying the data |
| clientId | string | PingPong merchant number |
| signType | string | Supports MD5 , SHA256; for details, see the Signature Specification: /en/notes/guide/sign/ section of this document |
| sign | string | Signature; for details, see the Signature Specification: /en/notes/guide/sign/ section of this document. All parameters participate in the signature |
| code | string | Result status code, see the appendix Status Code Table: /en/notes/appendix/successCodeList/ |
| description | string | Result description |
| bizContent | string | Business response parameters |
| └─ transactionId | string | PingPong transaction number |
| └─ merchantTransactionId | string | Website transaction number |
| └─ currency | string | Transaction currency, ISO 4217 three-letter code, specific supported currencies see attachment Transaction currencies: /en/notes/appendix/transactionCurrency/ |
| └─ resultCode | string | Status result code |
| └─ resultDescription | string | Status result description |
| └─ amount | string | capture amount |
| └─ captureTime | string | capture initiation time, timestamp |
| └─ captureEndingTime | string | capture final state arrival time, timestamp |
| └─ status | string | Transaction status: status idempotence: /en/notes/guide/paystatus/ SUCCESS- success; FAILED- failure; PROCESSING- processing; |

### Response Example

```json
{
  "accId": "2023060217493010231446",
  "bizContent": "{\"amount\":\"200.000000\",\"captureTime\":\"1687335326000\",\"resultCode\":\"000000\",\"transactionId\":\"2023062150000332\",\"merchantTransactionId\":\"PMT-RRI7V42FR31687334823784\",\"currency\":\"USD\",\"resultDescription\":\"Transaction succeeded\",\"status\":\"SUCCESS\"}",
  "clientId": "2023060217493010231",
  "code": "001000",
  "description": "Successful request",
  "sign": "C550628F93D95A84AE89D18264CD9184520896908CEEEE77829F72196036A0AC",
  "signType": "SHA256"
}
```