Closed Bug 866939 Opened 10 years ago Closed 10 years ago

Receive server notifications about Bango payment transaction result

Categories

(Marketplace Graveyard :: Payments/Refunds, defect, P2)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED
2013-07-04

People

(Reporter: kumar, Assigned: andy+bugzilla)

References

Details

We would like to receive server notifications when Bango completes a payment. Keir, is there an easy way to do this?

Possibilities:
- IPN approach: Bango posts the transaction result to a pre-defined Mozilla server URL
- Polling approach: Bango provides an API that Mozilla can query after beginning each transaction

There are edge cases like bug 865612 where Mozilla will not get notified of payment completion if the client side redirect is interrupted. This is dangerous because Mozilla would then charge the user a second time for an item.
Blocks: 865612
-> Keir to get discussion started on this.  There is work for both of us here.
Assignee: nobody → keir
We already have an event notification API - see http://bango.zendesk.com/entries/23381152-Event-Notification-API
ok, great. I didn't know we can use that with the MozillaExporter. Do we simply need to configure Mozilla packages with a publication URL? If not, could you briefly summarize how we can activate this?
Let me know what the publication URL will be and add it as part of the package setup for Mozilla packages created via the MozillaExporter.
Awesome. We'll hoist up a URL and proceed once we have one.
Assignee: keir → nobody
Priority: -- → P2
Depends on: 869999
Depends on: 870001
Assignee: nobody → wraithan
Assignee: wraithan → amckay
We have one, it's at:

https://marketplace-dev.allizom.org/mozpay/bango/notification

It requires HTTP Basic Auth. This is for the test environment, when we know it works we can push it up the chain.

Keir, how do we set this up for receiving notifications and exchange the user and password?
Assignee: amckay → keir
We are making someone changes to the Mozilla exporter to allow you to call SetEventNotificationURL with a url, username and password.  Will update once completed, once do will allow you to control the url and username / password.
That sounds great, thanks.
I would assume that we would get notifications on chargebacks or refunds as well?
(In reply to David Bialer [:dbialer] from comment #9)
> I would assume that we would get notifications on chargebacks or refunds as
> well?

Documentation for Event Notification can be found here : http://support.bango.com/attachments/token/zno7v5ix5oswyae/?name=EventNotification_v2.0.pdf, but no, notification of refunds etc is not currently supported.
(In reply to Keir Kettle from comment #7)
> We are making someone changes to the Mozilla exporter to allow you to call
> SetEventNotificationURL with a url, username and password.  Will update once
> completed, once do will allow you to control the url and username / password.

Changes to Mozilla Exporter API now live, updated documentation sent to Kumar and Andy, but in short, changes include the ability to include a username and password when setting the event notification URL, both in CreatePackage and SetEventNotificationURL methods.  DeleteEventNotificationURL will also remove the username and password from the package.

Any questions let me know.
Reassigning to me to hook up, thanks Keir.
Assignee: keir → amckay
Target Milestone: --- → 2013-06-06
Target Milestone: 2013-06-06 → 2013-06-13
Depends on: 880467
https://github.com/mozilla/solitude/commit/53a6ec

Pending IT changes in bug 880467 before doing an end to end smoke test.
Target Milestone: 2013-06-13 → 2013-06-20
I don't see notifications coming in from Bango on payments. Should all be set up though.
Is there any way to check that Bango is sending them or having an issue? This is on mozilla -dev and on a completed payment I expected to see a POST back to:

https://marketplace-dev.allizom.org/mozpay/bango/notification
Flags: needinfo?(keir)
Target Milestone: 2013-06-20 → ---
Event notifications are enabled on a per package basis.  Looks like only a single package has been enabled on test.  There is a method in Mozilla Exporter (SetEventNotificationURL) that will allow you to do this.
Flags: needinfo?(keir)
This was implemented. We are troubleshooting configuration issues in bug 888954
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2013-07-04
You need to log in before you can comment on or make changes to this bug.