Re: [w3c/payment-handler] Drop PaymentInstrument in favor of MethodCapability (#302)

@anthonyvd,

> I think the proposal here is to move away from a world where the Payment Handler defines a set of instruments/hints and instead declares what types of payments it can process.

Ok, I see. In that case, exploring even further changes to simplify the API may be worthwhile. I don't see a reason to have a PaymentInstruments "container" that is "map-like". Perhaps this should instead be a single configuration call that would also provide a place for specifying icons, the "user hint", and so on:

```js
await registration.paymentManager.configure({
  icons: ['...'],
  userHint: '...',
  supportedMethods: [{
    method: 'basic-card',
    capabilities: {
     supportedNetworks: ['visa'],
     supportedTypes: ['credit']
    }
  }, {
    method: 'https://bobpay.com/'
 }]
});
```

-- 
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/302#issuecomment-387832880