Closed dermotcurranfiremelon closed 5 years ago
I would've expected that to work fine. Only thing I can suggest is make sure that the sagePay element of your web.config is built correctly as a NameValue section (as per https://github.com/JeremySkinner/SagePayMvc/blob/master/Sample/SagePayMvc.Sample/Web.config)
I can't really help further than that I'm afraid - this isn't a project I maintain/support any further (the last commit was 4 years ago), so your best bet is probably to download and debug the code directly if you're still having problems.
Only thing I can suggest is make sure that the sagePay element of your web.config is built correctly as a NameValue section (as per https://github.com/JeremySkinner/SagePayMvc/blob/master/Sample/SagePayMvc.Sample/Web.config)
The section is built as a NameValue section, so that's not it (left that out of my snippet, but its there!).
I can't really help further than that I'm afraid - this isn't a project I maintain/support any further (the last commit was 4 years ago), so your best bet is probably to download and debug the code directly if you're still having problems.
I had noticed the dates on the commits but thought i'd have a stab in the dark anyway, you never know!
I will download and debug it myself to get to the bottom of this.
Thanks for your quick response.
Hi,
After executing transactionRegistrar.Send(), the response comes back with error:
After digging around in the code I found that the notification URL being generated in the DefaultUrlResolver.BuildNotificationUrl() is:
Even though my config settings are as follows:
Notice I am using my own Controller "Payment" instead of the default "PaymentResponse" but I didn't think this would be an issue.
I have 2 questions:
Any help is appreciated.
Thanks.