Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Introduce the PaymentAppResponseData dictionary #84

Merged
merged 2 commits into from Jan 17, 2017
Merged

Introduce the PaymentAppResponseData dictionary #84

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ec536af
Change PaymentAppRequestData to PaymentAppRequest
Jan 16, 2017
1ebbb13
Introduce the PaymentAppResponse dictionary
Jan 12, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
72 changes: 47 additions & 25 deletions index.html
View file
Open in desktop
Expand Up @@ -573,16 +573,15 @@ <h3>Payment Method Support</h3>
<section>
<h3>Payment App Invocation and Response Data</h3>
<dl>
<dt><dfn id="dfn-app-request-data">payment app request data</dfn></dt>
<dd>data provided to the invoked payment app by the user agent to initiate a payment request. This data is a subset
of data input to the Payment Request API.
<dt><dfn id="dfn-app-request">payment app request</dfn></dt>
<dd>a request provided to the invoked payment app by the user agent to initiate a payment request. This request is a subset of the Payment Request.
<p class="note" title="JSON serialization">
The data passed between the user agent and the payment app will be serialized as JSON data.
</p>
</dd>
<dt><dfn id="dfn-app-response-data">payment app response data</dfn></dt>
<dd>data returned by an invoked payment app to the user agent, typically after payment authorization or other action
taken through the payment app. This data, which will vary according to payment method, is then returned to the payee via
<dt><dfn id="dfn-app-response">payment app response</dfn></dt>
<dd>a response returned by an invoked payment app to the user agent, typically after payment authorization or other action
taken through the payment app. This response, which will vary according to payment method, is then returned to the payee via
the Payment Request API as part of the payment response.</dd>
</dl>
</section>
Expand Down Expand Up @@ -1226,16 +1225,16 @@ <h3>Selection by the User</h3>
<h2>Payment App Invocation, Display and Response</h2>
<p>
Once the user has selected a payment app, the user agent is
responsible for preparing <a>payment app request data</a>, invoking the
responsible for preparing a <a>payment app request</a>, invoking the
payment app, providing the request data to the payment app, and
returning the payment app response through the Payment Request API.
</p>
<section id="sec-app-request-data">
<h3>Payment App Request Data</h3>
The <a>payment app request data</a> is conveyed using the following
<section id="sec-app-request">
<h3>Payment App Request</h3>
The <a>payment app request</a> is conveyed using the following
dictionary:
<pre class="idl">
dictionary PaymentAppRequestData {
dictionary PaymentAppRequest {
DOMString origin;
sequence&lt;PaymentMethodData&gt; methodData;
PaymentItem total;
Expand Down Expand Up @@ -1426,6 +1425,28 @@ <h3>
</ol>
</section>
</section>
<section id="sec-app-response">
<h3>Payment App Response</h3>
The <a>payment app response</a> is conveyed using the following
dictionary:
<pre class="idl">
dictionary PaymentAppResponse {
DOMString methodName;
object details;
};
</pre>
<dt><code>methodName</code> attribute</dt>
<dd>
The <a>payment method identifier</a> for the <a>payment method</a>
that the user selected to fulfil the transaction.
</dd>
<dt><code>details</code> attribute</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.
</dd>
</section>
<section>
<h3>Payment App Invocation</h3>
<p>
Expand All @@ -1435,7 +1456,7 @@ <h3>Payment App Invocation</h3>
user preferences). If the user selects a <a>user agent-based payment
app</a> to service the request, the <a>service worker</a> corresponding
to that application receives an event with the
<a>PaymentAppRequestData</a> containing information about the payment
<a>PaymentAppRequest</a> containing information about the payment
being requested. The event also contains a function that allows the
payment app to provide a <a>payment response</a> back to the
<a>payee</a>. This process is formally described in the following
Expand Down Expand Up @@ -1478,20 +1499,20 @@ <h3>
<pre class="idl">
[Exposed=ServiceWorker]
interface PaymentRequestEvent : ExtendableEvent {
readonly attribute PaymentAppRequestData data;
void respondWith(<a>Promise</a>&lt;<a>PaymentResponse</a>&gt;response);
readonly attribute PaymentAppRequest appRequest;
void respondWith(<a>Promise</a>&lt;<a>PaymentAppResponse</a>&gt;appResponse);
};
</pre>
<dl>
<dt><code>data</code> attribute</dt>
<dt><code>appRequest</code> attribute</dt>
<dd>
This attribute contains the <a>payment app request data</a> associated
This attribute contains the <a>payment app request</a> associated
with this <a>payment request</a>.
</dd>
<dt><code>respondWith</code> method</dt>
<dd>
This method is used by the payment app to provide a
<a>PaymentResponse</a> when the payment successfully completes.
<a>PaymentAppResponse</a> when the payment successfully completes.
</dd>
</dl>
<p>
Expand Down Expand Up @@ -1526,10 +1547,10 @@ <h3>
<code><a>PaymentRequestEvent</a></code> interface, with the
event type <code>paymentrequest</code>, which does not bubble,
cannot be canceled, and has no default action. </li>
<li>Set the <code>data</code> attribute of
<var>e</var> to a new <a>PaymentAppRequestData</a> instance,
<li>Set the <code>appRequest</code> attribute of
<var>e</var> to a new <a>PaymentAppRequest</a> instance,
populated as described in
<a href="#sec-app-request-data"></a>.
<a href="#sec-app-request"></a>.
</li>
<li>Dispatch <var>e</var> to <var>global</var>.</li>
<li>Wait for all of the promises in the <a>extend lifetime
Expand Down Expand Up @@ -1607,8 +1628,8 @@ <h3>Payment App Response</h3>
through resolution of the Promise provided to the <code>respondWith</code>
function of the corresponding <a>PaymentRequestEvent</a> dictionary.
The application is expected to resolve the Promise with a
<code>PaymentResponse</code> dictionary instance containing the payment
response information. In case of user cancellation or error, the
<code>PaymentAppResponse</code> instance containing the
payment response. In case of user cancellation or error, the
application may signal failure by rejecting the Promise.
</p>
<p>
Expand All @@ -1635,13 +1656,14 @@ <h3>Payment App Response</h3>
</p>
<ol>
<li>
Set <var>appResponse</var> to the <code>PaymentResponse</code> used to
resolve the <a>PaymentRequestEvent</a><code>.respondWith</code> Promise.
Set <var>appResponse</var> to the <code>PaymentAppResponse</code>
instance used to resolve the
<a>PaymentRequestEvent</a><code>.respondWith</code> Promise.
</li>
<li>
If <var>appResponse</var>.<code>methodName</code> is not present or
not set to one of the values from
<a>PaymentRequestEvent</a>.<code>data</code>, run the <a>payment app
<a>PaymentRequestEvent</a>.<code>appRequest</code>, run the <a>payment app
failure algorithm</a> and terminate these steps.
</li>
<li>
Expand Down