[w3c/webpayments-crypto] Where to communicate responseEncryptionKey (#6)

The example shows the responseEncryptionKey as part of the method data for a particular payment method:

    supportedMethods: "https://example.com/bobpay",
    data: {
      [...method data...],
      dataSecurity: {
        responseEncryptionKey: {...}
      }

If the merchant supports multiple payment methods using the same payment service provider, would the responseEncryptionKey be provided in each supportedMethods construct? That would lead to redundant data, but perhaps that is OK.

-- 
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/webpayments-crypto/issues/6