- From: Adrian Hope-Bailie <adrian@hopebailie.com>
- Date: Wed, 15 Jul 2015 11:42:33 -0700
- To: Manu Sporny <msporny@digitalbazaar.com>
- Cc: Web Payments IG <public-webpayments-ig@w3.org>
- Message-ID: <CA+eFz_+8qT7CF-DaaqKfUGBWH2O6ByOZnmf6U--GPH+onr5iGA@mail.gmail.com>
I've attached 3 diagrams for 3 generic use cases (push payment validated by the payee, push payment where the payee uses their PSP to validate the payment, and a pull payment where the payee uses their PSP to process the payment). They are all quite similar to yours (and I've excluded the decision points for simplicity) but I think they provide a good high level view of how this flow can support a number of usage patterns. It's also worth noting that the push with validation by PSP could be tweaked for escrow: 1. Replace the PSP with an escrow service 2. Instead of the wallet pushing the payment to the payee they would perform some form of communication with the escorw service to either make the payment or get a payment reference to make the payment later (via cash or similar). 3. The completion response would not carry a proof of payment but rather a payment reference from the escrow service that the merchant can link to the order. If the escrow service supports a different flow you could tweak the pull payment flow: 1. Replace the PSP with an escrow service 2. Instead of the payee calling processPayment they would get a payment reference from the escrow service and then link this to the payer's order. 3. The escrow service reference would be sent to the payer wallet in the completion request so that the payer can pay the escrow service later to complete the transaction. On 15 July 2015 at 07:20, Manu Sporny <msporny@digitalbazaar.com> wrote: > On 07/15/2015 05:16 AM, Mountie Lee wrote: > > I were try to draw basic sequence diagram with diagram at Charter > > see http://bit.ly/1e0ewma > > > > but technically it is not exact. > > > > please comment for last part of diagram. > > I just glanced at the diagram, but that seems like the right flow to me, > Mountie. > > At least, that's what's in my head and is what my company has > implemented wrt. a standard Web Payment flow. It also matches the flow > that was done in the Web Payments CG. Nicely done. :) > > -- manu > > -- > Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) > Founder/CEO - Digital Bazaar, Inc. > blog: Web Payments: The Architect, the Sage, and the Moral Voice > https://manu.sporny.org/2015/payments-collaboration/ > >
Attachments
- image/png attachment: Web_Payment_Sequence_Diagram__Pull_Payment_via_PSP_.png
- image/png attachment: Web_Payment_Sequence_Diagram__Push_Payment_with_validation_by_payee_.png
- image/png attachment: Web_Payment_Sequence_Diagram__Push_Payment_with_validation_by_PSP_.png
Received on Wednesday, 15 July 2015 18:43:07 UTC