If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Developer settlement data (Bank details) collection

RESOLVED FIXED

Status

Marketplace
Developer Pages
RESOLVED FIXED
5 years ago
4 years ago

People

(Reporter: Steve Ruston, Assigned: rforbes)

Tracking

x86
Mac OS X
Points:
---

Details

(Reporter)

Description

5 years ago
Validation of the use of bank details and data flows between Mozilla and Bango took place Thursday 6th of December. 
Details of the flow can be found at:https://wiki.mozilla.org/Apps/ID_and_Payments 

It was agreed the developer data can be collected on Mozilla pages and passed via the Solitude API to Bango.

There will be a further review of the Bango Web App for developers to see their current payment details and reports, but this is a separate item.

Please can all people cc'd agree this can now be closed and a further bug will be opened to cover the review of the Bango web app?
a=clouserw.  Assigning to Steve to drive getting people to respond.
Assignee: nobody → sruston
Target Milestone: 2012-12-13 → ---
Steve: what is the status of this bug?
Bank/account collection (via Bango's API) was done in bug 795103.

Is this bug about a security review maybe?
(Reporter)

Comment 4

5 years ago
Yes it was, during the call about using bank data, all the people on it said we need a bug for everyone to accept the decision
(In reply to Steve Ruston from comment #4)
> Yes it was, during the call about using bank data, all the people on it said
> we need a bug for everyone to accept the decision

Please drive this forward and close when finished. Thanks.
Raymond - this bug is super old and I assume you've been looking at security flows since it was filed.  If you have, would you resolve this?
Assignee: sruston → rforbes
Flags: needinfo?(rforbes)
(Assignee)

Updated

4 years ago
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Flags: needinfo?(rforbes)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.