---
url: >-
  https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/checkout/api/getAccessToken/index.md
description: >-
  Obtain sdkAccessToken to verify merchant identity during the checkout process.
  Suitable for online stores or applications that need to integrate payment
  functionality, supporting global payment processing. Main features include
  generating temporary access tokens, with key parameters such as merchantId and
  apiKey, ensuring a secure and reliable payment experience.
---
# Get sdkAccessToken

```apidef
endpoint: POST /v4/session/init
name: Get sdkAccessToken
summary: Initialize the SDK access token
tags: OnePage, Payment, Session
```

Obtain sdkAccessToken to verify merchant identity during the checkout process. Suitable for online stores or applications that need to integrate payment functionality, supporting global payment processing. Main features include generating temporary access tokens, with key parameters such as merchantId and apiKey, ensuring a secure and reliable payment experience.

## 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 | C | Member ID, the user's member ID on the merchant's website |

### Request Example

```json
{
  "accId": "2022102018024210348883",
  "bizContent": "{\"merchantUserId\":\"1260489643332523151\"}",
  "clientId": "2022102018024210348",
  "sign": "FE7BBF558C09740CC2B73F9DC8CF7701FEE9955D1FCB343BC36C921D9DA45138",
  "signType": "SHA256",
  "version": "1.0"
}
```

## 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 |
| └─ sdkAccessToken | string | sdkAccessToken |

### Response Example

```json
{
  "accId": "2023042011040310224447",
  "bizContent": "{\"sdkAccessToken\":\"DDf2S7RR3K4LQ1715047351210\"}",
  "clientId": "2023042011040310224",
  "code": "000000",
  "description": "succeeded",
  "sign": "5033C47D3A1CF3E19A4B0EE0E566CE723D67E8BA236B828829BDE586CA999D2A",
  "signType": "SHA256"
}
```