Wednesday, 30 December 2015
Tuesday, 29 December 2015
- Re: [webpayments] Should the payment request contain line item details? (#38)
- Re: [webpayments] Expression of monetary amounts (#40)
Thursday, 24 December 2015
Wednesday, 23 December 2015
- Re: [webpayments] Expression of monetary amounts (#40)
- Re: [webpayments] SDD one off e-mandate (#43)
- Re: [webpayments] Refined SEPA Credit Transfer to add the web interactions (#33)
- Re: [webpayments] Should the payment request contain line item details? (#38)
- Re: [paymentrequest] Should the Payment Request API only be available in a top-level browsing context? (#30)
- Re: [webpayments] Refined SEPA Credit Transfer to add the web interactions (#33)
Tuesday, 22 December 2015
- Re: [webpayments] How are third-party native wallets integrated? (#42)
- Re: [webpayments] How are third-party native wallets integrated? (#42)
Monday, 21 December 2015
- [Feb 2016 FTF meeting] Nearby hotels
- Re: [webpayments] How are third-party native wallets integrated? (#42)
- Re: [webpayments] How are third-party native wallets integrated? (#42)
- Re: [webpayments] How are third-party native wallets integrated? (#42)
- Re: [webpayments] How are third-party native wallets integrated? (#42)
- Re: [webpayments] How are third-party native wallets integrated? (#42)
- [webpayments] SDD one off e-mandate (#43)
- [paymentrequest] Use navigator.payments rather than creating a new object instance (#42)
Sunday, 20 December 2015
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39)
- Re: [webpayments] Should a payment request be just data, or a programmable object? (#36)
Saturday, 19 December 2015
- [webpayments] How are third-party native wallets integrated? (#42)
- Re: [webpayments] Expression of monetary amounts (#40)
- Re: [webpayments] Expression of monetary amounts (#40)
Friday, 18 December 2015
- Re: [webpayments] Expression of monetary amounts (#40)
- Re: [webpayments] Should we expose status change events in the browser API? (#41)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- Re: [admin]
Thursday, 17 December 2015
- Re: [admin]
- [admin]
- Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28)
- Re: [paymentrequest] CurrencyAmount description has exponent sign wrong (#39)
- Re: [webpayments] Is tracking payment request state necessary? (#35)
- Re: [webpayments] Is there an HTTP API based message flow? (#17)
- Re: [webpayments] Expression of monetary amounts (#40)
- Re: [webpayments] What is the use case for the Payment Details object? (#38)
- Re: [webpayments] Should list of accepted payment methods be strings or objects? (#37)
- wpwg-ACTION-10: Integrate standard flow into web payments cg's browser api spec.
- Re: [webpayments] Should we expose status change events in the browser API? (#41)
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39)
- RE: Agenda for tomorrow's call
- Re: [webpayments] Should list of accepted payment methods be strings or objects? (#37)
- Re: [webpayments] Should we expose status change events in the browser API? (#41)
- Re: [webpayments] Should we expose status change events in the browser API? (#41)
- Re: [webpayments] Should we expose status change events in the browser API? (#41)
- Re: [webpayments] What is the use case for the Payment Details object? (#38)
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39)
- Re: [webpayments] Should we expose status change events in the browser API? (#41)
- Re: [webpayments] What is the use case for the Payment Details object? (#38)
- Re: [webpayments] Should we expose status change events in the browser API? (#41)
- [paymentrequest] Combine API parameters into a single request object + options (#41)
- Re: [webpayments] Expression of monetary amounts (#40)
- Re: [webpayments] What is the use case for the Payment Details object? (#38)
- Re: [paymentrequest] CurrencyAmount description has exponent sign wrong (#39)
- Re: [webpayments] What is the use case for the Payment Details object? (#38)
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39)
- Re: [paymentrequest] CurrencyAmount description has exponent sign wrong (#39)
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39)
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39)
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39)
- Re: [webpayments] What is the use case for the Payment Details object? (#38)
Wednesday, 16 December 2015
- Agenda for tomorrow's call
- [paymentrequest] No mention of non-decimal currencies (#40)
- [paymentrequest] CurrencyAmount description has exponent sign wrong (#39)
- Re: [webpayments] What is the use case for the Payment Details object? (#38)
- Re: [webpayments] Expression of monetary amounts (#40)
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39)
- Re: [webpayments] What is the use case for the Payment Details object? (#38)
- Re: [webpayments] What is the use case for the Payment Details object? (#38)
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39)
- Re: [webpayments] Should we expose status change events in the browser API? (#41)
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39)
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39)
- Re: [webpayments] Expression of monetary amounts (#40)
- Re: [webpayments] Expression of monetary amounts (#40)
- Re: [webpayments] Expression of monetary amounts (#40)
- Re: [webpayments] Should we expose status change events in the browser API? (#41)
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39)
- Re: [webpayments] Should a payment request be just data, or a programmable object? (#36)
- Re: [webpayments] Should we expose status change events in the browser API? (#41)
- [webpayments] Should we expose status change events in the browser API? (#41)
- Re: [webpayments] Expression of monetary amounts (#40)
- [webpayments] Expression of monetary amounts (#40)
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39)
- [webpayments] Should a Payment Request API have shipping address APIs? (#39)
- Re: [webpayments] What is the use case for the Payment Details object? (#38)
- [webpayments] What is the use case for the Payment Details object? (#38)
- Re: [webpayments] Should list of accepted payment methods be strings or objects? (#37)
- [webpayments] Should list of accepted payment methods be strings or objects? (#37)
- Re: [webpayments] Should a payment request be just data, or a programmable object? (#36)
- [webpayments] Should a payment request be just data, or a programmable object? (#36)
- [webpayments] Is tracking payment request state necessary? (#35)
- Re: [webpayments] Is there an HTTP API based message flow? (#17)
- Re: [webpayments] Confining the definition of user agents to browsers (#34)
- Re: [webpayments] Confining the definition of user agents to browsers (#34)
- Re: [webpayments] Confining the definition of user agents to browsers (#34)
- [webpayments] Confining the definition of user agents to browsers (#34)
Tuesday, 15 December 2015
- Re: [paymentrequest] Update API document with missing details (#38)
- [paymentrequest] Update API document with missing details (#38)
Monday, 14 December 2015
Friday, 11 December 2015
- Re: [paymentrequest] Price breakdown (#25)
- Re: [paymentrequest] Second set of API refactoring changes (#37)
- Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28)
- Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28)
- Re: [paymentrequest] Should the Payment Request API only be available in a top-level browsing context? (#30)
- Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28)
- Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28)
- Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28)
- Re: [webpayments] How are payment messages trusted? (#19)
- [webpayments] Refined SEPA Credit Transfer to add the web interactions (#33)
- Re: [webpayments] Refined SEPA Credit Transfer to add the web interactions (#33)
- Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28)
- Re: [webpayments] How are cloud-based payment instruments supported? (#16)
- Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28)
- Re: [webpayments] Abstract payment architecture (#11)
- Re: [webpayments] Added PSP Hosted Card Payment (#32)
- Re: [paymentrequest] Should the Payment Request API only be available in a top-level browsing context? (#30)
- Re: [webpayments] How are payment messages trusted? (#19)
- [webpayments] Added PSP Hosted Card Payment (#32)
- Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28)
- wpwg-ACTION-9: Share iso20022 glossary/terminology
- Re: [Architecture] Updated wiki to address some comments
- Re: [paymentrequest] Should the Payment Request API only be available in a top-level browsing context? (#30)
- Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28)
- Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28)
- Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28)
- Re: [Architecture] Updated wiki to address some comments
Thursday, 10 December 2015
- [paymentrequest] Second set of API refactoring changes (#37)
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35)
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35)
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35)
- Re: [paymentrequest] What is the format for payment method identifiers for distributed extensibility (#34)
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35)
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35)
- Re: [paymentrequest] What is the format for payment method identifiers for distributed extensibility (#34)
- Re: [webpayments] How are payment instruments registered? (#14)
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35)
- Re: [webpayments] How are payment instruments registered? (#14)
- Re: [paymentrequest] What is the format for payment method identifiers for distributed extensibility (#34)
- Re: [webpayments] How are payment instruments registered? (#14)
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35)
- Re: [webpayments] Abstract payment architecture (#11)
- Re: [webpayments] Abstract payment architecture (#11)
- Re: [webpayments] Abstract payment architecture (#11)
- Re: [webpayments] How are payment instruments registered? (#14)
- Re: [webpayments] How are payment instruments registered? (#14)
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35)
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- Re: [webpayments] Should we be concerned about the use of the Browser API in a non-HTTPS environment? (#20)
Wednesday, 9 December 2015
- Re: [paymentrequest] Updated documents to ensure all issues notes link to issue in the repo. (#36)
- [paymentrequest] Updated documents to ensure all issues notes link to issue in the repo. (#36)
- [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35)
- [paymentrequest] What is the format for payment method identifiers for distributed extensibility (#34)
- Re: [paymentrequest] Should the Payment Request API only be available in a top-level browsing context? (#30)
- [paymentrequest] Should we support a delegated state for PaymentRequest? (#33)
- Re: [paymentrequest] Should the Payment Request API only be available in a top-level browsing context? (#30)
- Re: [paymentrequest] Standardizing Common Payment Instruments (#20)
- Re: [paymentrequest] UI for Payment Instrument (#17)
- Re: [paymentrequest] UI for Payment Instrument (#17)
- [paymentrequest] Should the web page be able to provide status information before calling complete() (#32)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28)
- Re: [paymentrequest] Let merchant pass in arbitrary data to payment request? (#11)
- Re: [paymentrequest] Let merchant pass in arbitrary data to payment request? (#11)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- Re: [paymentrequest] Reconsider the need to include shipping in this spec (#8)
- Re: [paymentrequest] Reconsider the need to include shipping in this spec (#8)
- [paymentrequest] Write-up initial proposal for card payment method spec (#31)
- Re: [paymentrequest] Should the Payment Request API only be available in a top-level browsing context? (#30)
- Re: [paymentrequest] Chain of trust between browser and merchant (#9)
- Re: [paymentrequest] Chain of trust between browser and merchant (#9)
- [paymentrequest] Should the Payment Request API only be available in a top-level browsing context? (#30)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- Re: [paymentrequest] Should the Payment Request API only be available in a secure context? (#29)
- [paymentrequest] Should the Payment Request API only be available in a secure context? (#29)
- Re: [paymentrequest] Price breakdown (#25)
- Re: [webpayments] Abstract payment architecture (#11)
- [paymentrequest] Write-up proposal for shipping address fields (#28)
- Re: [paymentrequest] Payment methods registering to handle schemes / Interledger support (in the future) (#14)
- Re: [paymentrequest] Payment methods registering to handle schemes / Interledger support (in the future) (#14)
- [paymentrequest] Write-up initial proposal for payment app registration spec (#27)
- Re: [paymentrequest] Could we design appropriate declarative models to go along with the API? (#13)
- Re: [paymentrequest] Could we design appropriate declarative models to go along with the API? (#13)
- Re: [paymentrequest] How do we think it will work with ServiceWorker? (#12)
- Re: [paymentrequest] How do we think it will work with ServiceWorker? (#12)
- Re: [paymentrequest] Can we call out how this relates to other payment efforts? (#6)
- Re: [webpayments] How are payment instruments registered? (#14)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- Re: [webpayments] How are payment messages trusted? (#19)
- Re: [webpayments] Abstract payment architecture (#11)
- Re: [webpayments] Should we be concerned about the use of the Browser API in a non-HTTPS environment? (#20)
- Re: [webpayments] How are payment instruments registered? (#14)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- Re: [paymentrequest] Payment instrument installation is platform-dependent (#5)
- Re: [webpayments] Abstract payment architecture (#11)
- Re: [webpayments] Abstract payment architecture (#11)
- Re: [paymentrequest] API needs equivalent of PassKit's paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23)
- Re: [paymentrequest] First set of API refactoring changes. (#26)
- Re: [paymentrequest] Currency Specification (#18)
- Re: [paymentrequest] There should be a way for the merchant to indicate the instrumentResponse was a failure (#15)
- Scheduled: February 2016 Web Payments Working Group FTF
- [paymentrequest] First set of API refactoring changes. (#26)
- Re: [webpayments] Abstract payment architecture (#11)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- Re: [webpayments] Abstract payment architecture (#11)
- Re: [webpayments] Abstract payment architecture (#11)
- Re: [webpayments] How are payment instruments registered? (#14)
- Re: [webpayments] How are cloud-based payment instruments supported? (#16)
- Re: [webpayments] How do organizations layer additional information in the core messages? (#18)
- Re: [webpayments] Is there an HTTP API based message flow? (#17)
- Re: [webpayments] How are payment messages trusted? (#19)
- Re: [webpayments] Should we be concerned about the use of the Browser API in a non-HTTPS environment? (#20)
- Re: [webpayments] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#29)
- Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25)
- Re: [webpayments] Minimum necessary information for merchant to process payment (#27)
- Re: [paymentrequest] Payment instrument installation is platform-dependent (#5)
- Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28)
- [Architecture] Updated wiki to address some comments
- Re: [webpayments] Machine readability of payment methods? (#30)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
Tuesday, 8 December 2015
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)
- [paymentrequest] Price breakdown (#25)
- Re: [paymentrequest] Overridng Common Payment Instruments (#21)
- Re: [paymentrequest] Overridng Common Payment Instruments (#21)
- Re: [paymentrequest] Overridng Common Payment Instruments (#21)
- Re: [paymentrequest] Overridng Common Payment Instruments (#21)
- Re: [paymentrequest] Payment instruments not supported by proposal (#10)
- Re: [paymentrequest] Payment instruments not supported by proposal (#10)
- Re: [paymentrequest] Standardizing Common Payment Instruments (#20)
- Re: [paymentrequest] Payment methods registering to handle schemes / Interledger support (in the future) (#14)
- Re: [paymentrequest] Payment instruments not supported by proposal (#10)
- Re: [paymentrequest] Can we call out how this relates to other payment efforts? (#6)
- Re: [paymentrequest] Do we need to support transactions that aren't finalised by the merchant in v1? (#3)
- Re: [paymentrequest] Do we need to support transactions that aren't finalised by the merchant in v1? (#3)
Monday, 7 December 2015
- Re: [webpayments] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#29)
- Re: [webpayments] Payment Request Architecture glossary should include IG glossary (#23)
- Re: [webpayments] Merge Payment Request Architecture with Capabilities Document (#22)
- Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25)
- Re: [webpayments] Minimum necessary information for merchant to process payment (#27)
- Re: [webpayments] How do organizations layer additional information in the core messages? (#18)
- Re: [webpayments] Machine readability of payment methods? (#30)
- Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25)
- Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25)
- Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25)
- Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25)
- Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25)
- Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25)
- Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25)
- Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25)
- Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25)
- Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25)
- Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25)
- Re: [webpayments] Should Payment Method Identifiers be a Linked Data Vocabulary? (#29)
- Re: Linking the Wiki to the example Flows
- Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25)
- Re: Experimental glossary definitions added
- Re: [webpayments] Payment Request Architecture glossary should include IG glossary (#23)
- [WPAY WG] Additional ANSI standards for Authentication(X9.122) added to WatchDox
- RE: Experimental glossary definitions added
- Re: [webpayments] Merge Payment Request Architecture with Capabilities Document (#22)
- Re: [webpayments] How are payment instruments shared between different browser brands? (#15)
- Re: [webpayments] Machine readability of payment methods? (#30)
- Re: Linking the Wiki to the example Flows
Sunday, 6 December 2015
- Re: [webpayments] Should Payment Method Identifiers be a Linked Data Vocabulary? (#29)
- Re: [webpayments] Should Payment Method Identifiers be a Linked Data Vocabulary? (#29)
- Re: [webpayments] Machine readability of payment methods? (#30)
- Re: [webpayments] Machine readability of payment methods? (#30)
- Re: [webpayments] Machine readability of payment methods? (#30)
- [webpayments] Machine readability of payment methods? (#30)
- [webpayments] Should Payment Method Identifiers be a Linked Data Vocabulary? (#29)
- Re: [webpayments] How do organizations layer additional information in the core messages? (#18)
- Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28)
- Re: [webpayments] How do organizations layer additional information in the core messages? (#18)
- [webpayments] What gets registered - apps, wallets, or payment instruments? (#28)
- Re: [webpayments] Minimum necessary information for merchant to process payment (#27)
- [webpayments] Minimum necessary information for merchant to process payment (#27)
- [webpayments] Splitting registration from payment (#26)
- [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25)
- [webpayments] Document relationship diagrams? (#24)
- Re: [webpayments] Payment Request Architecture glossary should include IG glossary (#23)
- Re: [webpayments] Payment Request Architecture glossary should include IG glossary (#23)
- [webpayments] Payment Request Architecture glossary should include IG glossary (#23)
- [webpayments] Merge Payment Request Architecture with Capabilities Document (#22)
- New landing page for Google/Microsoft paymentRequest() API
- Re: [paymentrequest] Update explainer.md (#7)
- Re: [paymentrequest] Update explainer.md (#7)
- Re: [paymentrequest] Added initial spec drafts and architecture overview. (#24)
- Re: [paymentrequest] Added initial spec drafts and architecture overview. (#24)
- Experimental glossary definitions added
- Re: [paymentrequest] Added initial spec drafts and architecture overview. (#24)
- Re: [paymentrequest] Added initial spec drafts and architecture overview. (#24)
- Re: [paymentrequest] Added initial spec drafts and architecture overview. (#24)
- Re: [webpayments] No proprietary binary files, please (#7)
- Re: [webpayments] No proprietary binary files, please (#7)
- Re: [webpayments] No proprietary binary files, please (#7)
Saturday, 5 December 2015
Friday, 4 December 2015
- RE: Linking the Wiki to the example Flows
- Re: [webpayments] How are payment instruments shared between different browser brands? (#15)
- Re: [webpayments] How are payment instruments shared between different browser brands? (#15)
- Re: Linking the Wiki to the example Flows
- Re: [webpayments] Uploaded Credit Transfer files for Cyril (#21)
- [webpayments] Uploaded Credit Transfer files for Cyril (#21)
- Re: Linking the Wiki to the example Flows
- Re: [webpayments] How are payment messages trusted? (#19)
- Re: [webpayments] How are payment instruments shared between different browser brands? (#15)
- Re: [webpayments] How are cloud-based payment instruments supported? (#16)
- Re: Linking the Wiki to the example Flows
- Re: Linking the Wiki to the example Flows
Thursday, 3 December 2015
- Re: Linking the Wiki to the example Flows
- Re: Linking the Wiki to the example Flows
- Re: Linking the Wiki to the example Flows
- Re: Linking the Wiki to the example Flows
- Linking the Wiki to the example Flows
- [Minutes] 3 Dec 2015 WPWG meeting
- Re: [webpayments] How are payment instruments shared between different browser brands? (#15)
- Re: [paymentrequest] Clarity on Currency Conversion (#19)
- Re: [paymentrequest] Clarity on Currency Conversion (#19)
- Re: [paymentrequest] Clarity on Currency Conversion (#19)
- Re: [webpayments] How are cloud-based payment instruments supported? (#16)
- Re: [webpayments] How are cloud-based payment instruments supported? (#16)
- Re: [webpayments] How are payment instruments shared between different browser brands? (#15)
- Re: [webpayments] How are payment instruments registered? (#14)
- Re: [webpayments] How are payment messages trusted? (#19)
- Re: [webpayments] How are cloud-based payment instruments supported? (#16)
- Re: [webpayments] Is there an HTTP API based message flow? (#17)
- Re: [webpayments] How are payment instruments shared between different browser brands? (#15)
- Re: [webpayments] How are payment instruments registered? (#14)
- Re: [webpayments] Should we be concerned about the use of the Browser API in a non-HTTPS environment? (#20)
- Re: [webpayments] How are payment messages trusted? (#19)
- Re: [webpayments] How are payment messages trusted? (#19)
- Re: [webpayments] How are cloud-based payment instruments supported? (#16)
- Re: [webpayments] How are cloud-based payment instruments supported? (#16)
- Re: [webpayments] How are cloud-based payment instruments supported? (#16)
Wednesday, 2 December 2015
- Re: [webpayments] How are payment messages trusted? (#19)
- Re: [webpayments] How are payment instruments registered? (#14)
- Re: [webpayments] How are cloud-based payment instruments supported? (#16)
- Re: New wiki article: TPAC 2015 issues list (was RE: wpwg-ACTION-8: Move google docs list of issues to github wiki)
- Re: New wiki article: TPAC 2015 issues list (was RE: wpwg-ACTION-8: Move google docs list of issues to github wiki)
- Meeting 3rd December at 17:00 UTC
- Re: [webpayments] How are payment messages trusted? (#19)
- Re: [webpayments] Should we be concerned about the use of the Browser API in a non-HTTPS environment? (#20)
- Re: [webpayments] Should we be concerned about the use of the Browser API in a non-HTTPS environment? (#20)
- Re: [paymentrequest] API needs equivalent of PassKit's paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23)
- Re: [webpayments] How are cloud-based payment instruments supported? (#16)
- Re: [webpayments] How are payment messages trusted? (#19)
- Re: [webpayments] How are payment instruments registered? (#14)
- Re: [webpayments] Is there an HTTP API based message flow? (#17)
- Re: [webpayments] How are cloud-based payment instruments supported? (#16)
- Re: [webpayments] How are payment instruments shared between different browser brands? (#15)
- Re: [webpayments] Should we be concerned about the use of the Browser API in a non-HTTPS environment? (#20)
- [webpayments] Should we be concerned about the use of the Browser API in a non-HTTPS environment? (#20)
- Re: [webpayments] How are payment messages trusted? (#19)
- [webpayments] How are payment messages trusted? (#19)
- Re: [webpayments] How do organizations layer additional information in the core messages? (#18)
- [webpayments] How do organizations layer additional information in the core messages? (#18)
- Re: [webpayments] Is there an HTTP API based message flow? (#17)
- [webpayments] Is there an HTTP API based message flow? (#17)
- Re: [webpayments] How are cloud-based payment instruments supported? (#16)
- [webpayments] How are cloud-based payment instruments supported? (#16)
- Re: [webpayments] How are payment instruments shared between different browser brands? (#15)
- [webpayments] How are payment instruments shared between different browser brands? (#15)
- Re: [webpayments] How are payment instruments registered? (#14)
- [webpayments] How are payment instruments registered? (#14)
- Re: [paymentrequest] API needs equivalent of PassKit's paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23)
- Re: [paymentrequest] API needs equivalent of PassKit's paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23)
- Re: [paymentrequest] API needs equivalent of PassKit's paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23)
- Re: [paymentrequest] API needs equivalent of PassKit's paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23)
- Re: [paymentrequest] API needs equivalent of PassKit's paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23)
Tuesday, 1 December 2015
- Re: [paymentrequest] API needs equivalent of PassKit's paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23)
- Re: [paymentrequest] Location of Authorisation in the flow (#22)
- Re: [paymentrequest] API needs equivalent of the paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23)
- [paymentrequest] API needs equivalent of the paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23)
- Re: [paymentrequest] Payment instruments not supported by proposal (#10)
- Re: New wiki article: TPAC 2015 issues list (was RE: wpwg-ACTION-8: Move google docs list of issues to github wiki)
- Re: New wiki article: TPAC 2015 issues list (was RE: wpwg-ACTION-8: Move google docs list of issues to github wiki)