Browser with remote Payment Apps
Adrian Hope-Bailie edited this page Nov 17, 2015
·
1 revision
Pages 55
- Home
- A Payments Initiation Architecture for the Web
- Agenda 12th November 2015 at 1700 UTC
- Agenda 17th December 2015 at 1700 UTC
- Agenda 19th November 2015 at 1700 UTC
- Agenda 20160107
- Agenda 20160121
- Agenda 20160128
- Agenda 20160204
- Agenda 20160211
- Agenda 20160310
- Agenda 20160317
- Agenda 20160331
- Agenda 20160407
- Agenda 20160414
- Agenda 20160421
- Agenda 20160428
- Agenda 20160505
- Agenda 20160512
- Agenda 20160519
- Agenda 20160526
- Agenda 20160602
- Agenda 20160609
- Agenda 20160616
- Agenda 20160623
- Agenda 3rd December 2015 at 1700 UTC
- Agenda for 3rd March telco
- All in the Browser
- Browser with remote Payment Apps
- Call for Consensus FPWD
- CFC_20140412
- Checkout API
- Components
- DeploymentExamples
- Extensibility_Notes
- F2F Agenda
- How it Works
- How the Working Group works
- Issue Summary
- MagWebinar
- Meetings
- Mobile Platform
- PaymentApp_Notes
- PaymentRequestFAQ
- PMI_Notes
- RegistrationTypes
- Spec_Notes
- Support for multi price and currency
- Synchronizing Github Issues with W3C Mailing Lists
- TPAC 2015 issues list
- Web Payment Deployment Examples
- Web Payments Working Group FTF Meeting (July 2016)
- Web Payments Working Group Plan
- WPWG FTF Feb 2016
- WPWG FTF Feb 2016 Requirements
- Show 40 more pages…
A Payments Initiation Architecture for the Web
Clone this wiki locally
In the this deployment example the majority of components have been deployed in the browser however the browser vendor supports remote Payment Apps hosted by the payer's PSPs.
When the mediator has established which app to forward the paymentRequest to it will do so via an HTTP POST to the endpoint defined in the Payment App's manifest.
The response will be rendered in an iFrame or separate (modal?) dialogue.
