Re: [w3c/payment-method-basic-card] Brand selection (#49)

> According buyer selected network, acquisition fees can differs. 

Ok, but, today, that's handled by payment method modifiers. That is:

```JS
// merchant supports
const methods =   {
    supportedMethods: "basic-card",
    data: {
      supportedNetworks: ["visa", "mastercard", "cb"],
      supportedTypes: ["credit"],
    },
  }

const visaFee = {
  label: "Visa processing fee",
  amount: { currency: "EUR", value: "3.00" },
};

const mastercardFee = {
  label: "MasterCard processing fee",
  amount: { currency: "EUR", value: "4.00" },
};

// When you pick one... 
const modifiers = [
  {
    additionalDisplayItems: [visaFee],
    supportedMethods: "basic-card",
    total: {
      label: "Total due",
      amount: { currency: "USD", value: "68.00" },
    },
    data: {
      supportedNetworks: ["mastercard"],
      supportedTypes: ["credit"],
    },
  },
  {
    additionalDisplayItems: [mastercardFee],
    supportedMethods: "basic-card",
    total: {
      label: "Total due",
      amount: { currency: "USD", value: "69.00" },
    },
    data: {
      supportedNetworks: ["mstercard"],
      supportedTypes: ["credit"],
    },
  },
];
```

If this is just for merchant fees, then the above has you covered, no? Hmm... I guess  you still need it if you need to route the payment. So maybe `BasicCardResponse` needs to have "type" and "network" and the browser needs to actually allow the user to pick with "mode" the card is operating under?   

PS: a friendly reminder to all that when exemplifying someone by gender, please use "she or he" or "he or she", or just "they".  


-- 
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-method-basic-card/issues/49#issuecomment-372283196