Page History

eWAY is a payment gateway for credit card payments over a secure connection. It conforms to PSI DSS (Payment Card Industry Data Security Standard). 

CSS supports the two newer current eWAY Rapid API methods:

• eWAY Secure Fields - fields securely hosted by eWAY appear in the form on your website.
• eWAY Responsive Shared Page - an entirely eWAY hosted payment popup form for the customer to enter their card details so the payment process is removed from your site altogether. If credit card fees are charged on your site, Responsive Shared Page is recommended. 

The two older (deprecated) methods are also supported:

...

For more information on eWAY's payment solutions, refer to their website.

eWAY Payment Processing Overview

Credit card payment using eWAY is processed through the following steps:. Commerce Vision never handles or even sees credit card information at any point in the process.

1. A site user creates an order and goes through checkout.

2. They select credit card as their payment option

   and will be presented with credit card input fields.

   .

3. What they see depends on the method used on your site:

   If Secure Fields is in use,

   then fields securely hosted by eWAY appear in the form. If Responsive Shared Page is used, then customers will be redirected to a form entirely

   the user will see the credit card form with input fields securely hosted by eWAY.

    

   Image Added 4. They enter their card details and submit their order.

    

   5. Commerce Vision does the preliminary setup and checks

   :for Secure Fields: ensure

   to ensure the order is valid for submission and payment information is set up, request an Access Code for the transaction from eWAY over a secure connection

   which needs to be posted with the card information
4. for Responsive Shared: pass the customer and transaction details to eWAY to generate a Responsive Shared Page URL, redirect the customer to the URL to enter payment information
For Secure Fields, we

. 6. We post/submit the page (including the credit card information and the Access Code) directly to eWAY's servers.

For

If Responsive Shared Page

, we

is in use, no form is displayed.  Image Added 4. Instead, when the buyer clicks 'Process Payment', the system passes the user and transaction details to eWAY to generate a Responsive Shared Page URL with a popup form for entering card information. This form is entirely hosted by eWAY.  Image Added 5. They enter their card details and submit their order. 6. We request the results from eWAY using the Access Code.

Commerce Vision never handles or even sees credit card information at any point in the process.

7. For both methods, eWAY processes the payment and then redirects the user to our return page, which finalises the order and triggers the appropriate Success or Fail page to be displayed. Image Added

...

When setting eWAY up on your site, CV Support will configure method selected for your website will be using will have been set up. However, note that you can change the method yourself. Note - if you change methods, the relevant new API key need to be created. 

1. In the CMS, navigate to Settings → Feature Management → Payment & Checkout.
   
   
2. If not already onenabled, toggle on Payment Provider on.
   
   
3. Click Configure.
    
4. In Provider Selection, select the eWAY method required.
   
   
5. Click Save or Save and Exit. 

eWAY methods

Secure Fields

Secure Fields involve a simple, single server side call to process a transaction. Secure fields hosted by eWAY appear in the form.  

Responsive Shared Page

...

...

Image Removed

Instead, when the buyer clicks 'Process Payment', they will see a popup form from eWAY for entering credit card information. 

Image Removed

Once payment is processed, the form closes and the buyer will be redirected to your site's Order Confirmation page.

Image Removed

Deprecated methods

Both these methods use eWAY's Transparent Redirect solution. They are deprecated but are still available in the CSS.

...