eWAY Eway is a payment gateway for credit card payments over a secure connection. It conforms to PSI PCI DSS (Payment Card Industry Data Security Standard).
CSS supports four eWAY Rapid API methods:
...
The Customer Self Service eCommerce Platform supports the current Eway 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 orders for your site, Responsive Shared Page is recommended.
Info |
---|
To use the current Eway methods, websites must be on version 4.23+. |
The two older (deprecated) methods are also supported:
- Rapid API Version 3
- eWAY Direct Connection API / using Secured Fields
- eWAY Responsive Shared Page API
- Rapid API Version 1.1
For more information on eWAY's payment solutions, refer to their website.
Note |
---|
|
Eway Payment Processing Overview
Credit card payment using eWAY Eway is processed through the following steps:
...
. At no point does Commerce Vision handle or see credit card information during the transaction.
- The site user creates an order and goes through checkout.
They select credit card as their payment option
and will be presented with credit card input fields..
What they see next depends on the method selected for your site:
For Secure Fields, the credit card form with input fields securely hosted by Eway will be displayed.
4. They enter their card details and submit their order.
setup and checks, such as:5. Commerce Vision does the preliminary
checks to ensure the order is valid for submission
payment informationrequestand payment information is set up
eWAY, then requests an Access Code for the transaction from
which needs to be posted with the card information.Once our checks and set ups are done, we post/submit theEway over a secure connection
on behalf of the user.
6. The page (including the credit card information and the Access Code)
eWAYis submitted directly to
. Their credit card information goes directly to eWAY. Commerce Vision never handles or even sees the information at any point in the process.eWAYEway's servers
our.
For Responsive Shared Page is in use, no form is displayed.
4. Instead, the user clicks 'Process Payment'.
5. The system passes the user and order transaction details to eWAY, which generates a popup form for entering card details. This form is entirely hosted by Eway.
6. The user enters their card details and submits their order.
7. For both methods, Eway processes the payment and then redirects the user to
, which finalises the order and triggers the appropriateyour site's return page
to be displayed. The order is finalised, triggering either the Success or Fail page
.
Step-by-step guide
Note |
---|
|
...
Select an Eway method
When your site uses an Eway method to process credit cards, this the message appears in the 'Payment' panel of the Checkout page under the Credit Card tab . It includes the eWAY method actively used will include the Eway method active on your site.
Once eWAY has been set up on your site, the eWAY method required can be selected for credit card processing and paymentDuring setup, Commerce Vision will configure the selected method for your website. However, note that you can change and configure the method yourself. NOTE - if you change methods, the relevant new API key need to be generated.
- In the CMS, navigate to Settings → Feature Management → Payment & Checkout.
- If not already onenabled, toggle ON Payment Provider on.
- Click Configure.
- In Provider Selection, select the eWAY Eway method required for your site.
- Click Save or Save and Exit.
Tip |
---|
You can also select the payment option in Settings → Settings → Orders → Credit Cards. In the 'C/Card Payment Provider' field, select the eWAY method required. |
eWAY methods
Direct Connection API
Direct Connection API involves a simple, single server side call to process a transaction. In CSS, it is implemented with eWAY's Secure Fields. This inserts eWAY hosted secure iframes into the card fields on your website so the customer is kept on your site during the payment process.
Responsive Shared Page API
This method is an entirely eWAY hosted payment form for the customer to enter their card details. So the payment process is removed from your site altogether. If this method is active on your site, there are no credit card fields in the Payment panel of the Checkout page.
Instead, when the buyer clicks 'Process Payment', they will see a popup box for entering credit card information from eWAY.
Once payment is processed, the box closes and the buyer will be taken to your site's Order Confirmation page.
- Ensure the configuration settings are correct.
- Click Save or Save and Exit.
Info | ||
---|---|---|
| ||
If When using eWAY Eway Responsive Shared Page:
|
Deprecated methods
Both these deprecated methods use eWAY's Transparent Redirect solution.
Rapid API Version 3
- For Rapid API Version 3.0, you need to have created an API key in your Eway Business Centre interface. See: Generating an API Key for Eway.
Rapid API Version 1.1
- This is the earliest Transparent Redirect solution.
To setup eWay Rapid API Version 1.1:
- Login as an Administrator
- Go to the Settings page
- Select the Orders tab
- Select the Credit Cards sub-tab
- Configure the following settings:
- C/Card Payment Provider: select eway rapid api
- Credit Card Capture Customer ID: enter your Customer ID (provided by eWAYEway)
- Retain Payment Provider Customer ID Token: check the box for customers to be able to choose whether their information will be stored in eWAY Eway and be available in future payments checks
eWay Billing Country: enter the relevant 2 letter country code, e.g., 'au' for Australia, 'nz' for New Zealand. A full list of available codes can be found here.
Warning The code must be entered in all lowercase letters.
...
title | Need assistance implementing this feature |
---|
...
.
Related
...
Help
Content by Label | ||||||||
---|---|---|---|---|---|---|---|---|
|
Content by Label | ||||||||
---|---|---|---|---|---|---|---|---|
|
...