Universal Token Schemes

The specifics on the types of Universal Tokens and how to use them.

Token schemes are the output formats that sensitive data can be transformed into. They can follow a 1:1 mapping, where the same token is returned for the same input data each time, or a 1:many mapping, where different tokens are generated for the same input data upon each tokenization. The schemes to be utilized are based on your organization's specific needs.

Vaulted

Vaulted tokenization involves storing sensitive data and its corresponding tokens in a secure, centralized database managed by TokenEx. Tokens are generated using a cryptographically secure pseudorandom number generator (CSPRNG), ensuring that they are non-sensitive and mathematically unrelated to the original data. Vaulted tokenization offers the most flexibility, as a single vault/TokenEx ID can be used with multiple token schemes and can accommodate scenarios where a unique token needs to be generated each time a given value is tokenized, rather than generating the same token. Vaulted tokenization is ideal for businesses seeking robust data management where TokenEx handles the secure storage of the sensitive information.

PCI

Description: This format returns an alphanumeric, length-preserving token. For inputs greater than or equal to 15 digits, the token will retain first 6 and last 4. For inputs less than 15 digits, the token will retain first 4 and last 4.
Input Validation: Luhn compliant numeric values (0-9)
Input Length: 13-19
Token Mapping: 1:1
JSON value: 26

Example Input DataExample Token
4242424242424242424242APT0Oa4242
4111111111119411157SGH1119

sixANTOKENfour

Description: This format returns an alphanumeric, upper case, length preserving token retaining the original first 6 and last 4 digits of the input data.
Input Validation: Alphanumeric(a-Z,0-9)
Input Length: 14-38
Token Mapping: 1:1
JSON value: 9

Example Input DataExample Token
4242424242424242424242HU0OIW4242

sixTOKENfour

Description: This format will return a LUHN-compliant token retaining the original first 6 and last 4 digits of the card number.
Input Validation: Numeric(0-9), Luhn compliant
Input Length: 13-19
Token Mapping: 1:1
JSON value: 1

Example Input DataExample Token
4242424242424242424242925164242
41111111111194111117641119

sixTOKENfourNonLuhn

Description: This format will return a Non-LUHN-compliant token retaining the original first 6 and last 4 digits of the card number.
Input Validation: Numeric(0-9), Luhn compliant
Input Length: 13-19;
Token Mapping: 1:1
JSON value: 23

Example Input DataExample Token
4242424242424242424242925864242
41111111111194111qlziM1119

sixNTOKENfour

Description: This format will return a numeric length preserving token retaining the original first 6 and last 4 digits of the input data.
Input Validation: Numeric(0-9)
Input Length: 14-38
Token Mapping: 1:1
JSON value: 19

Example Input DataExample Token
999999999999999999999685129999
4111111111111941111179461119

sixASCIITOKENfour

Description: This format returns an ASCII, length preserving token retaining the original first 6 and last 4 digits of the input data.
Input Validation: Accepts any ASCII characters
Input Length: 14-38
Token Mapping: 1:1
JSON value: 16

Example Input DataExample Token
1324-123-48457961324-1TFTFO5796

fourANTOKENfour

Description: This format returns an alpha numeric, length preserving token retaining the original first 4 and last 4 digits of the input data.
Input Validation: Alpha-Numeric(a-Z,0-9)
Input Length: 12-38
Token Mapping: 1:1
JSON value: 10

Example Input DataExample Token
42424242424242424242ZYAV5124242

fourTOKENfour

Description: This format will return a LUHN-compliant token retaining the original first 4 and last 4 digits of the card number.
Input Validation: Numeric(0-9), Luhn compliant
Input Length: 13-19
Token Mapping: 1:1
JSON value: 2

Example Input DataExample Token
4242424242424242424276225864242

fourTOKENfourNonLuhn

Description: This format will return a Non-LUHN-compliant token retaining the original first 4 and last 4 digits of the card number.
Input Validation: Numeric(0-9), Luhn compliant
Input Length: 13-19
Token Mapping: 1:1
JSON value: 24

Example Input DataExample Token
4242424242424242424276925864242

fourNTOKENfour

Description: This format will return a numeric length preserving token retaining the original first 4 and last 4 digits of the card number.
Input Validation: Numeric(0-9)
Input Length: 12-38
Token Mapping: 1:1
JSON value: 20

Example Input DataExample Token
99999999999999999017819999

fourASCIITOKENfour

Description: This format returns an ASCII, length preserving token retaining the original first 4 and last 4 digits of the input data.
Input Validation: Accepts any ASCII characters
Input Length: 12-38
Token Mapping: 1:1
JSON value: 17

Example Input DataExample Token
1324-123-4841324DI2-484

ANTOKEN

Description: This format returns an alpha numeric, length preserving token.
Input Validation: Alpha-Numeric(a-Z,0-9)
Input Length: 4-38
Token Mapping: 1:1
JSON value: 12

Example Input DataExample Token
98765432105FR962FGT0

ANTOKENfour

Description: This format returns an alpha numeric, length preserving token retaining the original last 4 digits of the input data.
Input Validation: Alpha-Numeric(a-Z,0-9)
Length: 8-38
Token Mapping: 1:1
JSON value: 11

Example Input DataExample Token
42424242424242429TY2ZYAV5124242

ANTOKENAUTO

Description: This format automatically selects an ANTOKEN type token scheme that will retain the maximum number of original characters.
Input Validation: Alpha-Numeric(a-Z,0-9)
Input Length: 4-38
Token Mapping: 1:1
JSON value: 13

Character retention:
0 to 7 characters - none are retained
8 to 11 characters - last 4 are retained
12 to 13 characters - first 4 and last 4 are retained
14 or more characters - first 6 and last 4 are retained

Example Input DataExample Token
F447424ARBSBI3

ASCIITOKEN

Description: This format returns an ASCII, length preserving token
Input Validation: Accepts any ASCII characters
Input Length: 4-38
Token Mapping: 1:1
JSON value: 15

Example Input DataExample Token
1324-123-484D258G4F7R4FG

ASCIITOKENfour

Description: This format returns an ASCII, length preserving token retaining the original last 4 digits of the input data.
Input Validation: Accepts any ASCII characters
Input Length: 8-38
Token Mapping: 1:1
JSON value: 14

Example Input DataExample Token
2-5-9241G4F79241

ASCIITOKENAUTO

Description: This format automatically selects an ASCIITOKEN type token scheme that will retain the maximum number of original characters.
Input Validation: Accepts any ASCII characters
Input Length: 4-38
Token Mapping: 1:1
JSON value: 18

Example Input DataExample Token
[email protected][email protected]

GUID

Description: This format requires no validation and will return a GUID as the token.
Validation: none
Length: 1-1000
Token Mapping: 1:Many
JSON value: 4

Example Input DataExample Token
ThisIsATest25892e17-80f6-415f-9c65-7395632f0223

nGUID

Description: This format is used to tokenize any number combination.
Validation: Numeric(0-9)
Length: 1-1000
Token Mapping: 1:1
JSON value: 6

Example Input DataExample Token
2594758225892e17-80f6-415f-9c65-7395632f0223

nTOKEN

Description: This format returns a numeric, length preserving token.
Validation: Numeric(0-9)
Length: 4-38
Token Mapping: 1:Many
JSON value: 8

Example Input DataExample Token
98765432108631457809

nTOKENfour

Description: This format returns a numeric token while retaining length and last 4 digits of the input data.
Validation: Numeric(0-9)
Length: 8-38
Token Mapping: 1:Many
JSON value: 7

Example Input DataExample Token
98765432101234563210

nTOKENfour1to1

Description: This format returns a numeric token while retaining the length and last 4 digits of the input data.
Validation: Numeric(0-9)
Length: 8-38
Token Mapping: 1:1
JSON value: 28

Example Input DataExample Token
98765432101234563210

nTOKENAUTO

Description: This format automatically selects the NTOKEN type token scheme that will retain the maximum number of original characters.
Validation: Numeric(0-9)
Length: 8-38
Token Mapping: 1:1
JSON value: 21

Example Input DataExample Token
1234567898765432112345657142954321

SSN

Description: This format is used to tokenize a social security number.
Validation: Numeric(0-9)
Length: 9
Token Mapping: 1:1
JSON value: 5

Example Input DataExample Token
123456789958475126

TOKEN

Description: This format requires no validation and will return a random 38 character alpha-numeric token.
Validation: None
Length: 4-1000
Token Mapping: 1:1
JSON value: 22

Example Input DataExample Token
ThisIsATestDUH3JSLDTAYHUCO51MXY7IINZ8HLNDU90FMTTM

TOKENfour

Description: This format will return a LUHN-compliant token retaining the original last 4 digits of the card number.
Validation: Numeric(0-9), Luhn compliant
Length: 13-19
Token Mapping: 1:1
JSON value: 3

Example Input DataExample Token
4242424242424242635276725864242

TOKENfourNonLuhn

Description: This format will return a Non-LUHN-compliant token retaining the original last 4 digits of the card number.
Validation: Numeric(0-9), Luhn compliant
Length: 13-19
Token Mapping: 1:1
JSON value: 25

Example Input DataExample Token
4242424242424242635276925864242

ThreeTwo

Description: This format will return a 9 digit numeric token retaining the last 4 digits of input value.
Validation: Numeric(0-9)
Length: 9
Token Mapping: 1:1
JSON value: 32

Example Input DataExample Token
123456789048176789

Vaultless

Vaultless tokenization does not require storing sensitive data in a vault. Instead, tokens are algorithmically generated using the sensitive data combined with data points that are unique to the client's configuration. The resulting non-sensitive token is returned to the merchant and can be stored for future use. When this non-sensitive token is sent through the detokenization algorithm, TokenEx is able to use the token along with the unique data from the client's configuration to return the original sensitive data. Because neither the token nor the sensitive data is stored in a database, vaultless tokenization generally allows for quicker processing times, particularly in large scale batch processing. This also means that the client is responsible for storing their tokens, as once they are deleted from the client's systems, there is no record of this token on the TokenEx side. In contrast with vaulted tokenization, vaultless tokenization limits 1 scheme per TokenEx ID and will always generate the same token each time a given value is tokenized.

PCI

Description: This format returns an alphanumeric, length-preserving token. For inputs greater than or equal to 15 digits, the token will retain first 6 and last 4. For inputs less than 15 digits, the token will retain first 4 and last 4.
Input Validation: Luhn compliant numeric values (0-9)
Input Length: 13-19
Token Mapping: 1:1
JSON value: 26

Example Input DataExample Token
4242424242424242424242APT0Oa4242
4111111111119411157SGH1119

ANTOKEN4

Description: Returns an alphanumeric, length preserving token retaining the last 4 digits of the input.
Input Validation: Accepts numeric values (0-9)
Input Length: 9-512
Token Mapping: 1:1
JSON value: 29

Example Input DataExample Token
42424242424242429TY2ZYAV5124242
12345678901236ZOZ109MS0123

ANTOKEN512

Description: This format returns an alpha numeric, length preserving token.
Input Validation: Accepts numeric values (0-9)
Input Length: 5-512
Token Mapping: 1:1
JSON value: 30

Example Input DataExample Token
42424242424242428KR56689POLN11NV
5552713000L9632NB9P5

ASCII

Description: Returns an alphanumeric token that is double the length of input value.
Input Validation: Accepts any ASCII characters
Input Length: 5-128
Token Mapping: 1:1
JSON value: 27

Example Input DataExample Token
John.Doe85KOC8ExkNin7J6q91JwDT