The app payment setup page on the devhub is pretty complicated and if part of the flow fails can lead to payments not being set up correctly. But never fear, we've got an API to test this now: http://firefox-marketplace-api.readthedocs.org/en/latest/topics/apps.html#post--api-v1-apps-app-%28int-id%29-payments-status- This could be an automatic check on save, or maybe a manual check to make sure everything ran ok. I prefer the manual one, it might need to occur after the save though, because the save is still needed to set things up prior to checking.

We're not sure what this bug means. Andy - would you expand on comment 0?

Basically this is a test transaction sent from the developer hub to ensure that everything works ok. Imagine a button that you press and it says "Payments ready to go!" or "Something went wrong." This will do a test transaction and ensure that things are ok. This bug originally came from Paypal because we didn't really now how well a payment account was set up without testing it because we didn't onboard developers. For Bango this is less relevant because we onboard developers. For Boku they manually onboard developers. I'm fine with closing this now.