Redundant payment data and display data? about src HOT 4 OPEN

One comment in the wiki on this:

"Remove to reduce confusion on redundant data, and perhaps reduce complexity for developer (e.g. two places to look up BIN, two expiration dates, etc.)"

from src.

My recollection from tokenization discussions is that there might be some display use cases for the original date info, but that it might different from dynamic date info.

from src.

There are two ways payment card is represented in SRC:

• For display purpose: MaskedCard that contains the following payment card details panBin, panLastFour, panExpirationYear, panExpirationMonth. In addition, when the card is tokenized the dictionary also contains tokenBinRange and tokenLastFour.
• For processing purpose: Card or PaymentToken contained in Payload.

from src.

We started discussion of this issue at the 12 June teleconference [1]. We usefully ended up discussing the overall shape of the response data. We did not, however, conclude what data should belong in the response data about displayable information.

[1] https://www.w3.org/2019/06/12-wpwg-minutes#item04

from src.