Status: This draft document is for discussion as part of the development use case by the Web Payments Interest Group.
Please contact Ian Jacobs <ij@w3.org> or send feedback to the Interest Group at public-webpayments-comments@w3.org.
This is a view of the Web Payments IG Use Cases, organized by Payment Phases.
Electronic commerce is thriving and continues to expand. However, fragmentation of payment systems is limiting the potential, as are problems such as fraud and usability. Since the Web is ubiquitous, strengthening support for payments has the potential to create new opportunities for businesses and customers. Although we are seeing innovation in payment services, the lack of Web standards makes it more difficult to adapt to new payment approaches or integrate new payment providers. Fragmented regulatory environments further complicate the payments landscape.
The purpose of this document is to employ use cases to frame what a realistic
vision looks like for payments on the Web Platform. The end result is not
meant to replace existing payment systems, but augment and simplify the
interface to each system via the Web. The purpose of this
initiative is to enable as many of the current
In order to categorize the use cases in this document into a manner that is easy to comprehend, they are separated into four primary phases. The phases are:
This particular model focus on he interactions between a person (or organization) and a merchant. This particular model does not intend to address the exchanges between bank, card associations, or other back-end parties in a Payment.
Each phase consists of a series of steps.
The details of each step vary by
It is also important to note that these phases and steps may be be interrupted at various times (e.g., one party drops out, or exceptions occur like insufficient funds, refunds, or a regulatory block). While these phases are an approximation of the general flow of all payments, they are helpful in structuring the use cases such that it is easy to figure out to which part of the payment process a particular use case belongs.
These phases can be applied to a variety of different payment scenarios such as person-to-person, person-to-business, business-to-person, government-to-person, and so forth.
The first phase of the payment process is where the payer and the payee negotiate the terms of the payment.
The second phase of the payment process is used to determine which payment instruments the payer will use to transfer funds to the payee.
The third phase of the payment process is used to initiate the transfer of funds. Depending on the payment instrument, the transfer of funds may be verified immediately or may take several days to be verified.
The fouth phase of the payment process is used to complete the transaction by providing the payer with a receipt and/or the product that was purchased.
This document attempts to communicate the concepts outlined in the Web Payments space by using specific terms to discuss particular concepts. This terminology is included below and linked to throughout the document to aid the reader:
The use cases below rely on a number of assumptions that are not detailed in the use cases but that will be explored in more detail in the architecture and requirements documents.
Note: Initiation of processing is Payment scheme dependent.
The above use cases cover a wide range of scenarios for each step in a payment flow. The scenarios are (by design) very different. In this section we provide some narratives that illustrate some payment scenarios from beginning to end. This is meant to illustrate the phases of a payment through uniform stories.
Please note that these narratives do not define the scope of this group's work; that is determined by the group's charter and the use cases earlier in this document. We provide several narratives below (the first is intentionally more detailed) to help make clear that these are only subsets of the use cases.
Jill seeks a new outfit for a party. She selects items from PayToParty, which is a brick-and-mortar store with an online presence as well. She chooses how to pay, and the items are delivered the next day to her home. The steps are described now in more detail.
Discovery of Offer: Jill begins her purchase at home on her laptop, where she browses the items on the PayToParty Web site. On the way to work the next morning she explores the catalog further from a native app on her smart phone. Jill can't decide whether the dress displayed online is blue with black stripes or white with gold stripes, so during her lunch break, she drops into the PayToParty store near her office. When she enters the store, PayToParty lets her know with a message that causes her phone to buzz that there's a special offer (next day delivery) if she pays with the debit card preferred by PayToParty.
Agreement on Terms: That same evening at home, Jill logs into her account on the PayToParty Web site, adding her preferred items to her shopping cart. Before checking out, Jill succombs to temptation and subscribes to the site's monthly tea selection. She will pay automatically each month —she calls this her Tea-Bill— and PayToParty will deliver tea to her home. Because of her tea subscription, PayToParty removes 5% from the price of her clothing items.
Application of Marketing Elements: As Jill prepares to check out, PayToParty offers her a discount of 10% if she uses the debit card preferred by PayToParty.
Discovery of Accepted Schemes: Given where Jill lives, PayToParty offers her payment by credit card, debit card, and PayPal, but not Jill's favorite cryptocurrency (which she uses on other sites).
Selection of Payment Instruments: Jill pushes the "pay now" button and is presented with a number of options to pay, including a credit card, a debit card (which is highlighted to remind her of the special delivery offer), and a PayPal account. Jill's credit card is issued by BankLove and her debit card is from BankNow, the preferred bank of PaytoParty. There is also a gift card from PayToParty that she received for her birthday, but she chooses not to use it for this purchase.
Authentication to Access Instruments: Jill selects the debit card from BankNow to pay and is prompted to enter a secret that the bank sends to her mobile phone. Jill notes that the bank's authentication method has improved in the past year, improving her online experience without requiring any action from her.
To be continued...
Please send feedback to the Web Payments Interest Group at public-webpayments-comments@w3.org.