Working on a team commerce install and its been fine so far. Once we have gone live we have experienced issues with sagepay.
The site was developed and tested on a temporary URL, this all worked fine when using sagepay test accounts and it continues to work fine if we access what is now the live site via that URL (the server is still configured to respond to this URL).
The issues arrive when we use the new "live" URL (lets call it mydomain.com). When we try to pay or cancel out of a payment in Sagepay we get an error. When paying and it fails its a sagepay error 5006 which means the RedirectURL isnt provided or not in the correct format.
When i check the sagepay transactions i can see that attempts either from mydomain.com or the test URL always pass the callbackURL to Sagepay as the test URL. Is there any config anywhere that would drive where this is is generated from? I've checked in the teacommerce settings and we are providing CompleteURL and FailureURL as relative paths (/cart/complete and /cart/fail) and am not providing a domain on these.
Tearing my hair out with this one a little bit, can anyone suggest any ideas where to look or how to debug this?
If you use the latest Tea Commerce then this is the code for the SagePay provider. See line 106 where it parse the notification url. And that is using the domain that the webshop is running at.
Teacommerce callbackURL different domain question
Hi
Working on a team commerce install and its been fine so far. Once we have gone live we have experienced issues with sagepay.
The site was developed and tested on a temporary URL, this all worked fine when using sagepay test accounts and it continues to work fine if we access what is now the live site via that URL (the server is still configured to respond to this URL).
The issues arrive when we use the new "live" URL (lets call it mydomain.com). When we try to pay or cancel out of a payment in Sagepay we get an error. When paying and it fails its a sagepay error 5006 which means the RedirectURL isnt provided or not in the correct format.
When i check the sagepay transactions i can see that attempts either from mydomain.com or the test URL always pass the callbackURL to Sagepay as the test URL. Is there any config anywhere that would drive where this is is generated from? I've checked in the teacommerce settings and we are providing CompleteURL and FailureURL as relative paths (/cart/complete and /cart/fail) and am not providing a domain on these.
Tearing my hair out with this one a little bit, can anyone suggest any ideas where to look or how to debug this?
Thanks in advance
Hmm that sounds weird :(
Have you changed the full homepage url in SagePay - see image 1 here: https://documentation.teacommerce.net/guides/payment-providers/sage-pay/
If you use the latest Tea Commerce then this is the code for the SagePay provider. See line 106 where it parse the notification url. And that is using the domain that the webshop is running at.
https://github.com/TeaCommerce/Payment-providers/blob/master/Source/TeaCommerce.PaymentProviders/Classic/SagePay.cs
Someone that had a 5006 error as well:
https://our.umbraco.org/projects/website-utilities/tea-commerce/tea-commerce-support/77804-error-5006-sagepay
Kind regards
Anders
is working on a reply...