- From: L. David Baron <notifications@github.com>
- Date: Tue, 13 Feb 2018 17:36:16 -0800
- To: w3c/payment-handler <payment-handler@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 14 February 2018 01:37:27 UTC
The [definition of `PaymentInstrument`](https://w3c.github.io/payment-handler/#paymentinstrument-dictionary) defines a `capabilities` member that is described as: > The capabilities member is a list of payment-method-specific capabilities that this payment handler is capable of supporting for this instrument. For example, for the basic-card payment method, this object will consist of an object with two fields: one for supportedNetworks, and another for supportedTypes. This seems to define how it works by example. I would expect something to say which specification is responsible for the definition for each payment method. For example, it's common for a specification like this to define a term that each specification for a payment method would then have to reference in order to define how it interacts here. It's also not clear how `capabilities` interactions with the possibility that `enabledMethods` has more than one member. (I got here from w3ctag/design-reviews#231.) -- 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/payment-handler/issues/249
Received on Wednesday, 14 February 2018 01:37:27 UTC