---
updatedAt: 2025-11-11T01:49:27.000Z
agentTools:
  projectIndex: https://docs.pci-proxy.com/llms.txt
---

# Token Formats

> 🚧 Although all formats are supported and compliant according to PCI DSS, we highly recommend using the Alias 2.0 format to run certain operations and obtain maximum security.
>
> Refer to the [Convert API](https://docs.pci-proxy.com/docs/convert-tokens) if you want to migrate from legacy formats to the new format.

# Alias 2.0

Alias 2.0 is our default token format. All the tokens in this format are unique. When using the Alias 2.0 format, we return an additional `fingerprint` parameter from our APIs. It's a unique identifier for the underlying card. This allows you to identify the same card usage across different customer accounts.

<Table align={["left","left","left"]}>
  <thead>
    <tr>
      <th>
        Possible characters
      </th>

      <th>
        Length (characters)
      </th>

      <th>
        Supported features
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        `A-Z`, `a-z`, `0-9`, `-`, `_`
      </td>

      <td>
        `32`
      </td>

      <td>
        Network Tokenisation\
        Manage API\
        Fingerprint
      </td>
    </tr>
  </tbody>
</Table>

## Example

| Input              | Output                            |
| :----------------- | :-------------------------------- |
| `4242424242424242` | `AABcH0Bq92s3kgAESIAAbGj5NIsAHWC` |

# Alias 2.0 - Length preserving

This format inherits all features and functionalities of the Alias 2.0 format with the difference that the length of the alias equals the length of the original card number.

<Table align={["left","left","left"]}>
  <thead>
    <tr>
      <th>
        Possible characters
      </th>

      <th>
        Length (characters)
      </th>

      <th>
        Supported features
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        `A-Z`, `a-z`, `0-9`, `-`, `_`
      </td>

      <td>
        `12`-`19`
      </td>

      <td>
        Network Tokenisation\
        Manage API\
        Fingerprint
      </td>
    </tr>
  </tbody>
</Table>

## Example

| Input              | Output             |
| :----------------- | :----------------- |
| `4242424242424242` | `AEcyq81HSCWWGihU` |

# CVV/CVC Alias

This format is only relevant for <Glossary>CVV</Glossary> or <Glossary>CVC</Glossary>s.

Due to PCI DSS requirement 3.2 the cvv token and the cvv must be deleted after the first detokenization/usage.

| Possible characters           | Length (characters) |
| :---------------------------- | :------------------ |
| `A-Z`, `a-z`, `0-9`, `-`, `_` | `24`                |

## Example

| Input | Output                     |
| :---- | :------------------------- |
| `123` | `Glb62cRnQV0jJxI0Iaeq9Wme` |

# Masked Alias

This format consists of the first 6 digits of the real credit card number, which corresponds to the BIN (Bank Identification Number) range. This is followed by the token in the form of 6 upper-case letters. The Masked Alias ends with the last 3-4 of the real credit card number. The length of the token varies based on the card brand.

| Possible characters | Length (characters) |
| :------------------ | :------------------ |
| `A-Z`, `0-9`        | Same as input       |

## Example

| Input              | Output             |
| :----------------- | :----------------- |
| `4242424242424242` | `424242ABCDEF4242` |

# Full substitution

This format only consists of digits.

| Possible characters | Length (characters) |
| :------------------ | :------------------ |
| `0-9`               | `20`                |