Currently we only handle the payment notifications AUTHORISED/CANCELLED while in the PaymentInitiated state.
We are seeing oopses like (update with web-link when setup): www-oops/2010-10-27/71154-1761rangpur53.oops
because they are arriving after the subscription has already transitioned past PaymentInitiated.
Currently we only handle the payment notifications AUTHORISED/ CANCELLED while in the PaymentInitiated state.
We are seeing oopses like (update with web-link when setup): 2010-10- 27/71154- 1761rangpur53. oops
www-oops/
because they are arriving after the subscription has already transitioned past PaymentInitiated.