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

Specification of required fields #114

Closed
wants to merge 4 commits into from
Closed

Specification of required fields #114

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d7c19dc
Merge remote-tracking branch 'refs/remotes/w3c/gh-pages' into gh-pages
Mar 20, 2016
72a39e1
Added card sub-brands to payment method identifier list (based upon m…
Mar 20, 2016
19f257c
Merge remote-tracking branch 'refs/remotes/w3c/gh-pages' into gh-pages
Apr 1, 2016
ff776e8
Proposal for dealing with specification of required fields
Apr 2, 2016
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
35 changes: 30 additions & 5 deletions specs/basic-card-payment.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -166,8 +166,33 @@ <h2>Payment Method Identifier</h2>
<h2>Payment Method Specific Data for the PaymentRequest constructor</h2>
<p>This section describes payment method specific data that is supplied as part of the <code>data</code>
argument to the PaymentRequest constructor.</p>
<p>There is no payment method specific data used by the PaymentRequest constructor when processing
Basic Card Payment methods.</p>
<p>The PaymentRequest constructor can optionally take a BaseRequest object to indicate where generally optional fields in the BasicCardResponse
must be returned for this instance</p>


<section>
<h2>BaseRequestData</h2>
<pre class="idl">
dictionary BaseRequestData {
sequence<DOMString> requiredFields;
};
</pre>

<p>
The <code>BasicRequestData</code> dictionary contains the following fields:
</p>

<dl>
<dt><dfn><code>requiredFields</code></dfn></dt>
<dd>The <code>requiredFields</code> field contains the list of fields that the Payment App must attempt to return, if this requirements cannot be met, e.g. the payment instrument does not support that field, an empty field must be returned to indicate this</dd>
</dl>

</section>

<div class="issue" title="Should BasicRequest be moved into PaymentRequestAPI">
This type should be generic to any PaymentRequest and should be moved to the PaymentRequest API as a base type
</div>

</section>

<section id="response">
Expand All @@ -179,10 +204,10 @@ <h2>Payment Method Response</h2>
<h2>BasicCardResponse</h2>
<pre class="idl">
dictionary BasicCardResponse {
required DOMString cardholderName;
DOMString cardholderName;
required DOMString cardNumber;
required DOMString expiryMonth;
required DOMString expiryYear;
DOMString expiryMonth;
DOMString expiryYear;
DOMString cardSecurityCode;

BillingAddress? billingAddress;
Expand Down