Request Cryptogram

Request Cryptogram - Testing

The CryptoFetch API retrieves the cryptogram associated with the active Network Tokens for a card. This cryptogram is used to facilitate secure, tokenized transactions.

To successfully test CryptoFetch, the card must have an active Network Tokens provisioned with the network in the sandbox environment.

Refer to VGS Sandbox Network Token Provisioning for guidance on provisioning Network Tokens.

Points to Note

• For CMP accounts with ON-CREATE enrollment type:

  • Network Tokens are automatically provisioned when the card is created.

  • Perform a GET on the card ID to verify that the Network Tokens status is active.

  • Once verified, you can proceed with the CryptoFetch API call.

• For CMP accounts with MANUAL enrollment type:

  • Network Tokens are not provisioned by default.

  • Use the Network Tokens Provisioning endpoint to provision the Network Tokens manually.

  • Then, perform a GET to ensure the Network Tokens status is active before calling CryptoFetch.

• Do not use mock test cards for CryptoFetch testing:

  • Mock cards do not provision Network Tokens with networks.

  • Since CryptoFetch depends on active Network Tokens, it will not work with mock cards.

Testing Steps

• Create Cards: Use the Create Card API to register test cards that support Network Tokens provisioning in the sandbox.

• Provision Network Tokens (if required):

  • Skip this step forON-CREATE enrollment (Network Tokens is auto-provisioned).

  • For MANUAL enrollment, call the Network Tokens Provisioning endpoint.

• Verify Network Tokens Status: Use the GET Card API to check that the Network Tokens status is active.

• Call CryptoFetch API: Once the Network Tokens is active, use the CryptoFetch endpoint to retrieve the cryptogram for that token.