PApaymentology
Card PaySecure WS

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">WeakPINs 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>
post/sc/sc_set_pin/

Request

  • Base URL
    https://api.uat.paymentology.com/ppws/api
  • URL
    https://api.uat.paymentology.com/ppws/api/sc/sc_set_pin/
  • Auth
    none declared. Required headers: Session-Id

Headers

Session-Idstring required

Session Id for Current Request - 32 byte AES key encrypted by RSA Public Key passed in Header in every PaySecure API call.

x-api-keystring

The X-API key is sent to the client in an email during client creation

Request body

client_idinteger required

Unique identifier for the client which Paymentology will provide at outset

ivstring required

16 bits initialization vector (IV) used while encryption

pinstring required

AES Encrypted pin Block

tokeninteger required

Public token for the card

Example request

{
  "client_id": 760131,
  "iv": "Xb6qbV2L6d1F92YU",
  "pin": "+AyrdXnhXhXb6qbV2L6d1F92YUc=",
  "token": 311012081
}

Response

Successful Response

Example response

{
  "header": {
    "error_desc": "success"
  },
  "body": {
    "message": "pin set success"
  }
}

Changes

No recorded changes to this operation across all 2 revisions of this API.