v5.1 Token support for eWay (Australia)

[slim]

Just use the file I posted on the previous page - Its direct from WHMCS support staff, and it fixes the issue.

[webmaster@auses.org.au]

Just use the file I posted on the previous page - Its direct from WHMCS support staff, and it fixes the issue.

 

It's not working for me. For some reason it won't login to the gateway so I get a 'Remote Transaction Failure' message. Login details are correct and the module worked on a test account. I think maybe it's still accessing the test site even though 'test mode' is unchecked.

[slim]

What does the gateway log say?

[alexe]

I am using the new file and getting a error also, in the gateway log I get: eWay Customer Profile Not Found.

[slim]

What exactly are you trying to do when you get that error?

[iNGENUiTY]

I have the exact same error, demo mode works fine, but when trialling live billing, it fails with the same error....tried different username and passwords, but no go.

[iNGENUiTY]

*slaps forehead*

 

I had demo mode enabled when I first created the new client....so the user wasn't created on the eway side.....works fine now..

[slim]

Once you have it setup, goto a customer in WHMCS and click on the 'Credit Card Information' link in 'Clients Information'.

 

In here, if you see a 'REMOTE GATEWAY TOKEN' then you know what whmcs has sent the customers details over to eway. If you cant see this, then processing for that client wont work.

 

If the card number is in the WHMCS db, simply enter your decryption key to view the full card number, then copy it and 'update' the customers card details.

 

This will create the token at eway. You should end up seeing somthign like this...

 

 

 

If you cant see the token number, then a token at eway has not been created and therefore if you try to capture funds it wont work.

 

If you have upgraded from the regular eway module -> token module then the only way to get the individual customer tokens created at eway is:

 

1. Let each and every customer login and update their card details.

or...

2. Go through every client in WHMCS, view the card details and update them - doing this creates the token.

Edited November 1, 2012 by slim

[iNGENUiTY]

Hi Guys,

 

Im now having a issue whereas any clients created manually via the admin interface are having their CC details stored locally...even thou the eway token gateway is the only module I currently have active.... test customers that I have created via a signup process seem to work ok.

[slim]

Yeap, I have the same issue - If you have the CVC, login as the customer and update that way.. It will create the token.

 

Hopefully they will fix the admin area - it ALWAYS needs to create a token - and NEVER store locally.

[iNGENUiTY]

Yea, its crazy to have it fall back to storing locally imho.

[iNGENUiTY]

and it seems like you can only enter the CVC when the customer first signs up, editing a customer by logging in as them after creation from the admin interface wont show a place for it...

[slim]

Is someone at WHMCS watching this thread?

 

The token system isnt 100% - Its possible to store the details in the local db. When using the token module it should NEVER happen. WHMCS needs to be updated so that no matter how the card details are entered (either via admin area, via client area or when client paying individual invoice) a TOKEN is made/updated - the card should not end up in the WHMCS db under any circumstance.

 

PLEASE FIX

[Digital Anvil]

Seems as though this is a real issue that eWay nor WHMCS can be bothered fixing.

 

I am having a problem where one off payments can be successfully made using the eWay token but when a new customer purchases a service the information appears to try and validate against existing data in the eWay business center. Of course this fails as the customer does not exist in eWay as yet.

 

If I create a customer in the token system in eWay and then get that customer (after manually adding the token id to the WHMCS database) to make a payment it then works.

 

So the problem that I see is that the token system does not allow creation of new token customers from WHMCS into eWay.

 

Has anyone been able to find a work around to this?

Edited January 22, 2013 by Digital Anvil

[slim]

For me, the system is creating the tokens at eway - most of the time. Manual payments and admin side card updates are not consistant.

[Digital Anvil]

Are you able to provide your token module you are using in WHMCS? We just aren't having any success unless the client is created at eway first knowing the credit card details.

[slim]

Ask whmcs support - they provided it to me.

 

P.S I wouldnt trust anyone with providing a gateway module... For all you know it could redirect funds etc.

[Digital Anvil]

I actually spent some time with eWay and have resolved the issue - stupid check boxes. The tokenisation is now working and creating new accounts.

[Damo]

After reading through this forum post I can't tell whether the version 1 of this module is working correctly for tokens support and eWay. It appears that we will have to create a title field but there's no mention of that in the documentation.

 

My main concern is migrating customers over to it. Does anyone have a successful setup of eWay token support?

[host1164]

Yes, I have a successful setup.

Ask WHMCS support. They have an updated module that will work correctly with the sandbox credentials when in demo mode.

The copy I have has a "Created: March 2013" line in the header of the ewaytp.php file

 

There's no explicit need to create a title field - it will still function, defaulting to "Mr." if the custom field is not provided.

 

Keep in mind you will need to create an "API key" within the eway sandbox area in order to use the token module in WHMCS 5.2.2. This will go in the "Password" field in the gateway module. Your client number and username should be those you use for your sandbox.

[Damo]

Thanks for the reply.

 

What happens to customers, and their card details, that are in the current eWay module? How did you migrate them?

 

I wonder if they'll update the module for download in the docs. I prefer to have a public version then something supplied from support.

[host1164]

Do you mean the standard eWay module, or the token module? I've only made use of the token one.

Ours was a new system, there was nothing to migrate.

I'm surprised they haven't updated the module in the docs already.

[Damo]

Yes I meant from the standard eWay module. There doesn't appear to be any way to move clients across without getting them to re-enter their details.

[host1164]

Yes, without their CVV I don't think there will be a direct way to move clients across.

[slim]

Has anyone noticed the eway token module breaking after the release of 5.2.4?

 

I can successfully attempt capture from the admin area, but from the clients front end, there are problems:

 

<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><soap:Fault><faultcode>soap:Client</faultcode><faultstring>Server was unable to read request. ---> There is an error in XML document (32, 46). ---> Input string was not in a correct format.</faultstring><detail /></soap:Fault></soap:Body></soap:Envelope>

 

Invoice ID => 83

User ID => 41

Amount => 369.30

<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><soap:Fault><faultcode>soap:Client</faultcode><faultstring>Invalid CVN. </faultstring><detail /></soap:Fault></soap:Body></soap:Envelope>

 

Anyone else seen this? It means I cant process orders via the front end. I think its truncating the CVN / CVC number to two digits.. but not 100% sure.