Closed
Bug 819934
Opened 12 years ago
Closed 11 years ago
Developer settlement data (Bank details) collection
Categories
(Marketplace Graveyard :: Developer Pages, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: steve, Assigned: rforbes)
Details
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?
Comment 1•12 years ago
|
||
a=clouserw. Assigning to Steve to drive getting people to respond.
Assignee: nobody → sruston
Updated•12 years ago
|
Target Milestone: 2012-12-13 → ---
Comment 2•11 years ago
|
||
Steve: what is the status of this bug?
Comment 3•11 years ago
|
||
Bank/account collection (via Bango's API) was done in bug 795103. Is this bug about a security review maybe?
Reporter | ||
Comment 4•11 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
Comment 5•11 years ago
|
||
(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.
Comment 6•11 years ago
|
||
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
Updated•11 years ago
|
Flags: needinfo?(rforbes)
Assignee | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(rforbes)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•