Question

Photo of Matthew Meekins

0

Payment Error

4

We've implemented online giving through Rock recently and some people are having trouble with it. There's two things coming up that I've seen. One is an exception, "Object reference not set to an instance of an object."

The other is this screen shot that I was sent today that multiple people have seen.

IMG_2714.JPG

I know that the issues happen across multiple devices and browsers. 

  • Photo of Jim Michael

    1

    Regarding the PayFlow error, this might help http://therealdanvega.com/blog/2013/11/29/paypal-payflowpro-result117-failed-merchant-rule-check  That error can come from a too-large transaction, or a mis-set security setting.

    Regarding the Exception... we have see this on our current ChMS when you stay on the giving page too long before actually submitting the form... something times out. Is that possibly the case here, or are you seeing that error immediately when giving in a normal (reasonably quick) fashion?

  • Photo of Robbie Funderburk

    0

    Jim,  Thanks for the heads up here with the Exception.   I called PayFlow Pro and they confirmed that this setting was indeed the source of the problem with the 117 Error.   Unfortunately we can't check it to prove that it works due to the "Object reference not set to an instance of an object." problem.   At this point we can not enter a financial transaction in any way shape or form.

  • Photo of Jim Michael

    0

    If you look at the exception table, do you get any more information surrounding this object error? I also wonder if something might be "stuck" because of the other errors, and restarting Rock might fix it? Have you tried restarting the application and clearing the cache? Full disclosure: most of this is just stabs in the dark since I'm not an expert with the code/giving side of things. Hopefully someone with more mojo on this topic will jump in ;-)

  • Photo of Robbie Funderburk

    0

    Thanks for your help!  The answer was in the Payflow side where we had the setting wrong mentioned in the first post.   The other problem was in a workflow that was created in error.