Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Payments and Payment Gateway / APIs /

This is a forum for discussing SilverStripe can-do payments and their APIs / Gateways.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

eWay Payment Error


Go to End


4 Posts   3668 Views

Avatar
IDOLYZ

Community Member, 40 Posts

13 September 2011 at 8:35pm

Hi,

I am trying to implement the eWay payment gateway into an ecommerce site but am running into a few errors. I'm running it in dev mode and test eWay mode.

The first is this:
[User Error] Uncaught Exception: Object->__call(): the method 'member' does not exist on 'EwayXMLPayment'

This is the code that is calling it:
$member = $this->Member();

If I comment it out, it will execute the code up until this line:
$ewayResponseFields = $eway->doPayment();

And then it doesn't return any error, just a blank page.

Has anyone got eWay working before? If so, can you please help me with this issue?

Cheers,
Ben

Avatar
eWAYPartners

Community Member, 1 Post

14 September 2011 at 6:19pm

Hi Ben,

Let us know if we can be of any assistance with this matter.

Give the Customer Care team a call on 1800 10 65 65, or email support@eWAY.com.au

Regards,

Tom
Partner Manager
eWAY - Payments made easy!

Avatar
IDOLYZ

Community Member, 40 Posts

20 September 2011 at 6:31pm

When the XML is created an passed via cURL, the response I get is:

Resource id #313

This doesn't look right... does anyone know what this means or what should be returned?

Thanks,
Ben

Avatar
IDOLYZ

Community Member, 40 Posts

26 September 2011 at 7:19pm

I found out the variables weren't getting outputted in the XML file, so I had to add the customerID variable at the top of the page, and then it worked.