W3C home > Mailing lists > Public > public-payments-wg@w3.org > May 2016

Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)

From: Adrian Hope-Bailie <notifications@github.com>
Date: Wed, 18 May 2016 05:38:54 -0700
To: w3c/webpayments <webpayments@noreply.github.com>
Cc:
Message-ID: <w3c/webpayments/issues/130/220013343@github.com>
@tommythorsen can you submit a PR against the proposal that suggests how this might be done.

I like the idea of re-using the mechanism that is used in WebRTC to register an IdP service.
https://w3c.github.io/webrtc-pc/#sec.register-idp

Perhaps we need a `PaymentApp` interface that has a `ProcessPaymentRequestCallback` member that returns a `Promise<PaymentResponse`?

When the user calls `register()` to register the payment app they can pass in either a `start_url` or an implementation of `PaymentApp`.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/130#issuecomment-220013343
Received on Wednesday, 18 May 2016 12:39:26 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 18 May 2016 12:39:26 UTC