---
title: "Set pin V2"
method: POST
path: "/sc/v2/sc_set_pin/"
tags: ["Card PaySecure WS V2"]
---

# Set pin V2

`POST /sc/v2/sc_set_pin/`

<ul>
<li class="docBullet">This web service allows  set pin for a card/token.</li>
<li class="docBullet"> client should pass AES encrypted pin  to api.</li>
<li class="docBullet">Weak PINs would not be accepted. 'Weak PIN' refers to<ol> <li>PIN containing ascending digits, eg: 1234</li><li>PIN containing descending digits, eg: 4321</li><li>PIN containing a single digit repeated more than half the total number of digits in the PIN, eg: 1111, 4442, 71577, etc</li> </ol>For more information, contact Paymentology</li>
</ul>

## Headers

- `Session-Id` string, required
- `x-api-key` string

## Request body

- PSSetPinModel — This web service allows to set pin for a card/token. client should pass AES encrypted pin to api.
  - `client_id` integer, required — Unique identifier for the client which Paymentology will provide at outset
  - `iv` string, required — 16 bits initialization vector (IV) used while encryption
  - `pin` string, required — AES Encrypted pin Block
  - `token` integer, required — Public token for the card

## Response `200`

Successful Response

- PaySecureSetPinResponse — This model contains the response details of paysecure set pin api
  - `header` PaySecureSetPinHeader
    - `error_id` integer — error id
    - `error_desc` string — error message
  - `body` PaySecureSetPinBody
    - `message` string — information

## 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)