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

Minor HTML typo on Arch proposal #126

Merged
merged 1 commit into from Apr 21, 2016
Merged

Minor HTML typo on Arch proposal #126

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
40 changes: 20 additions & 20 deletions proposals/architecture/index.html
View file
Open in desktop
Expand Up @@ -229,7 +229,7 @@ <h2>Definitions</h2>
component that exercises the role of a payment app as described in the section <em>Roles</em>.
</p>

<p>An informative summary of the required capabilities of a payment app are:
<p>An informative summary of the required capabilities of a payment app are:</p>
<ul>
<li>It makes available a list of the payment methods for which it is able to process payment requests.
</li>
Expand All @@ -240,7 +240,6 @@ <h2>Definitions</h2>
supports and one of the payment methods that was listed as supported in the original request.
</li>
</ul>
</p>
<p>
Payment apps MAY implement algorithms given in this specification in any way desired, so long as
the end result is indistinguishable from the result that would be obtained by the specification's
Expand All @@ -255,7 +254,7 @@ <h2>Definitions</h2>
component that exercises the role of a payment mediator as described in the section <em>Roles</em>.
</p>

<p>A summary of the required capabilities of a payment mediator are:
<p>A summary of the required capabilities of a payment mediator are:</p>
<ul>
<li>It maintains a record of the available payment apps that it is able to pass payment requests to.
</li>
Expand All @@ -267,7 +266,6 @@ <h2>Definitions</h2>
of the corresponding payment request.
</li>
</ul>
</p>
<p>
Payment mediators MAY implement algorithms given in this specification in any way desired, so long as
the end result is indistinguishable from the result that would be obtained by the specification's
Expand Down Expand Up @@ -519,23 +517,25 @@ <h4>Filtering for capable Payment Apps</h4>
conclusion on the correct algorithm to use in mathcing payment method identifiers.
</div>
</section>
<h3>Extension Points</h3>
<p>The following extension points are defined for implemntation specific processing.</p>
<section>
<h4>Selection of Payment App</h4>
<p>Once the mediator has determined the set of <a>payment apps</a> that are able to process the
<a>payment request</a> it must select one and pass the request to it.</p>
<p>The <dfn>steps for selecting a payment app</dfn> are implementation specific and MAY involve user
interaction with the payer or may involve an algorithm that uses defaults and configuration data to
make the selection.</p>
<p>The input to this process is an ordered list of <a>payment apps</a> and the output is a single
<a>payment app</a>.</p>
</section>
<section
<h4>Passing the Payment Request to the Payment App</h4>
<p>The payment mediator must have some mechanism of passing the <a>payment request</a> to the
<a>payment app</a> that was selected following the <a>steps for selecting a payment app</a>.</p>
<p>The <a>payment request</a> MUST not be altered by the <a>payment mediator</a>.</p>
<h3>Extension Points</h3>
<p>The following extension points are defined for implemntation specific processing.</p>
<section>
<h4>Selection of Payment App</h4>
<p>Once the mediator has determined the set of <a>payment apps</a> that are able to process the
<a>payment request</a> it must select one and pass the request to it.</p>
<p>The <dfn>steps for selecting a payment app</dfn> are implementation specific and MAY involve user
interaction with the payer or may involve an algorithm that uses defaults and configuration data to
make the selection.</p>
<p>The input to this process is an ordered list of <a>payment apps</a> and the output is a single
<a>payment app</a>.</p>
</section>
<section>
<h4>Passing the Payment Request to the Payment App</h4>
<p>The payment mediator must have some mechanism of passing the <a>payment request</a> to the
<a>payment app</a> that was selected following the <a>steps for selecting a payment app</a>.</p>
<p>The <a>payment request</a> MUST not be altered by the <a>payment mediator</a>.</p>
</section>
</section>
</section>
</section>
Expand Down