Re: [w3c/payment-request] Added based on issue 936 (#937)

@marcoscaceres commented on this pull request.



> +          In particular, the {{PaymentMethodData.data}} and
+          {{PaymentResponse.details}} members allow for the arbitrary exchange
+          of data. In light of the wide range of data models used by existing
+          payment methods, prescribing data specifics in this API would limit
+          its usefulness. The {{PaymentResponse.details}} member carries data
+          from the payment handler, whether Web-based (as defined by the
+          [[Payment Handler API]]) or proprietary. The <a>user agent</a> MUST
+          NOT support payment handlers unless they include adequate user
+          consent mechanisms (such as awareness of parties to the transaction
+          and mechanisms for demonstrating the intention to share data).

```suggestion
          In particular, the {{PaymentMethodData}}'s {{PaymentMethodData/data}} and
          {{PaymentResponse}}'s {{PaymentResponse/details}} members allow for the arbitrary exchange
          of data. In light of the wide range of data models used by existing
          payment methods, prescribing data specifics in this API would limit
          its usefulness. The {{PaymentResponse/details}} member carries data
          from the payment handler, whether Web-based (as defined by the
          [[[payment-handler]]]) or proprietary. The [=user agent=] MUST
          NOT support payment handlers unless they include adequate user
          consent mechanisms (such as awareness of parties to the transaction
          and mechanisms for demonstrating the intention to share data).
```

-- 
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-request/pull/937#pullrequestreview-576977814