From d3200c6c734ee2c9bf9f35c90655da2a16de3a4a Mon Sep 17 00:00:00 2001
From: rvm4 <rvm4@fb.com>
Date: Sun, 10 Apr 2016 16:01:41 -0400
Subject: [PATCH 1/2] provide shipping address in PaymentResponse

---
 specs/paymentrequest.html | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/specs/paymentrequest.html b/specs/paymentrequest.html
index e7a3c6de..85c2a2fd 100644
--- a/specs/paymentrequest.html
+++ b/specs/paymentrequest.html
@@ -770,8 +770,9 @@ <h2>ShippingAddress interface</h2>
       <p>
         If the <a>requestShipping</a> flag was set to <code>true</code> in the <a>PaymentOptions</a>
         passed to the <a>PaymentRequest</a> constructor, then the <a>user agent</a> will populate the
-        <code>shippingAddress</code> field of the <a><code>PaymentRequest</code></a> object with
-        the user's selected shipping address.
+        <code>shippingAddress</code> field of the <a><code>PaymentRequest</code></a> and ultimately the
+        <a><code>PaymentResponse</code></a> object with the user's selected shipping address after
+        the user has accepted the payment.
       </p>
       <div class="issue" data-number="6" title="Write-up proposal for shipping address fields">
         The fields of the <a><code>ShippingAddress</code></a> interface are
@@ -820,6 +821,7 @@ <h2>PaymentResponse interface</h2>
         interface PaymentResponse {
           readonly attribute DOMString methodName;
           readonly attribute object details;
+          readonly attribute ShippingAddress? shippingAddress;
 
           Promise&lt;void&gt; complete(boolean success);
         };
@@ -840,6 +842,12 @@ <h2>PaymentResponse interface</h2>
         A <a>JSON-serializable object</a> that provides a <a>payment method</a> specific message used by the merchant to
         process the transaction and determine successful fund transfer.
       </dd>
+      <dt><code><dfn>shippingAddress</dfn></code></dt>
+      <dd>
+        If the <a>requestShipping</a> flag was set to <code>true</code> in the <a>PaymentOptions</a>
+        passed to the <a>PaymentRequest</a> constructor, then <a><code>shippingAddress</code></a> will
+        be the full and final shipping address chosen by the user.
+      </dd>
       </dl>
 
       <section>

From f485a7a0b85bf37d4fbd2452429329282cebcc47 Mon Sep 17 00:00:00 2001
From: Ade Bateman <bateman@acm.org>
Date: Thu, 28 Apr 2016 17:16:10 -0700
Subject: [PATCH 2/2] Add note to emphasise that the `details` field is
 populated by the app

---
 specs/paymentrequest.html | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/specs/paymentrequest.html b/specs/paymentrequest.html
index 85c2a2fd..1e4e0d69 100644
--- a/specs/paymentrequest.html
+++ b/specs/paymentrequest.html
@@ -840,7 +840,8 @@ <h2>PaymentResponse interface</h2>
       <dt><code><dfn>details</dfn></code></dt>
       <dd>
         A <a>JSON-serializable object</a> that provides a <a>payment method</a> specific message used by the merchant to
-        process the transaction and determine successful fund transfer.
+        process the transaction and determine successful fund transfer. This data is returned by the <a>payment app</a>
+        that satisfies the payment request.
       </dd>
       <dt><code><dfn>shippingAddress</dfn></code></dt>
       <dd>