Moving existing CC clients to eWay Token Payments

[tonyz]

Now the eWay AU token payments module has been released

 

http://docs.whmcs.com/EWay_Tokens

 

how should we go about moving clients with stored credit card information across to tokenised payments please?

 

Tony

--

[WHMCS John]

Hi,

It's pretty straight forward:

 

You should first enable & configure the eWay Tokens module, then disable the regular eWay module ensuring to select the option to assign clients to the Token module: http://docs.whmcs.com/Payment_Gateways#Deactivating_Gateway_Modules

 

Now your clients can login and pay their next invoice manually to save their card details on eWay's servers and in future payments will be attempted automatically.

[slim]

This really isnt a suitible migration - Getting large numbers of customers to submit their card information 'out of the blue' is simply going to cause grief. There needs to be a migration of the data.

 

Also, you do not explain how the existing card data gets removed from the WHMCS database? What triggers this removal?

[DigitalEnigma]

Hi,

 

If this is anything like the SagePay Token module a migration of data without the client manually paying isn't going to be possible.

 

I know with SagePay the user need to enter their CV2 number when creating the token, this only happend when they manually pay, I brought this up in beta of 5.1 which added the SagePay token support as the customer needs the ability to enter the CV2 during card update for a new token to be generated. This is still not possible in 5.1.2 though Matt did advise they were working on a solution for this so the user can enter the CV2 when using a token gateway.