Network Tokenization Test Cases

Once you have been provisioned for Network Tokenization in the TokenEx Test environment, the following test cases can be used to verify your implementation prior to being provisioned for Network Tokenization in the TokenEx Production environment.

TokenEx will provide you with a list of test card numbers and corresponding security codes via the Solutions Architect working with your Sales representative or Client Success Manager. You may contact Sales or Client Success directly, via [email protected] or [email protected], respectively.

As you complete each of the following test cases, document the corresponding reference numbers in each API response as described below. Technical Support will use the reference numbers to verify the successful completion of each test case.

🚧

Important Test PAN Information

TokenEx test PANs can be leveraged to verify that the call to the card brands via our Network Token endpoints are successful. However, your Payment Services Provider (PSP) or Gateway may not accept the TokenEx test PAN in their environment. Please contact your PSP/Gateway to obtain a PAN for testing on their platform.

Test 1: Tokenize a PAN and security code using the Tokenize endpoint within the Network Token API

Using a PAN & Security Code pair from the test data list, send a request to the Tokenize endpoint and ensure the following conditions in the response:

1. The "Success" parameter equals "true"
2. The "NetworkResponse" JSON object is not null
3. The "NetworkResponse.StatusCode" parameter equals “0000”
4. The "NetworkResponse.TokenizationDecision" parameter equals “APPROVED”

Provide the "ReferenceNumber" response parameter for validation.

Test 2: Tokenize a PAN using the Tokenize endpoint within the Network Token API

Using only a PAN from the test data list, send a request to the Tokenize endpoint and ensure the following conditions in the response:

1. The "Success" parameter equals "true"
2. The "NetworkResponse" JSON object is not null
3. The "NetworkResponse.StatusCode" parameter equals “0000”
4. The "NetworkResponse.TokenizationDecision" parameter equals “APPROVED”

Provide the "ReferenceNumber" response parameter for validation.

Test 3: Tokenize a PAN with risk data using the Tokenize endpoint within the Network Token API

Using a PAN from the test data list, send a request which includes risk data to the Tokenize endpoint and ensure the following conditions in the response:

1. The "Success" parameter equals "true"
2. The "NetworkResponse" JSON object is not null
3. The "NetworkResponse.StatusCode" parameter equals “0000”
4. The "NetworkResponse.TokenizationDecision" parameter equals “APPROVED”

Provide the "ReferenceNumber" response parameter for validation.

Test 4: Suspend an active token using the LifecycleManagement endpoint within the Network Token API

Using a PAN from the test data list, generate a network token and verify the tokenization was successful.
NOTE: Alternatively, you can use an existing token which is already provisioned for network tokenization, and is in an “ACTIVE” state.

Using the token generated from the previous step, suspend the token by sending the appropriate request to the LifecycleManagement endpoint and verify the following conditions are met in the response:

1. The "Success" parameter equals "true"
2. The "NetworkResponse" JSON object is not null
3. The "NetworkResponse.StatusCode" parameter equals “0000”

Provide the "ReferenceNumber" from the successful suspension response for validation.

Test 5: Verify the suspended state of a token using the GetStatus endpoint within the Network Token API

Using a PAN from the test data list, generate a network token and verify the tokenization was successful.

Using the token generated from the previous step, suspend the token by sending the appropriate request to the LifecycleManagement endpoint and verify the result was successful:
NOTE: Alternatively, you can skip the previous steps by using an existing token which is already provisioned for network tokenization, and is in a “SUSPENDED” state.

Send a request to the GetStatus endpoint for the same token and verify the following conditions are met in the response:

1. The "Success" parameter equals "true"
2. The "NetworkResponse" JSON object is not null
3. The "NetworkResponse.StatusCode" parameter equals “0000”
4. The "tokenState" parameter equals "SUSPENDED"

Provide the "ReferenceNumber" from the successful GetStatus response for validation.

Test 6: Resume a suspended token using the LifecycleManagement endpoint within the Network Token API

Using a PAN from the test data list, generate a network token and verify the tokenization was successful.

Using the token generated from the previous step, suspend the token by sending the appropriate request to the LifecycleManagement endpoint and verify the result was successful:
NOTE: Alternatively, you can skip the previous steps by using an existing token which is already provisioned for network tokenization, and is in a “SUSPENDED” state.

Using the suspended token, resume the token by sending the appropriate request to the LifecycleManagement endpoint and verify the following conditions are met in the response:

1. The "Success" parameter equals "true"
2. The "NetworkResponse" JSON object is not null
3. The "NetworkResponse.StatusCode" parameter equals “0000”

Provide the "ReferenceNumber" from the successful resume response for validation.

Test 7: Generate a payment bundle using the GetPaymentBundle endpoint within the Network Token API

Using a PAN from the test data list, generate a network token and verify the tokenization was successful.
NOTE: Alternatively, you can skip the previous step by using an existing token which is already provisioned for network tokenization, and is in an “ACTIVE” state.

Using the token generated from the previous step, generate a payment bundle by sending the appropriate request to the GetPaymentBundle endpoint and verify the following conditions are met in the response:

1. The "Success" parameter equals "true"
2. The "NetworkResponse" JSON object is not null
3. The "NetworkResponse.StatusCode" parameter equals “0000”

Provide the "ReferenceNumber" from the payment bundle response for validation.

Test 8: Get card metadata and assets using the GetCardMetadata endpoint within the Network Token API

Using a PAN from the test data list, generate a network token and verify the tokenization was successful.
NOTE: Alternatively, you can skip the previous step by using an existing token which is already provisioned for network tokenization, and is in an “ACTIVE” state.

Using the token generated from the previous step, send a request to the GetCardMetadata endpoint and verify the following conditions are met in the response:

1. The "Success" parameter equals "true"
2. The "NetworkResponse" JSON object is not null
3. The "NetworkResponse.StatusCode" parameter equals “0000”

Using the Asset GUIDs from the GetCardMetadata response, send requests to the GetAsset endpoint for each available asset and verify the following conditions are met in the response:

1. The "Success" parameter equals "true"
2. The "NetworkResponse" JSON object is not null
3. The "NetworkResponse.StatusCode" parameter equals “0000”

Provide the "ReferenceNumber" from the successful GetCardMetadata response and each reference number for the GetAsset responses for validation.

Test 9: Delete an active token using the LifecycleManagement endpoint within the Network Token API

Using a PAN from the test data list, generate a network token and verify the tokenization was successful.
NOTE: Alternatively, you can skip the previous step by using an existing token which is already provisioned for network tokenization, and is in an “ACTIVE” state.

Using the token generated from the previous step, delete the token by sending the appropriate request to the LifecycleManagement endpoint and verify the following conditions are met in the response:

1. The "Success" parameter equals "true"
2. The "NetworkResponse" JSON object is not null
3. The "NetworkResponse.StatusCode" parameter equals “0000”

Provide the "ReferenceNumber" from the successful delete response for validation.