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

Fair point, I’ll update it

From: Nick Shearer <>
Reply-To: w3c/webpayments <>
Date: Monday, February 13, 2017 at 6:08 PM
To: w3c/webpayments <>
Cc: Subscribed <>
Subject: [w3c/webpayments] [Tokenized Card Payment] TokenCardRequest should inherit from BasicCardRequest (#212)

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 itssupportedTypes 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, view it on GitHub<>, or mute the thread<>.

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:

Received on Thursday, 16 February 2017 19:16:14 UTC