We are implementing Marketplace payments with Boku. This is going to be the same flows as Bango, except at the payment point, we call Boku instead of Bango. That means that things like persona, pin and the like will not need changing. However data flows between Boku and the Marketplace, callbacks and verifification of the callbacks all need to happen and be secure. There is a deadline to get this in place by the end of April, so this is pretty high priority from the Marketplace point of view.

In Firefox OS, we currently have just a single provider in Gaia code: https://github.com/mozilla-b2g/gaia/blob/master/build/config/payment-prefs.js I don't suppose we know if Gaia UI actually support multiple payment providers? That's probably an input to this review (and how we do UX for users choosing which provider etc) This may already be supported, I'm just not sure. What about other platforms ?

(In reply to Paul Theriault [:pauljt] from comment #1) > In Firefox OS, we currently have just a single provider in Gaia code: > https://github.com/mozilla-b2g/gaia/blob/master/build/config/payment-prefs.js > > I don't suppose we know if Gaia UI actually support multiple payment > providers? That's probably an input to this review (and how we do UX for > users choosing which provider etc) This may already be supported, I'm just > not sure. > > What about other platforms ? We aren't changing the provider in Gaia. This is about implementing the provider in marketplace. All Gaia has to do is keep pointing at marketplace and the decision will be made there.

this review was completed. we created the data flow diagrams. for the most part this process is very similar to the bango process we already approved.

rforbes when you get a sec... can you link to the data flow diagrams referenced above? would be most useful!! merci beaucoup! caitlin

Caitlin: https://wiki.mozilla.org/Apps/ID_and_Payments