AWS Security ChangesHomeSearch

AWS payment-cryptography: Update dCVV inputs and EMV tag mapping for Visa use case

Service: payment-cryptography · 2026-09-27 · Documentation low

File: payment-cryptography/latest/userguide/use-cases-issuers.networkfunctions.visa.md

Summary

Replaces the documented dCVV generation inputs (unpredictable number, track data) with card expiry date and service code, adds a mapping table tying API parameters to Visa/EMV data (ATC 9F36, PSN 5F34, expiry 5F24, service code), and switches example PANs from a 5-series to a 4-series test number in both generate and verify CLI examples.

Security assessment

The diff documents which card/CV parameters feed a payment cryptogram (DynamicCardVerificationValue) and their EMV tag equivalents; it is cryptographic-parameter documentation tied to a payment card verification API, but there is no evidence of a vulnerability, CVE, or credential/permission change being fixed, so it is hardening/guidance only.

Evidence

+`CardExpiryDate`, provided in the same format used by your other card verification calls.

Diff

diff --git a/payment-cryptography/latest/userguide/use-cases-issuers.networkfunctions.visa.md b/payment-cryptography/latest/userguide/use-cases-issuers.networkfunctions.visa.md
index 2a6d69b91..b8a54b31d 100644
--- a//payment-cryptography/latest/userguide/use-cases-issuers.networkfunctions.visa.md
+++ b//payment-cryptography/latest/userguide/use-cases-issuers.networkfunctions.visa.md
@@ -185 +185 @@ CAVV is not a user entered value (like CVV2) but is calculated by the issuer ACS
-dCVV (dynamic Card Verification Value) is a Visa-specific dynamic cryptogram used for contactless EMV transactions. It is known as early EMV and it provides enhanced security by generating a unique verification value for each transaction. The dCVV uses inputs including the Primary Account Number (PAN), PAN Sequence Number (PSN), Application Transaction Counter (ATC), unpredictable number, and track data. It is still used in some places, but has mostly been replaced by other algorithms like CVN18.
+dCVV (dynamic Card Verification Value) is a Visa-specific dynamic cryptogram used for contactless EMV transactions. It is known as early EMV and it provides enhanced security by generating a unique verification value for each transaction. The dCVV uses inputs including the Primary Account Number (PAN), PAN Sequence Number (PSN), Application Transaction Counter (ATC), card expiry date, and service code. It is still used in some places, but has mostly been replaced by other algorithms like CVN18.
@@ -188,0 +189,22 @@ For all available parameters see [DynamicCardVerificationValue](https://docs.aws
+The inputs to `DynamicCardVerificationValue` map to the following Visa authorization and EMV transaction data:
+
+`ApplicationTransactionCounter` (ATC)
+    
+
+The transaction counter maintained by the chip, incremented for each transaction. In EMV data this is tag `9F36`.
+
+`PanSequenceNumber`
+    
+
+The PAN sequence number that distinguishes cards sharing the same `[PAN](./terminology.html#terms.pan)`. In EMV data this is tag `5F34`.
+
+`CardExpiryDate`
+    
+
+The card's application expiration date (EMV tag `5F24`), provided in the same format used by your other card verification calls.
+
+`ServiceCode`
+    
+
+The three-digit service code carried in the card's track 2 (equivalent) data.
+
@@ -233 +255 @@ Take note of the `KeyArn` that represents the key, for example _arn:aws:payment-
-In this example, we will generate a dCVV for a contactless EMV transaction. The inputs include the PAN, PAN Sequence Number, Application Transaction Counter, unpredictable number, and track data. 
+In this example, we will generate a dCVV for a contactless EMV transaction. The inputs include the PAN, PAN Sequence Number, Application Transaction Counter, card expiry date, and service code. 
@@ -237,2 +259,2 @@ In this example, we will generate a dCVV for a contactless EMV transaction. The
-        --primary-account-number=5111112627662122 \
-        --generation-attributes DynamicCardVerificationValue='{ApplicationTransactionCounter=01,PanSequenceNumber=00,TrackData=12345,UnpredictableNumber=123}' \
+        --primary-account-number=4111112627662122 \
+        --generation-attributes DynamicCardVerificationValue='{ApplicationTransactionCounter=01,PanSequenceNumber=00,CardExpiryDate=1226,ServiceCode=201}' \
@@ -258 +280 @@ If AWS Payment Cryptography is able to validate, an http/200 is returned. If the
-        --primary-account-number=5111112627662122 \
+        --primary-account-number=4111112627662122 \
@@ -260 +282 @@ If AWS Payment Cryptography is able to validate, an http/200 is returned. If the
-        --verification-attributes DynamicCardVerificationValue='{ApplicationTransactionCounter=01,PanSequenceNumber=00,TrackData=12345,UnpredictableNumber=123}'
+        --verification-attributes DynamicCardVerificationValue='{ApplicationTransactionCounter=01,PanSequenceNumber=00,CardExpiryDate=1226,ServiceCode=201}'