Jamie McClelland

I think this is an important feature! And, I think this is a duplicate of of #240, which has a long conversation in the pull request. I think the other...

I resolved the issue by fixing a an error in the javascript script. There is an undefined variable (currentTotal - perhaps defined on contribution pages, not on event registration pages)....

Found yet another error situation. The check for currentTotal is not reliable. If you have a priceset with a default price selected, then currentTotal will be set to 0 even...

I see that you even have code commented out that allows us to use Stripe without the javascript. I think we should switch to using that code or at least...

I agree having the credit card details submitted via javascript is a nice feature of stripe and adds additional security above and beyond any of the other payment processors available...

I'm leaving this issue open (since we have a new use case the triggers the error that I haven't not tracked down and fixed). I have opened #113 to cover...

I'm not running any 4.6 instances at the moment - but since there is a separate 4.6-dev and 4.7-dev branches, perhaps this could be committed to the 4.7-dev branch?

I think this is an important feature and I would really like to see it added. It seems like the only outstanding issue is h-c-c's suggestion about how to handle...

Functionally it's the same, however, by supporting handlePaymentNotification we will provide support for the new standard way to distinguish between payment processors - so if users follow the general CiviCRM...

And create unit tests to ensure that our IPN code continues to work. I'm happy to work on this ticket.