Network Token Sandbox Testing

this page is to test network tokenisation transactions only to request network tokens to be enabled on your account, contact your account manager or https //help\@judopay com/ for a full overview of network tokensisation see, 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 above 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 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 "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" { "accountdetailsupdate" true } } response fields example transaction response where a network token was created and used "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 accountdetailsupdate 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