Closed Bug 740652 Opened 10 years ago Closed 10 years ago

[traceback] PaypalError: Bad refund status for seller_1322765404_biz@gmail.com: NOT_PROCESSED

Categories

(addons.mozilla.org Graveyard :: Public Pages, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: krupa.mozbugs, Assigned: ashort)

References

()

Details

Attachments

(1 file)

steps to reproduce:
1. Make a purchase and ask for refund or be lazy and load https://marketplace-dev.allizom.org/en-US/support/5078691/reason



observed behavior:
traceback- 
PaypalError: Bad refund status for seller_1322765404_biz@gmail.com: NOT_PROCESSED

"NOT_PROCESSED – Request rejected because it cannot be processed at this time"
Blocks: 735764
Blocks: 740236
Allen, you looked at some of this before. The response from Paypal is:

{'responseEnvelope.build': '2486531', 'currencyCode': 'USD', 'responseEnvelope.timestamp': '2012-03-29T16:31:59.240-07:00', 'responseEnvelope.correlationId': '09528c5987e62', 'refundInfoList.refundInfo(1).receiver.amount': '0.30', 'refundInfoList.refundInfo(1).refundStatus': 'NO_API_ACCESS_TO_RECEIVER', 'refundInfoList.refundInfo(1).receiver.email': 'andy_1318364497_biz@gmail.com', 'refundInfoList.refundInfo(0).receiver.email': 'seller_1322765404_biz@gmail.com', 'refundInfoList.refundInfo(0).refundStatus': 'NOT_PROCESSED', 'responseEnvelope.ack': 'Success', 'refundInfoList.refundInfo(0).receiver.amount': '0.99'}

Which means that there might be an issue with checking the order of the refundStatuses, it's blowing up on refundInfoList.refundInfo(0).refundStatus, NOT_PROCESSED first.

Second why does it need refund access to andy_1318364497_biz@gmail.com?
Assignee: nobody → ashort
Target Milestone: --- → 6.4.9
Priority: -- → P1
http://github.com/mozilla/zamboni/commit/1d74c26
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Verified as fixed.
Status: RESOLVED → VERIFIED
Attached image Postfix Screenshot
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.