W3C home > Mailing lists > Public > public-webpayments@w3.org > July 2015

Rationalizing "Push" and "Pull" payments

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Mon, 27 Jul 2015 21:54:50 +0200
To: Web Payments CG <public-webpayments@w3.org>
Message-ID: <55B68C8A.7010505@gmail.com>
It is possible that this is obvious for everybody but it surely wasn't for me :)

Although not yet ready for the public my initial experiments verified that
it is fairly easy combining Push and Pull for all three entities (Wallet, Merchant, Bank):

https://github.com/cyberphone/web2native-bridge/blob/master/webpayment.bank/src/org/webpki/w2nb/webpayment/bank/PaymentCoreServlet.java

The only difference between the push and pull wallet responses is that the latter encrypts the push
response and sends it to the merchant instead of the bank.  The merchant must in turn send it to the
bank since the bank is the only party that can unlock the pull request.

The bank's authorization message is identical for both push and pull, the only difference is the way it is delivered .

It will probably take another month for the system to become fully presentable.

Writing a Wallet in Java/Swing was quite a challenge but it seems to run on most desktop OSes:
https://github.com/cyberphone/web2native-bridge/blob/master/webpayment.client/src/org/webpki/w2nb/webpayment/client/PaymentAgent.java

Anders
Received on Monday, 27 July 2015 19:55:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:07:41 UTC