Payments/Working: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "This is proposed home page of the proposed payments working group. The goal is to make payments better for the web. This is a seperate project from the Marketplace, although t...")
 
(delete me)
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{delete|Not in use, no content, obsolete|date=07/08/2020}}
This is proposed home page of the proposed payments working group. The goal is to make payments better for the web. This is a seperate project from the Marketplace, although the Marketplace payments team might become consumers of the outcomes of this group.
This is proposed home page of the proposed payments working group. The goal is to make payments better for the web. This is a seperate project from the Marketplace, although the Marketplace payments team might become consumers of the outcomes of this group.


= Goals =
= Goals =
Make payments more secure, easier for developers and users. More random notes: http://www.agmweb.ca/2013-11-04-payments-we-deserve/
Make payments more secure, easier for developers and users.  
 
== Existing APIs ==
 
* [https://wiki.mozilla.org/WebAPI/WebPayment mozPay] the existing platform API for initiating a payment.
 
* [https://wiki.mozilla.org/WebAPI/WebPaymentProvider#Silent_SMS SilentSMS] a way to authenticate a device using silent SMS.
 
== APIs under Discussion ==
 
* [http://www.html5rocks.com/en/tutorials/forms/requestautocomplete/ Request Autocomplete]: Allow completion of payment information in one client eg: Desktop, then have it sync over to other devices like Android and Firefox OS. So that you don't have to type in all the information on mobile.
** [https://bugzilla.mozilla.org/show_bug.cgi?id=939351 Bug 939351] and [https://bugzilla.mozilla.org/show_bug.cgi?id=946022 Android bug 946022] and [https://bugzilla.mozilla.org/show_bug.cgi?id=964295 Firefox OS bug 964295].
** There is an [https://www.dropbox.com/s/2t56r0xpfs4m2k7/%28feb-3%29%20form%20auto-fill.pdf example mockup for Android].


== Ideas ==
== Ideas ==
Line 13: Line 26:


Is trusted UI a valued approach? Could we do something more with this UI and expand this to more systems. Currently its only usable by persona and marketplace payments.
Is trusted UI a valued approach? Could we do something more with this UI and expand this to more systems. Currently its only usable by persona and marketplace payments.
*[https://groups.google.com/forum/#!topic/mozilla.dev.b2g/aH4rDn3qEiQ Redesigning the Trusted UI proposal]
*[https://groups.google.com/d/msg/mozilla.dev.b2g/t4Fd5r7MD3w/2ZjqUYSfM4UJ Redesigning the Trusted UI discussion]


=== Device API ===
=== Device API ===


There are discreet and useful APIs that we can create after our experience with the Marketplace. See: https://wiki.mozilla.org/WebAPI/Direct_Billing for a proposal.
There are discreet and useful APIs that we can create after our experience with the Marketplace. See: https://wiki.mozilla.org/WebAPI/Direct_Billing for a proposal.
=== Data ===
Entering all the data is repetitive. Can we store user data in a secure way. See: http://www.chromium.org/developers/using-requestautocomplete


=== Privacy ===
=== Privacy ===
Line 36: Line 48:
== Mailing list ==
== Mailing list ==


TODO
Mailing list: https://mail.mozilla.org/listinfo/wg-payments
 
The mailing list is '''open to the public'''.


== Weekly meetings ==
== Weekly meetings ==


TODO
TODO

Latest revision as of 17:36, 8 July 2020

Do not edit this page THIS PAGE IS PROPOSED FOR DELETION 07/08/2020
Not in use, no content, obsolete

This is proposed home page of the proposed payments working group. The goal is to make payments better for the web. This is a seperate project from the Marketplace, although the Marketplace payments team might become consumers of the outcomes of this group.

Goals

Make payments more secure, easier for developers and users.

Existing APIs

  • mozPay the existing platform API for initiating a payment.
  • SilentSMS a way to authenticate a device using silent SMS.

APIs under Discussion

Ideas

Payment chooser

Users and developers should not be locked down into just one payment choice. A payment chooser would allow users to chose alternative payment systems when starting off the payment flow.

Trusted UI

Is trusted UI a valued approach? Could we do something more with this UI and expand this to more systems. Currently its only usable by persona and marketplace payments.

Device API

There are discreet and useful APIs that we can create after our experience with the Marketplace. See: https://wiki.mozilla.org/WebAPI/Direct_Billing for a proposal.

Privacy

Could the client act as a broker to prevent the passing of personal information?

Transparency

Can there be an improvement in the transparency of where your personal information is going, how the payment is going to be split up and what happens afterwards in terms of refunds?

Alternatives

Supporting alternative payment systems.

Mailing list

Mailing list: https://mail.mozilla.org/listinfo/wg-payments

The mailing list is open to the public.

Weekly meetings

TODO