Closed
Bug 797927
Opened 13 years ago
Closed 12 years ago
Add support for handling of postback and chargeback URLs that point to a 404
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
2013-01-31
People
(Reporter: jsmith, Assigned: andy+bugzilla)
References
Details
(Whiteboard: u=dev c=pmt p=2)
We need to add support for handling of the postback and chargeback URLs that point to a 404 in the payment process. This bug tracks the implementation of whatever is necessary to be implemented to handle this fallback case.
| Reporter | ||
Updated•13 years ago
|
Blocks: basecamp-payments
Comment 1•13 years ago
|
||
We can probably just email the developer so that they know about it. btw, notifications are happening in bug 795143
Blocks: 794651
Comment 2•13 years ago
|
||
Email sounds fine to me. This will cover more than just 404s too - temporary outages, etc.
| Assignee | ||
Comment 3•13 years ago
|
||
If a certain number of postbacks fail, they should probably go into a re-review queue. cc'ing robhudson for that.
| Reporter | ||
Updated•13 years ago
|
Updated•13 years ago
|
Depends on: market-packaged-apps
Comment 4•13 years ago
|
||
Rob, how does this depend on packaged-apps?
Comment 5•13 years ago
|
||
(In reply to Kumar McMillan [:kumar] from comment #4)
> Rob, how does this depend on packaged-apps?
Yeah, that makes no sense.
I saw Andy's note about re-reviewing apps if postbacks fail and wanted to track it. I should file a bug for myself that depends on this one.
No longer depends on: market-packaged-apps
Comment 7•12 years ago
|
||
comment 3 is now bug 831390. This bug is just about email
Updated•12 years ago
|
Assignee: nobody → amckay
Target Milestone: --- → 2013-01-24
Updated•12 years ago
|
Target Milestone: 2013-01-24 → 2013-01-31
Updated•12 years ago
|
Priority: P3 → P2
Version: 1.0 → 1.1
| Assignee | ||
Comment 8•12 years ago
|
||
| Assignee | ||
Comment 9•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•