Testing Encrypted Card and CVV in Register Token Requests
If you plan to submit an encrypted account number and/or card validation number in your Register Token request, you must certify your transactions using the following procedure.
To test using an encrypted account number and/or card validation number in your Register Token request:
-
Obtain the latest key from this URL: https://request.eprotect.vantivprelive.com/eProtect/keys.json. The URL displays information similar to the following:
{"publicKey":{"modulus":"bc637dd74ba76507dad5af1c7ad6f97dbef5298c3b9f74caea7301347db7b4 a8c37f26491863100667246fd45071f3346bf62239f9b117d06fb67861b66ad0d158beeddd2f6f28be93d84 6f4c8f9ba1bd7e8f186f36cab0e432f22b3d732c221a9ff00a9bfacb88b24503e2695fd7237835d4936477b 21289478906a49b164f52503c20eb29f11fcbda2af94deb9a0bfde5a4589276897436315c5d664d60bf1065 0164f509283aed39747ad5d6cb2bbe54e1b42306e5db37dfd42dcbfcc689e0ddfe3bc9cb22ae7018e5a4a1f f39813584ac7bd6d6d65ca763f0a672da454081ea20e8b1d403316d80b9353ba396bea8962b1a7d2f775c76 612d857c1f7594f","exponent":"10001","keyId":"1"},"visaCheckout":{"apiKey":"UHTJ5A1SMG3P C81Y1CJT13x6XM0ekIIdixNrIMcPe8KI4GgNg"}}
The key changes daily. In the production environment, each key expires after 1 year. Keys do not expire in the Pre-Live environment.
-
Verify that your cnpAPI template is coded correctly for this transaction type (see Register Token Transactions.)
-
Using the data for Order Ids encrypted_1 through encrypted_4 from Table 2-34 and the key information from the URL, encrypt the supplied values using RSA-OAEP SHA1.
-
Verify that your
registerTokenResponse
values match those shown in the Key Response Elements section of Table 2-34. The complete token values are not defined in the table, because the system generates the tokens dynamically according to your token scheme.
TABLE 2-34 Encrypted Register Token Test Data
orderId |
Supplied Data Elements |
Key Response Elements |
||
---|---|---|---|---|
Element |
Value |
Element |
Value |
|
encrypt_1
|
<encryptionKeyId> <encryptedAccountNumber> <encryptedCardValidationNum>
|
Value from URL Encrypt this value: 4457119922390123 Encrypt this value: 367
|
<cnpToken> <bin> <type> <response> <message> |
value per token scheme 445711 VI 801 Account number was successfully registered |
encrypt_2
|
<encryptionKeyId> <encryptedAccountNumber> <encryptedCardValidationNum> |
Value from URL Encrypt this value: 4457119999999999 None |
<cnpToken> <response> <message> |
none returned 820 Credit card number was invalid |
encrypt_3
|
<encryptionKeyId> <encryptedAccountNumber> <encryptedCardValidationNum>
|
Value from URL Encrypt this value: 4457119922390123 Encrypt this value: 367
|
<cnpToken> <bin> <type> <response> <message> |
value per token scheme 445711 VI 802 Account number was previously registered |
encrypt_4
|
<encryptionKeyId> <encryptedAccountNumber> <encryptedCardValidationNum> |
Value from URL Encrypt this value: 4457119922390123, but change one character in the encrypted value. Encrypt this value: 367 |
<response> <message>
|
540 Hard Decline - Decryption Failed
|