EWAY Tokens - Revision history

John: Redirected page to EWAY Rapid 3.1

2018-07-03T14:22:35Z

Redirected page to EWAY Rapid 3.1

AlexN at 08:29, 11 June 2018

2018-06-11T08:29:56Z

John: /* Updating Clients' Credit Card Details via the Admin Area */

2017-12-20T18:34:09Z

‎Updating Clients' Credit Card Details via the Admin Area

Joshua: /* Updating Clients' Credit Card Details via the Admin Area */

2017-12-20T18:32:41Z

‎Updating Clients' Credit Card Details via the Admin Area

Joshua: /* Updating Clients' Credit Card Details via the Admin Area */

2017-12-20T18:21:13Z

‎Updating Clients' Credit Card Details via the Admin Area

Joshua: /* Updating Clients' Credit Card Details via the Admin Area Credit Card Details Popup */

2017-12-20T18:18:44Z

‎Updating Clients' Credit Card Details via the Admin Area Credit Card Details Popup

Joshua at 18:13, 20 December 2017

2017-12-20T18:13:58Z

John at 13:52, 4 July 2017

2017-07-04T13:52:10Z

John: /* Migrating to the eWAY Tokens Module */

2017-07-04T11:03:26Z

‎Migrating to the eWAY Tokens Module

John at 17:26, 7 April 2017

2017-04-07T17:26:41Z

← Older revision		Revision as of 14:22, 3 July 2018
Line 1:		Line 1:
−	~~{{gateways~~	+	#REDIRECT [[EWAY_Rapid_3.1]]
−	~~\| type = token~~
−	~~\| onetime = yes~~
−	~~\| recurring = yes~~
−	~~\| refunds = yes~~
−	~~\| updatecc = yes~~
−	~~\| 3dsecure = yes~~
−	}}
−
−	eWAY is a leading global merchant payment services provider that operates accross a number of countries. At the time of writing Australia, New Zealand, United Kingdom, Singapore, Hong Kong & Malaysia, with the USA scheduled to be added later this year.
−	eWAY Tokens, the name of the module available in WHMCS, is a [http://developers.whmcs.com/payment-gateways/tokenised-remote-storage/ tokenised gateway] that allows you to perform credit card processing and recurring billing without having to store credit card details locally.
−
−	Going one step further than a lot of other payment gateway solutions, eWAY's Transparent Redirect implementation method which the WHMCS module takes advantage of provides a seamless checkout experience for customers while ensuring card details never pass through your web server, allowing you to avoid most PCI Compliance requirements and negating any of the risks normally associated with processing and storing credit cards on your website.
−
−	~~Contrary to what you might think, you should not tick the setting to "Disable Credit Card Storage" in '''Setup > General Settings > Security''' as that will disable entry by a client.~~
−
−	~~===Creating an eWAY API Account===~~
−
−	~~All requests to eWAY's Rapid API are authenticated using basic authentication, this uses the eWAY API Key and Password.~~
−
−	~~To create an API key:~~
−
−	~~#Log in to your Partner Portal account~~
−	~~#Navigate to ''Resources > Sandbox/Testing'' and click on 'Request Sandbox'~~
−	~~##Note: Skip this step if you already have a Sandbox account~~
−	~~#Navigate to the Sandbox Login page~~
−	~~#Go to ''My Account > User Security > Manage Roles''~~
−	~~#Create role under name of "API KEY"~~
−	~~#Go to ''My Account > User Security > Create User''~~
−	~~#Assign "API KEY" role to new user.~~
−	#~~Choose a name, enter your email address and choose a password.~~
−	~~#Once the role is created, click ‘actions’ dropdown menu and click "View API Key"~~
−	~~#Select the Rapid API Key, the password you set in step 8 is the API password for this key.~~
−
−	~~For full instructions, including login links, please refer to the~~ [[~~https://eway~~.~~io/api-v3/#authentication\|eWAY Website~~]]
−
−	~~===Test Mode===~~
−
−	The eWAY test mode has a feature to use the "pennies" value of the invoice total to return that specific status code. To ensure this is not triggered, ensure your testing invoices have a 0 "penny" amount.
−
−	~~You can also set the Sandbox to always approve, by logging into the Sandbox and navigating to Settings > Sandbox and changing the transaction response to Always Approve.~~
−
−	~~===Migrating to the eWAY Tokens Module===~~
−
−	In earlier versions of WHMCS, there were modules for eWAY that did not make use of the Transparent Redirect or Tokenised storage mechanisms. If you are using one of these payment gateway solutions, we encourage you to look at migrating to the newer eWAY Tokens module.
−
−	If you are using a payment gateway module named "eWAY", switching to the current module will require your clients login and enter their credit card payment details manually the first time they receive an invoice following the switch. This is so that eWAY can capture your customers credit card details in order to create a token.
−
−	To make the switch, simply activate the new module which you'll find in ''Setup > Payment Gateways'' listed as '''eWAY Token Payments''', configure it with your eWAY RapidAPI credentials, and then click the deactivate button next to the older module, at which point you'll be prompted to choose a replacement payment gateway for items assigned to that currently, and there you should just select the eWAY Token Payments module from the dropdown provided.
−
−	~~For more information or advice on the various payment gateway solutions eWAY offers, you can contact eWAY directly via https://www.eway.com.au/contact-us~~
−
−	~~===Updating Clients' Credit Card Details via the Admin Area===~~
−
−	Transferring a local card to remote storage from within the admin area is not currently supported by the eWAY Tokens Module. The client should make the first payment via the client area in order for WHMCS to store their card details remotely with the eWAY Tokens module.
−
−
−
−	~~{{modules}}~~

@@ Line 45: / Line 45: @@
 In earlier versions of WHMCS, there were modules for eWAY that did not make use of the Transparent Redirect or Tokenised storage mechanisms.  If you are using one of these payment gateway solutions, we encourage you to look at migrating to the newer eWAY Tokens module.
-If you are using a payment gateway module named "eway", switching to the current module will require your clients login and enter their credit card payment details manually the first time they receive an invoice following the switch.  This is so that eWay can capture your customers credit card details in order to create a token.
+If you are using a payment gateway module named "eWAY", switching to the current module will require your clients login and enter their credit card payment details manually the first time they receive an invoice following the switch. This is so that eWAY can capture your customers credit card details in order to create a token.
 To make the switch, simply activate the new module which you'll find in ''Setup > Payment Gateways'' listed as '''eWAY Token Payments''', configure it with your eWAY RapidAPI credentials, and then click the deactivate button next to the older module, at which point you'll be prompted to choose a replacement payment gateway for items assigned to that currently, and there you should just select the eWAY Token Payments module from the dropdown provided.

@@ Line 53: / Line 53: @@
 ===Updating Clients' Credit Card Details via the Admin Area===
-Transferring a local card to remote storage from within the admin area is not currently supported by the eWAY Tokens Module. The client need to make the first payment via the client area in order for WHMCS to store their card details remotely with the eWAY Tokens module.
+Transferring a local card to remote storage from within the admin area is not currently supported by the eWAY Tokens Module. The client should make the first payment via the client area in order for WHMCS to store their card details remotely with the eWAY Tokens module.
 {{modules}}

@@ Line 53: / Line 53: @@
 ===Updating Clients' Credit Card Details via the Admin Area===
-It isn't possible to transfer a local card to remote storage from within the admin area when using eWAY Tokens. The client has to make the first payment via the client area in order for WHMCS to store their card details remotely with the eWAY Tokens module.
+Transferring a local card to remote storage from within the admin area is not currently supported by the eWAY Tokens Module. The client need to make the first payment via the client area in order for WHMCS to store their card details remotely with the eWAY Tokens module.
 {{modules}}

@@ Line 53: / Line 53: @@
 ===Updating Clients' Credit Card Details via the Admin Area===
-It isn't possible to transfer a local card to remote storage from within the admin area when using eWay Tokens. The client has to make the first payment via the client area in order for WHMCS to store their card details remotely with the eWay Tokens module.
+It isn't possible to transfer a local card to remote storage from within the admin area when using eWAY Tokens. The client has to make the first payment via the client area in order for WHMCS to store their card details remotely with the eWAY Tokens module.
 {{modules}}

@@ Line 51: / Line 51: @@
 For more information or advice on the various payment gateway solutions eWAY offers, you can contact eWAY directly via https://www.eway.com.au/contact-us
-===Updating Clients' Credit Card Details via the Admin Area Credit Card Details Popup===
+===Updating Clients' Credit Card Details via the Admin Area===
 It isn't possible to transfer a local card to remote storage from within the admin area when using eWay Tokens. The client has to make the first payment via the client area in order for WHMCS to store their card details remotely with the eWay Tokens module.

← Older revision		Revision as of 18:13, 20 December 2017
Line 50:		Line 50:

	For more information or advice on the various payment gateway solutions eWAY offers, you can contact eWAY directly via https://www.eway.com.au/contact-us		For more information or advice on the various payment gateway solutions eWAY offers, you can contact eWAY directly via https://www.eway.com.au/contact-us
		+
		+	===Updating Clients' Credit Card Details via the Admin Area Credit Card Details Popup===
		+
		+	It isn't possible to transfer a local card to remote storage from within the admin area when using eWay Tokens. The client has to make the first payment via the client area in order for WHMCS to store their card details remotely with the eWay Tokens module.
		+
		+

	{{modules}}		{{modules}}

@@ Line 9: / Line 9: @@
 eWAY is a leading global merchant payment services provider that operates accross a number of countries.  At the time of writing Australia, New Zealand, United Kingdom, Singapore, Hong Kong & Malaysia, with the USA scheduled to be added later this year.
-eWAY Tokens, the name of the module available in WHMCS, is a tokenised gateway [link to Tokenised Gateways docs] that allows you to perform credit card processing and recurring billing without having to store credit card details locally.
+eWAY Tokens, the name of the module available in WHMCS, is a [http://developers.whmcs.com/payment-gateways/tokenised-remote-storage/ tokenised gateway] that allows you to perform credit card processing and recurring billing without having to store credit card details locally.
 Going one step further than a lot of other payment gateway solutions, eWAY's Transparent Redirect implementation method which the WHMCS module takes advantage of provides a seamless checkout experience for customers while ensuring card details never pass through your web server, allowing you to avoid most PCI Compliance requirements and negating any of the risks normally associated with processing and storing credit cards on your website.

← Older revision		Revision as of 11:03, 4 July 2017
Line 46:		Line 46:

	If you are using a payment gateway module named "eway", switching to the current module will require your clients login and enter their credit card payment details manually the first time they receive an invoice following the switch. This is so that eWay can capture your customers credit card details in order to create a token.		If you are using a payment gateway module named "eway", switching to the current module will require your clients login and enter their credit card payment details manually the first time they receive an invoice following the switch. This is so that eWay can capture your customers credit card details in order to create a token.
−
−	If you are using the payment gateway module named "eway tokens" then the current module can act as a drop-in replacement for that and the existing tokens will be able to be used by the newer module, so recurring billing can continue interupted.

	To make the switch, simply activate the new module which you'll find in ''Setup > Payment Gateways'' listed as '''eWAY Token Payments''', configure it with your eWAY RapidAPI credentials, and then click the deactivate button next to the older module, at which point you'll be prompted to choose a replacement payment gateway for items assigned to that currently, and there you should just select the eWAY Token Payments module from the dropdown provided.		To make the switch, simply activate the new module which you'll find in ''Setup > Payment Gateways'' listed as '''eWAY Token Payments''', configure it with your eWAY RapidAPI credentials, and then click the deactivate button next to the older module, at which point you'll be prompted to choose a replacement payment gateway for items assigned to that currently, and there you should just select the eWAY Token Payments module from the dropdown provided.

← Older revision		Revision as of 17:26, 7 April 2017
Line 12:		Line 12:

	Going one step further than a lot of other payment gateway solutions, eWAY's Transparent Redirect implementation method which the WHMCS module takes advantage of provides a seamless checkout experience for customers while ensuring card details never pass through your web server, allowing you to avoid most PCI Compliance requirements and negating any of the risks normally associated with processing and storing credit cards on your website.		Going one step further than a lot of other payment gateway solutions, eWAY's Transparent Redirect implementation method which the WHMCS module takes advantage of provides a seamless checkout experience for customers while ensuring card details never pass through your web server, allowing you to avoid most PCI Compliance requirements and negating any of the risks normally associated with processing and storing credit cards on your website.
		+
		+	Contrary to what you might think, you should not tick the setting to "Disable Credit Card Storage" in '''Setup > General Settings > Security''' as that will disable entry by a client.

	===Creating an eWAY API Account===		===Creating an eWAY API Account===