Skip to content
This repository has been archived by the owner on Aug 27, 2021. It is now read-only.

add requestSecurityCode member to BasicCardRequest #78

Merged
merged 9 commits into from
Feb 13, 2020

Conversation

ianbjacobs
Copy link
Contributor

@ianbjacobs ianbjacobs commented Apr 24, 2019

Relates to
w3c/payment-request#97

It does not close that issue because this solution is payment method specific (and also does not address all the fields within Basic Card; however it does address the one that has been cited).

The following tasks have been completed:

  • Confirmed there are no ReSpec errors/warnings.
  • Added Web platform tests (link)
  • added MDN Docs (link)

Implementation commitments:

  • Chrome (link to issue)
  • Firefox
  • Edge (public signal)

Preview | Diff

Copy link
Member

@marcoscaceres marcoscaceres left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm ok with this

@marcoscaceres marcoscaceres changed the title requestSecurityCode add requestSecurityCode member to BasicCardRequest Apr 25, 2019
@marcoscaceres
Copy link
Member

@marcoscaceres
Copy link
Member

Sent a patch to Gecko. Note that it only patches the DOM implementation. We don't have a basic card UI.

Copy link
Collaborator

@rsolomakhin rsolomakhin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks right 👍

@marcoscaceres
Copy link
Member

We should probably add a manual test before merging.

@rsolomakhin
Copy link
Collaborator

rsolomakhin commented Apr 29, 2019 via email

@marcoscaceres
Copy link
Member

@rsolomakhin or @danyao, just wondering if this ever landed in Chrome?

@rsolomakhin
Copy link
Collaborator

This did not land in Chrome yet, @marcoscaceres .

@marcoscaceres
Copy link
Member

@rsolomakhin thanks for confirming. I guess we should wait till it's in Chrome before we land this, otherwise it might confuse people.

@marcoscaceres marcoscaceres added the blocked Blocked waiting on something label Nov 4, 2019
@Krystosterone
Copy link

I like this and believe this makes sense

@marcoscaceres
Copy link
Member

@rsolomakhin or @danyao, any update on the Chrome side about supporting this?

@rsolomakhin
Copy link
Collaborator

Hi @marcoscaceres , at this point we're investing heavily into payment handlers (both web based and OS-specific apps), so let's bypass waiting for Chrome to update it's basic-card implementation. Instead, let's update the spec and encourage payment apps that implement the basic-card standard to implement support for this new field as well. WDYT?

@marcoscaceres
Copy link
Member

Ah, just stumbled onto https://blog.chromium.org/2020/01/rethinking-payment-request-for-ios.html

Sounds like we might want to wrap up Basic Card entirely then.

@rsolomakhin
Copy link
Collaborator

rsolomakhin commented Feb 13, 2020

Sounds like we might want to wrap up Basic Card entirely then.

The Basic Card standard can exist for 3rd party payment handlers to implement and for merchants to use, if they wish. It's just not Google's cup of tea to implement it, though. We'd much rather focus on Payment Request and Payment Handler standards.

Edit: More precise wording.

@ianbjacobs
Copy link
Contributor Author

I think that we should maintain Basic Card as a Note.

@marcoscaceres
Copy link
Member

Ok, the above sounds like a plan.

@marcoscaceres marcoscaceres merged commit c07025c into gh-pages Feb 13, 2020
@marcoscaceres marcoscaceres deleted the requestsecuritycode branch February 13, 2020 17:13
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
blocked Blocked waiting on something
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants