---
title: "Token Approve Device Binding"
method: POST
path: "/pws/customerservice/v3/token/binding/approve/"
tags: ["Tokenization customer service"]
---

# Token Approve Device Binding

`POST /pws/customerservice/v3/token/binding/approve/`

Used to bind a device to an already provisioned token.

## Request body

- TokenDeviceBindingInternal
  - `api_call_unique_identifier` string, required — Unique number that must be passed at each API request. Identifier to make each API request unique
  - `client_id` integer, required — Unique identifier for the client which Paymentology will provide at outset
  - `deviceId` string, required — Device identification
  - `deviceIndex` string, required — Device index
  - `token` integer, required — Paymentology Public Token.
  - `tspToken` string, required — Token Service Provider Unique reference to the token
  - `user_id` string — User Id of the Customer who triggered the API request.
  - `remarks` string — Remarks for API request
  - `commentText` string — Comment related to the token status change. Maximum length of 500.

## Response `200`

Successful Response

- TokenActivateResponseModel
  - `header` Header
    - `error_desc` string, required — Error Description
    - `error_id` integer, required — Error Id
  - `body` TokenActivateResponse
    - `responseId` string
    - `tokenUniqueReference` string
    - `commentId` string
    - `errors` ErrorResponse[]
      - `category` string
      - `code` string
      - `description` string
      - `emitter` string

## Other responses

- `404` — Webservices does not exist
- `500` — Internal Server error

---

[API](https://skmtc.net/paymentology/apis/payapi-docs.md) · [All operations](https://skmtc.net/paymentology/apis/payapi-docs/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/paymentology/payapi-docs/revisions/a675891b0365/schema)