Closed markmead closed 2 years ago
Sage Pay will send a POST to the notify url. Make sure you don't have any CSRF security on that route. Laravel will use that by default, unless you explicitly disable it. Other frameworks are likely to do the same.
Though having read again, that's not the problem you are having!
The 3011 comes from the remote server. Could it be only accepting https?
Error documentation here https://www.opayo.co.uk/search/all?keyword=3011
I think HTTP is fine, but this line is the answer.
The NotificationURL field must contain a Fully Qualified Domain Name
Thankfully, Lando provides a http://name.land.site/
URL, I'll give that a whirl.
Oh course, that makes sense. You can use a service such as https://ngrok.com/ to tunnel the notifications to your local machine, if you aren't working on a public domain.
NGROK was the ticket, thanks a lot!
Now it's working I'm a little lost on how you handle where to redirect a user when they click "Cancel", I've looked through the README but I can't seem to find anything that answers this.
Ignore me, it was an issue in the code, hah! Thanks for all the help!
No, it was a good question that others are bound to hit, and you stuck around to confirm what the fix was :-)
Hello there 👋
I'm trying to update to v3 making use of
SagePay_Server
but when I use a named/local route fornotifyUrl
I hit the following error:Here's the code that is causing the issue:
Results to something like
http://localhost:12345/payment/notify
.Strangely (to me), if I pass in a route like
http:://www.something123.test/
it works fine.It's worth noting that I am using Lando.