By clicking “Accept All”, you agree to the storing of cookies on your device to enhance site navigation, analyse site usage, and assist in our marketing efforts
Essential
These cookies enable our website and App to remember things such as your region or country, language, accessibility options and your preferences and settings.
Analytics
Analytic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.
Marketing
Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.
Drop us an email if you want to try our Sage Pay Suite extension, we offer free and paid versions and we can even install it on your server for free. Cheers!
We've been there a few years ago, and believe me, inventory issues were way to much of a trouble for many many merchants, and when your user base is over 3.5K merchants, you have to take decisions in favor of what's better for the majority of them.
Having said this, we offer free support...
Clodbuster, as mentioned on another thread, we are keen to help you (with no extra cost), can you please PM us to get your details? Orphans transactions usually have an explanation, and we are eager to help you, and help others facing this issue.
Thanks for your feedback.
We have posted an explanation of Sage Pay Suite "orphan" transactions on post #2271244, we are happy to help anyone facing Sage Pay integration issues with Magento, feel free to PM us if you need assistance.
Thanks.
Hello guys,
Let me explain how orphan transactions work in Sage Pay Suite on Magento.
The concept is simple, all Sage Pay transactions started by a customer are saved in a Magento table, if everything goes as expected and the customer actually completes the order that transaction will be...
Hello,
Have you checked your Magento log files? Also, you might want to debug using Firebug as this could be caused by a Javascript conflict (in case you use both, jQuery and Prototype).
Thanks.