- From: Adrian Hope-Bailie <notifications@github.com>
- Date: Thu, 16 Feb 2017 13:47:43 -0800
- To: w3c/webpayments <webpayments@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 16 February 2017 21:48:43 UTC
> Interesting, so how would the provider of the token know how many digits to include? That's not something they'd know from this spec. It's specific to the local scheme rules. The spec must simply accommodate as many of the various rules that are out there. Another consideration is where this field holds just the "unmasked" PAN values (`1234`) or a masked PAN including the masking characters (`************1234`). If it is the latter I'd recommend calling the field `maskedPan` or similar. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments/issues/211#issuecomment-280471940
Received on Thursday, 16 February 2017 21:48:43 UTC