ISSUE-4: Routing a Payment Request to the appropriate Payment Agent

Multiple Payment Agents

Routing a Payment Request to the appropriate Payment Agent

State:
RAISED
Product:
Use Cases
Raised by:
Laurent Castillo
Opened on:
2015-02-19
Description:
From Laurent:

I definitely see use cases for multiple payment agents. A typical situation on a user’s phone would look like:

- My bank mobile banking app, acting as a payment agent containing my VISA card and my country’s local scheme card.
- My PayPal app, acting as payment agent for my PayPal account and my registered VISA card.
- My local Bitcoin wallet acting as payment agent for Bitcoin.

Relationships would work a bit like this:

User 1-n Payment Agents
Payment Agent 1-n Payment Schemes
Payment Scheme 1-n Payment Instruments
Payment Agent 1-n Payment Instruments

A scheme is a good abstraction to discover payment instruments and agents locally. In essence the user agent asks “Which payment agents do you have installed that support bitcoin and country’s local scheme cards?”, the answer would be “bitcoin app with bitcoin wallet foo, and my bank app with card bar”. The user agent would then know how to route the payment request to the correct agent (through an API, WebIntents, web2native proposal, …). Choice of the payment instrument can be done either at the merchant level OR left to the payment agent.
Related Actions Items:
No related actions
Related emails:
  1. [use cases] Agenda: Use Cases Task Force - Thursday, March 19th 2015 (from msporny@digitalbazaar.com on 2015-03-15)
  2. RE: [use cases] Agenda: Use Cases Task Force - Thursday, March 12th 2015 (from ryladog@gmail.com on 2015-03-11)
  3. [use cases] Agenda: Use Cases Task Force - Thursday, March 12th 2015 (from msporny@digitalbazaar.com on 2015-03-11)
  4. RE: [use cases] Agenda: Use Cases Task Force - Thursday, February 26th 2015 (from ryladog@gmail.com on 2015-02-26)
  5. Re: [use cases] Agenda: Use Cases Task Force - Thursday, February 26th 2015 (from ij@w3.org on 2015-02-23)
  6. [use cases] Agenda: Use Cases Task Force - Thursday, February 26th 2015 (from msporny@digitalbazaar.com on 2015-02-22)
  7. Re: FW: [use cases] Review of use case 3.3 "Choosing a Payment Instrument" (from msporny@digitalbazaar.com on 2015-02-19)

Related notes:

No additional notes.

Display change log ATOM feed


David Ezell <david_e3@verifone.com>, Dapeng Liu <max.ldp@alibaba-inc.com>, Kenneth Mealey <kenneth.mealey@aexp.com>, Chairs, Ian Jacobs <ij@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 4.html,v 1.1 2017/09/15 15:02:31 ted Exp $