Closed Bug 794530 (basecamp-payments) Opened 11 years ago Closed 10 years ago
[meta] Implement new client side payment provider flow
Our move to a new payment provider requires refactoring of client and server flows. This bug tracks those changes.
See https://mana.mozilla.org/wiki/display/MARKET/Marketplace+Home for data flows and supporting info.
making bug 775802 a dep (not a blocker) because that covers everything that the Marketplace needs to do to make payments work. There are other Gaia and identity pieces which will go on this tracker.
Better resource: https://wiki.mozilla.org/Apps/ID_and_Payments
Lucas, we will be following this too. We haven't permissions to access https://mana.mozilla.org/wiki/display/MARKET/Marketplace+Home, but everything will be at https://wiki.mozilla.org/Apps/ID_and_Payments, right? Otherwise, we will need permissions to access the first link. Thanks
(In reply to David Lozano from comment #4) > We haven't permissions to access > https://mana.mozilla.org/wiki/display/MARKET/Marketplace+Home that was just for the sequence flow which had partner details. I removed the details and posted it publicly on the wiki
Did some refactoring of the tracking bugs. This one I'm treating as tracking any work required on the client side for payment provider flow. Let's use bug 775802 for the marketplace work, so that people don't get confused.
Summary: [meta] Implement new payment provider flow → [meta] Implement new client side payment provider flow
Closing this bug as fixed - at this point, the client-side implementation for mozPay is finished and validated (although there's always a change of regressions, but this webapi I'm not expecting to regress due to low code churn). Trustworthy UI is being tracked separately against bug 801561, although the work is pretty much done there implementation-wise with some followups.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.