--- a/latest/use-cases/index.html Tue Mar 17 00:40:52 2015 -0400
+++ b/latest/use-cases/index.html Tue Mar 17 01:33:32 2015 -0400
@@ -874,7 +874,7 @@
There are types of information, such as personally identifiable information,
that <tref title="payee">payees</tref> do not need to know for some
transactions. Limiting sensitive information to be transmitted to entities
-involved in a payment on a purely need-to-know basis increases security
+involved in a payment on a purely need-to-know basis increases security
while ensuring regulatory compliance.
</dd>
</dl>
@@ -955,115 +955,41 @@
</p>
<section>
- <h5>High Priority</h5>
- <dl class="dl-horizontal">
- <dt></dt>
- <dd>
-
- </dd>
- <dt>Goals</dt>
- <dd>
-Increased user choice,
-Improved user experience,
-Greater security,
-Minimal standardization,
-Regulatory acceptance,
-Innovation,
-Lower Costs,
-Transparency,
-Automatability,
-Portability,
-Monetization,
-and Rapid, widespread adoption.
- </dd>
- <dt>Motivation</dt>
- <dd>
-
- </dd>
- <dt>Privacy / Security</dt>
- <dd>
-
- </dd>
- <dt>Exceptions</dt>
- <dd>
-
- </dd>
- </dl>
- </section>
-
- <section>
<h5>Medium Priority</h5>
<dl class="dl-horizontal">
- <dt></dt>
+ <dt>Coupons</dt>
<dd>
-
+JustPopcorn sends Marco a special discount offer given Marco's past purchases.
+The offer takes the form of a coupon that may be applied during payment.
</dd>
<dt>Goals</dt>
<dd>
-Increased user choice,
-Improved user experience,
-Greater security,
-Minimal standardization,
-Regulatory acceptance,
-Innovation,
-Lower Costs,
-Transparency,
-Automatability,
-Portability,
-Monetization,
-and Rapid, widespread adoption.
+Automatability, and Portability,
</dd>
<dt>Motivation</dt>
<dd>
-
- </dd>
- <dt>Privacy / Security</dt>
- <dd>
-
- </dd>
- <dt>Exceptions</dt>
- <dd>
-
+Providing a mechanism to apply digital coupons before a payment is initiated
+helps price conscious customers as well as merchants attempting to research
+price sensitivity.
</dd>
</dl>
- </section>
- <section>
- <h5>Low Priority</h5>
<dl class="dl-horizontal">
- <dt></dt>
+ <dt>Loyalty Cards</dt>
<dd>
-
+Terry uses his FoodCo loyalty card when purchasing his weekly groceries, which
+gives him a discount on gas purchases performed at the FoodCo gas station.
</dd>
<dt>Goals</dt>
<dd>
-Increased user choice,
-Improved user experience,
-Greater security,
-Minimal standardization,
-Regulatory acceptance,
-Innovation,
-Lower Costs,
-Transparency,
-Automatability,
-Portability,
-Monetization,
-and Rapid, widespread adoption.
+Improved user experience, and Portability,
</dd>
<dt>Motivation</dt>
<dd>
-
- </dd>
- <dt>Privacy / Security</dt>
- <dd>
-
- </dd>
- <dt>Exceptions</dt>
- <dd>
-
+Loyalty cards may be used at multiple locations to augment the price of a
+particular good.
</dd>
</dl>
-
</section>
</section>
@@ -1080,113 +1006,49 @@
<h4>Discovery of Accepted Schemes</h4>
<p>
</p>
+
<section>
<h5>High Priority</h5>
<dl class="dl-horizontal">
- <dt></dt>
- <dd>
-
- </dd>
- <dt>Goals</dt>
+ <dt>Ubiquitous Schemes</dt>
<dd>
-Increased user choice,
-Improved user experience,
-Greater security,
-Minimal standardization,
-Regulatory acceptance,
-Innovation,
-Lower Costs,
-Transparency,
-Automatability,
-Portability,
-Monetization,
-and Rapid, widespread adoption.
- </dd>
- <dt>Motivation</dt>
- <dd>
-
- </dd>
- <dt>Privacy / Security</dt>
- <dd>
-
- </dd>
- <dt>Exceptions</dt>
- <dd>
-
- </dd>
- </dl>
- </section>
-
- <section>
- <h5>Medium Priority</h5>
- <dl class="dl-horizontal">
- <dt></dt>
- <dd>
-
+A game store Web site accepts payment via credit card, echeck, and
+operator billing.
</dd>
<dt>Goals</dt>
<dd>
Increased user choice,
Improved user experience,
-Greater security,
Minimal standardization,
-Regulatory acceptance,
-Innovation,
Lower Costs,
-Transparency,
Automatability,
-Portability,
-Monetization,
and Rapid, widespread adoption.
</dd>
<dt>Motivation</dt>
<dd>
-
- </dd>
- <dt>Privacy / Security</dt>
- <dd>
-
- </dd>
- <dt>Exceptions</dt>
- <dd>
-
+Existing ubiquitous payment schemes must be supported with no changes to the
+operation of the payment scheme.
</dd>
</dl>
- </section>
- <section>
- <h5>Low Priority</h5>
<dl class="dl-horizontal">
- <dt></dt>
+ <dt>Emerging Schemes</dt>
<dd>
-
+CrowdFundCo supports Bitcoin, Ripple, Google Wallet, and PayPal.
</dd>
<dt>Goals</dt>
<dd>
Increased user choice,
Improved user experience,
-Greater security,
Minimal standardization,
-Regulatory acceptance,
-Innovation,
Lower Costs,
-Transparency,
Automatability,
-Portability,
-Monetization,
and Rapid, widespread adoption.
</dd>
<dt>Motivation</dt>
<dd>
-
- </dd>
- <dt>Privacy / Security</dt>
- <dd>
-
- </dd>
- <dt>Exceptions</dt>
- <dd>
-
+The same mechanism used to support existing payment schemes should also be
+able to support emerging schemes.
</dd>
</dl>
@@ -1202,114 +1064,126 @@
<section>
<h5>High Priority</h5>
<dl class="dl-horizontal">
- <dt></dt>
- <dd>
-
- </dd>
- <dt>Goals</dt>
+ <dt>Manual Selection</dt>
<dd>
-Increased user choice,
-Improved user experience,
-Greater security,
-Minimal standardization,
-Regulatory acceptance,
-Innovation,
-Lower Costs,
-Transparency,
-Automatability,
-Portability,
-Monetization,
-and Rapid, widespread adoption.
- </dd>
- <dt>Motivation</dt>
- <dd>
-
- </dd>
- <dt>Privacy / Security</dt>
- <dd>
-
- </dd>
- <dt>Exceptions</dt>
- <dd>
-
- </dd>
- </dl>
- </section>
-
- <section>
- <h5>Medium Priority</h5>
- <dl class="dl-horizontal">
- <dt></dt>
- <dd>
-
+ <ul>
+ <li>
+Marie has credit cards from three different institutions:
+one for work (from BankA), one personal card (from BankB), and one retail card
+from PayCo. She wants to choose the right one depending on the context of her
+purchase.
+ </li>
+ <li>
+Claire has multiple credit cards from the same bank as well as one debit card.
+ </li>
+ <li>
+Veronique wants to use a cryptocurrency in some cases (e.g.,
+peer-to-peer payments).
+ </li>
+ <li>
+Seth participates in a loyalty program with his local grocery store and
+can apply a variety of digital coupons when he visits the store.
+<span class="issue">Is a loyalty card a payment instrument, or a credential?
+</span>
+ </li>
+ <li>
+David wants to be able to manually order available payment instruments
+when they are presented to him.
+<span class="issue">Why? Isn't this just a part of the wallet UI?</span>
+ </li>
+ </ul>
</dd>
<dt>Goals</dt>
<dd>
Increased user choice,
Improved user experience,
-Greater security,
-Minimal standardization,
-Regulatory acceptance,
Innovation,
-Lower Costs,
Transparency,
-Automatability,
Portability,
-Monetization,
and Rapid, widespread adoption.
</dd>
<dt>Motivation</dt>
<dd>
-
- </dd>
- <dt>Privacy / Security</dt>
- <dd>
-
- </dd>
- <dt>Exceptions</dt>
- <dd>
-
+There are scenarios, such as the first interaction/use of a payment instrument,
+where selection of the payment instrument won't be able to be performed
+automatically.
</dd>
</dl>
- </section>
- <section>
- <h5>Low Priority</h5>
<dl class="dl-horizontal">
- <dt></dt>
+ <dt>Automatic Selection</dt>
<dd>
-
+ <ul>
+ <li>
+PayCo wants Elizabeth to know that if she pays with the debit card preferred
+by PayCo (because of a lower transaction fee for PayCo), she will get a
+discount.
+ </li>
+ <li>
+Whenever Mary shops at BigFreshGrocery she wants to use the same credit card,
+so payment should happen with that card automatically when she puts her
+phone near the checkout terminal or when purchasing groceries online.
+ </li>
+ <li>
+Lalana wants to see the instruments she most often uses earlier in the list
+of available instruments.
+ </li>
+ </ul>
+ </dd>
+ <dt>Goals</dt>
+ <dd>
+Increased user choice,
+Improved user experience,
+Innovation,
+Lower Costs,
+Transparency,
+Automatability,
+and Rapid, widespread adoption.
+ </dd>
+ <dt>Motivation</dt>
+ <dd>
+When a <tref title="payer">payer's</tref> personal preferences are known by
+their devices, it becomes possible to make selections for them automatically.
+ </dd>
+ </dl>
+
+ <dl class="dl-horizontal">
+ <dt>Sharing Instruments</dt>
+ <dd>
+ <ul>
+ <li>
+Lucio sends information about instruments he is willing to use to
+TrustedMerchant, who provides a discount for access to his information.
+ </li>
+ <li>
+Carla does not want to share information about the payment instruments she
+uses with any merchants, so that information is not shared with any online
+merchants.
+ </li>
+ </ul>
</dd>
<dt>Goals</dt>
<dd>
Increased user choice,
Improved user experience,
-Greater security,
-Minimal standardization,
-Regulatory acceptance,
-Innovation,
-Lower Costs,
-Transparency,
-Automatability,
-Portability,
-Monetization,
-and Rapid, widespread adoption.
+Innovation, and
+Monetization.
</dd>
<dt>Motivation</dt>
<dd>
-
+Sharing or protecting data on the sorts of payment instruments available to
+a <tref>payer</tref> should be a decision made by the <tref>payer</tref>.
</dd>
<dt>Privacy / Security</dt>
<dd>
-
- </dd>
- <dt>Exceptions</dt>
- <dd>
-
+The types of payment instruments available to a <tref>payer</tref> could be
+used to digitally fingerprint a <tref>payer</tref> even if they were using an
+pseudo-anonymous payment mechanism.
</dd>
</dl>
</section>
+
</section>
<section>