New issue
Advanced search Search tips

Issue 673353 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Launch-OWP
Launch-Accessibility: ----
Launch-Exp-Leadership: ----
Launch-Leadership: ----
Launch-Legal: ----
Launch-M-Approved: ----
Launch-M-Target: ----
Launch-Privacy: ----
Launch-Security: ----
Launch-Test: ----
Launch-UI: ----
Rollout-Type: ----



Sign in to add a comment

Exp year and month sent to the merchant in PR should have exactly 2 digits.

Project Member Reported by se...@chromium.org, Dec 12 2016

Issue description

^^^

 

Comment 1 by rbyers@chromium.org, Dec 16 2016

Cc: rouslan@chromium.org
Is this 2-digit requirement documented anywhere?  I know the response details aren't part of the spec.  Are the docs just https://developers.google.com/web/fundamentals/discovery-and-monetization/payment-request/ ?
https://w3c.github.io/webpayments-methods-card/#basiccardresponse

expiryMonth
  The expiryMonth field contains a two-digit string for the expiry month of the card in the range 01 to 12.

expiryYear
  The expiryYear field contains a two-digit string for the expiry year of the card in the range 00 to 99.

Comment 3 by rbyers@chromium.org, Dec 16 2016

Ah right, sorry I forgot there was a separate spec for this.  Perfect!

Labels: -Type-Bug Type-Launch-OWP
Status: WontFix (was: Started)
Spec is changing to use 4 digit years.
Components: -UI>Browser>Autofill>Payments UI>Browser>Payments

Sign in to add a comment