Thread Starter
ariom
(@ariom)
I can confirm that worked brilliantly. We tested with a couple of $1 transactions. The payment went through without issue and in eWay is stored within its own separate Stored Payments page accessed through the Payments menu. Thank you so much.
Thread Starter
ariom
(@ariom)
That would be great. I’ll keep an eye out for an update on this. Thanks Ross.
Thread Starter
ariom
(@ariom)
Thanks for the fast response. This is the API I’m talking about: http://www.eway.com.au/developers/api/stored-(xml)
As I mentioned I don’t see any major difference between this API and the Direct Payment API. I know that might be a question for eWay itself (thats fine, I’ve already been in contact with them).
I’m hoping the only change is what is sent to eWay and the URL it’s sent to, therefore I can continue to use this awesomesauce plugin for this particular project.
Any ideas?