Card Tokenization

Example request:

{
    "card": {
        "number": "4111111111111111",
        "exp_month": "12",
        "exp_year": "29",
        "cvc": "123"
    },
    "source": "card"
}

Example response:

{
    "token": "M4oSP7QJzugrh5w3FWBUygW6",
    "objectType": "token",
    "card": {
        "fingerprint": "fa8b9de61c6bc8219e0fdf8b34c2ee52ca7119dfdf95a7dbbad9cdd3d6b2fc15",
        "brand": "VISA",
        "bank": "JPMORGAN CHASE BANK, N.A.",
        "first6": "411111",
        "last4": "1111",
        "mask": "41XX XXXX XXXX 1111",
        "expires": "2029-12-31"
    },
    "created": "2020-05-16T19:24:18.999Z",
    "type": "card"
}

👍

Client Side

This API is open for CORS, so you can run it direct from a client side javascript. The PUBLIC key is not a secret and can be included in the client side javascript.

🚧

Use the PUBLIC key

Notice that it is the PUBLIC key that are used for tokenization calls. That is so you can do the tokenization calls from client side javascript. That way you dont have to transmit or store any card number on your server, hence you will not require any PCI certification.

❗️

Avoid PCI requirements - call client side!

If you collect card data and send the tokenization server-side, you will transmit cardholder data, hence you will require PCI certification. This API will only help you to avoid the PCI certification requirement if it is called client side, direct from the clients browser to HIPS. The token you receive from the tokenization api can however be stored server-side, and then be used for all future communication with HIPS in regards to the underlying card.

Read more about the Tokenization here: Client Side Tokenization (hips.js)