diff --git a/index.html b/index.html index 2a589ace..c49c86b8 100644 --- a/index.html +++ b/index.html @@ -579,10 +579,12 @@
+ A PaymentRequest's payerAddress attribute is populated + when the user provides a payer address (commonly referred to as a + billing address). It is null by default. When a user provides a payer + address, the payer address changed algorithm runs. +
++ On some user agents, some attributes of payerAddress might be + redacted until the user accepts the payment request, at which + point all the user-provided details of payerAddress become + available. +
++ A PaymentRequest's onpayeraddresschange attribute is an + EventHandler for a PaymentRequestUpdateEvent named + "payeraddresschange". +
+@@ -1850,6 +1884,14 @@
dictionary PaymentValidationErrors { - PayerErrorFields payer; + PayerErrors payer; AddressErrors shippingAddress; + AddressErrors payerAddress; DOMString error; };@@ -3290,6 +3344,12 @@
- dictionary PayerErrorFields { + dictionary PayerErrors { DOMString email; DOMString name; DOMString phone; };
- The PayerErrorFields is used to represent validation errors + The PayerErrors is used to represent validation errors with one or more payer details.
@@ -3492,6 +3552,19 @@
+ If the requestPayerAddress member + was set to true in the PaymentOptions passed to the + PaymentRequest constructor, then payerAddress will be the + un-redacted payer's address chosen by the user. +
+payeraddresschange
+ + The payer address changed algorithm runs when the user + provides a new payer address. It MUST run the following steps: +
++ The redactList optionally gives user agents the + possibility to limit the amount of personal information + about the recipient that the API shares with the merchant. +
++ For merchants, the resulting PaymentAddress object + provides enough information to, for example, calculate tax, + but, in most cases, not enough information to physically + locate and uniquely identify the payer. +
++ Unfortunately, even with the redactList, + recipient anonymity cannot be assured. This is because in + some countries postal codes are so fine-grained that they + can uniquely identify a recipient. +
+PaymentAddress
from user-provided
+ input with redactList.
+ PaymentAddress
from user-provided input with
+ redactList.
+ Further, if the shippingAddressErrors + or the payerAddressErrors member is present, the user agent SHOULD display an error specifically for each erroneous field of the shipping address. This is done by matching each present member of