--- title: Network Token Sandbox Testing slug: network-token-sandbox-testing docTags: createdAt: 2026-01-07T14:48:08.072Z --- :::hint{type="warning"} This page is to test **Network Tokenisation** transactions only. ::: To request Network Tokens to be enabled on your account, contact your Account Manager or [Customer Support](mailto\:help@judopay.com). For a full overview of Network Tokenisation see, [Network Tokens](docId\:yUi7z1GNwHbWGvC2TCNjy). ## Sandbox Behaviour - Sandbox responses are designed to help you **validate **your integration logic and Network Token handling. - The sandbox environment is designed to simulate **common **Network Token scenarios. It may not reflect all production conditions or scheme responses. - Settlement behaviour and scheme-specific processing may differ in production. - Network Token sandbox test cards are only supported for the specific Network Token testing scenarios described below and **should not** be used to test other transaction types. - Network Token sandbox test cards do not have an associated expiry date. *** ## Disabling Network Tokenisation for a Specific Transaction To specify that network tokenisation should **not be used** for a specific transaction, use the `disableNetworkTokenisation` flag. The default setting = false, set it to **true **for any transactions where you do not want to use a Network Token: `disableNetworkTokenisation = true` This is only required to be set when generating the **payment session**.  :::hint{type="success"} This is even if network tokenisation registration has been enabled on the account. ::: *** ## Testing saveCard Testing a `/savecard` request using a Network Token. If `disableNetworkTokenisation = false` the sandbox will return: :::BlockQuote "networkTokenisationDetails": \{ "networkTokenProvisioned": true, "networkTokenUsed": false ::: The `networkTokenisationDetails` block provides details on whether a Network Token was **created**, or **created and used** for a transaction. To track if a Network Token was created, or created and used, check the **status **of these two fields: - `networkTokenProvisioned` - Indicates if a Network Token was generated. - `networkTokenUsed` - Indicates if the transaction was processed using a Network Token. The example sandbox response above indicates: - A Network Token was successfully provisioned. - The Network Token was not yet used in a transaction. *** ## Supported Network Token Sandbox Test Cards Below are the supported Network Token sandbox test cards and the expected behaviour for each. | Test Card Number | Test Scenario | Expected Sandbox Behaviour | | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 4111110956623818 | **Network Token provisioning fails**.

This test card simulates a scenario where a Network Token is not provisioned. | The response indicates Network Tokenisation has failed. 
“disableNetworkTokenisation": false,
"amount": "1.01",
"authCode": "1",
"networkTokenisationDetails": \{
"networkTokenProvisioned": false,
"networkTokenUsed": false | | 4111115748240383 | **Network Token provisioned, transaction fails**.

This test card simulates a scenario where a Network Token provisioning succeeds, then the transaction fails during processing. | Response includes `disableNetworkTokenisation`

If `disableNetworkTokenisation = false`
The `networkTokenisationDetails `object is returned. | | 4111111884228068 | **Network Token created on the first card entry**.

This test card simulates a scenario where a Network Token is created the first time a customer enters their card details.

Any subsequent transactions will use the saved Network Token. | For the **initial **transaction (using the card number), a  Network Token is provisioned during the transaction:
`networkTokenProvisioned = true`

For **subsequent **transactions (using the saved Network Token) the previously provisioned Network Token is reused.
**Note**: A new Network Token is **not **created.
`networkTokenProvisioned = false`

In both cases, transactions that **are not** `/savecard` requests, the Network Token is used to process the payment:
`networkTokenUsed = true` | | 4111110829811335 | **Network Token provisioned when using an existing card token**.

This test card simulates a scenario where Network Token is not created during the initial card payment, but is provisioned later when a previously saved card token is used.

Any subsequent transactions will use the saved Network Token. | For the **initial **transaction (using the card number), the payment is processed as a **standard **card (PAN) transaction:
As a Network Token has not been provisioned, a networkTokenisationDetails object is **NOT **returned.

For **subsequent** transactions the saved Network Token will be used:
`networkTokenProvisioned = true`
`networkTokenUsed = true` | | 4111116640745172 | **Account details updated via the Network Token**.

This test card simulates a scenario where the card issuer has updated the underlying card details associated with a Network Token (for example, due to card reissuance or replacement). | The response indicates an account details update has occurred, by returning:
\{
"networkTokenisationDetails": \{
"accountDetailsUpdated": true
}
} | *** ### Testing an Account Updater Event Testing requires two transactions to be performed: 1. Submit a transaction using the physical test card details. :::hint{type="info" indent="1"} Use this Visa test card in the production sandbox: `4111116640745172` ::: :::Paragraph{indent="1"} This prepares the Account Updater scenario by **provisioning and using** a Network Token. ::: :::Paragraph{indent="1"} The response should contain: ::: :::BlockQuote{indent="1"} \{ "networkTokenProvisioned": true, "networkTokenUsed": true, "accountDetailsUpdated": false } ::: 2. Submit a subsequent transaction using the **Judopay Card Token** returned for that card. This simulates **an update** to the underlying card details. :::Paragraph{indent="1"} The response should contain: ::: :::BlockQuote{indent="1"} \{ "networkTokenProvisioned": false, "networkTokenUsed": true, "accountDetailsUpdated": true } ::: The scenario can be tested using customer-initiated, merchant-initiated or recurring transaction types. The deciding factor is whether the request uses the physical test PAN or the associated Judopay Card Token: | **Request Credential** | **Simulated Behaviour** | | ---------------------- | -------------------------------------- | | Physical test PAN | Prepares the Account Updater scenario. | | Judopay Card Token | Triggers the Account Updated scenario. | Check the returned `virtualPan` block for the Network Token details associated with the simulated update in the [response](docId\:ZXd03ZbA8PNS25t07QlaB). *** ### Response Fields Example transaction response where a Network Token was created and used: :::BlockQuote "disableNetworkTokenisation": false, "amount": "1.01", "authCode": "1", "networkTokenisationDetails": \{ "networkTokenProvisioned": true, "networkTokenUsed": true, "accountDetailsUpdated": false, "virtualPan": \{ "lastFour": "7441", "expiryDate": "1126" } }, ::: | **Field** | **Description** | | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `networkTokenProvisioned` | Indicates whether a Network Token was created. | | `networkTokenUsed` | Indicates whether a Network Token was used in the transaction. | | `accountDetailsUpdated` | Indicates the card issuer has updated the underlying card details (for example, due to card reissuance or replacement), and the Network Token has been refreshed accordingly ensuring payments continue without interruption. | | `disableNetworkTokenisation` | Indicates whether tokenisation was disabled on a transaction level. | | `virtualPan` | Provides the PAN-formatted representation of the Network Token.
- `lastFour`
Last four of the virtual PAN.
- `expiryDate`
Expiry of the virtual PAN. |