Closed Bug 795492 Opened 13 years ago Closed 13 years ago

Create Data Flow diagram for payments refunds on FFOS V1

Categories

(Marketplace Graveyard :: Payments/Refunds, defect)

Product:
Marketplace Graveyard
Component:
Payments/Refunds
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
2012-12-06

People

(Reporter: cgalimidi, Assigned: mhanratty)

References

Details

Need a data flow reflecting the refund process. User Scenario: User requests refund of purchased app within 30 minute window Out-of-Scope: - User requests refund of purchased app after 30 minutes - User requests refund for in-app purchase (Path for customer = Contact support and they will direct you either to the payment provider or developer as appropriate)
Assignee: nobody → kumar.mcmillan
Is this just for internal use only? Or is an external partner requiring this? Just wondering, as that affects if this should block ship or not.
should not block ship... this bug is just for kumar to define / document the data flow as part of the technical spec for payments. want to make sure we can share the refund with UX and QA team.
I'm hoping to build on the data flow that rforbes is currently working on (the pay flow)
Blocks: marketplace-payments
No longer blocks: basecamp-payments
I think we've talked about giving this to Maureen. Maureen+David+Me to solve this before Wednesday.
Assignee: kumar.mcmillan → mhanratty
Target Milestone: --- → 2012-12-06
https://www.dropbox.com/s/7u8upr885b4kslc/Marketplace-Refunds-Q4-v3.pdf
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.