How do we define dynamic data options?

[ianbjacobs]

In the draft today there are three options for dynamic data:

• None. This intends to address the use case where the merchant does not want dynamic data. Question: Does this mean that accountNumber is a PAN?
• Limited. This is for cases where the dynamic data is most likely a few digits (e.g., dynamic cvv I think).
• Full. This is for more advanced alphanumeric data.

Are these the right labels? Do we need a system that supports greater extensibility?

Ian

[ianbjacobs]

SRC .9 defines these values (and expects more to be defined):

• CARD_APPLICATION_CRYPTOGRAM = 0;
• CARDHOLDER_AUTHENTICATION_CRYPTOGRAM = 1;
• CARD_SECURITY_CODE = 2;

The sense I had from 29 May discussion was that we should align with these values. I will update the wiki accordingly.

[tblachowicz]

Quick Update: In EMVCo SRC API 1.0 specification [1] the DynamicDataType enumeration has been modified and now contains the following values:

• CARD_APPLICATION_CRYPTOGRAM_SHORT_FORM
• CARD_APPLICATION_CRYPTOGRAM_LONG_FORM
• DYNAMIC_CARD_SECURITY_CODE
• CARDHOLDER_AUTHENTICATION_CRYPTOGRAM
• NONE

[ianbjacobs]

I have updated the wiki accordingly.