W3C home > Mailing lists > Public > public-payments-wg@w3.org > February 2017

[w3c/webpayments] [Tokenized Card Payment] TokenCardRequest should inherit from BasicCardRequest (#212)

From: Nick Shearer <notifications@github.com>
Date: Mon, 13 Feb 2017 18:08:05 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webpayments/issues/212@github.com>
_Ian requested some feedback on this proposal, which I am happy to provide. Note that my feedback should not be taken as an endorsement of the proposal itself._

The payment response of a tokenized card inherits from the basic card spec:

dictionary TokenizedCardResponse : BasicCardResponse {
    required DOMString cardLast4;
             DOMString tokenType;
             DOMString tokenRequesterId;

...but the request does not:

enum TokenCardType {

dictionary TokenCardRequest {
    sequence<DOMString>     supportedNetworks;
    sequence<TokenCardType> supportedTypes;

Additionally, it seems to me that basic card payment supports limiting the type of card whereas tokenized card does not:

enum BasicCardType {

dictionary BasicCardRequest {
    sequence<DOMString>     supportedNetworks;
    sequence<BasicCardType> supportedTypes;

Since it is a fairly common use case to limit payment to debit cards (versus credit) I wonder why tokenized card doesn't support this. If TokenCardRequest inherited from BasicCardRequest and renamed its`supportedTypes` property to `supportedTokenizationMethods` this could be very easily accomplished.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Received on Tuesday, 14 February 2017 02:08:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:24 UTC