866939 - Receive server notifications about Bango payment transaction result

Status: RESOLVED FIXED

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

Description

[Kumar McMillan [:kumar]]

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.

Comment 1

[Wil Clouser [:clouserw]]

-> Keir to get discussion started on this.  There is work for both of us here.

Comment 2

[Keir Kettle]

We already have an event notification API - see http://bango.zendesk.com/entries/23381152-Event-Notification-API

Comment 3

[Kumar McMillan [:kumar]]

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?

Comment 4

[Keir Kettle]

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.

Comment 5

[Kumar McMillan [:kumar]]

Awesome. We'll hoist up a URL and proceed once we have one.

Comment 6

[Andy McKay]

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?

Comment 7

[Keir Kettle]

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.

Comment 8

[Andy McKay]

That sounds great, thanks.

Comment 9

[David Bialer [:dbialer]]

I would assume that we would get notifications on chargebacks or refunds as well?

Comment 10

[Keir Kettle]

(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.

Comment 11

[Keir Kettle]

(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.

Comment 12

[Andy McKay]

Reassigning to me to hook up, thanks Keir.

Comment 13

[Andy McKay]

https://github.com/mozilla/solitude/commit/53a6ec

Pending IT changes in bug 880467 before doing an end to end smoke test.

Comment 14

[Andy McKay]

I don't see notifications coming in from Bango on payments. Should all be set up though.

Comment 15

[Andy McKay]

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

Comment 16

[Keir Kettle]

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.

Comment 17

[Kumar McMillan [:kumar]]

This was implemented. We are troubleshooting configuration issues in bug 888954