...
CSS supports four eWAY Rapid API methods:
- Rapid API Version 1.1
- Rapid API Version 3
- eWAY Direct Connection API / using Secured Fields
- eWAY Responsive Shared Page API
- Rapid API Version 1.1
- Rapid API Version 3
For more information on eWAY's payment solutions, refer to their website.
...
- A 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.
- They enter their card details and submit their order.
- Depending on which method is used, Commerce Vision does preliminary setup and checks, such as:
- ensure the order is valid for submission
- set up payment information
- request an Access Code for the transaction from eWAY over a secure connection which needs to be posted with the card information.
- Once our checks and set ups are done, we post/submit the page (including the credit card information and the Access Code) on behalf of the user directly to eWAY's servers. Their credit card information goes directly to eWAY. check? Commerce Vision never handles or even sees the information at any point in the process.
- 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.
Note | ||
---|---|---|
| ||
Please contact Commerce Vision for assistance implementing this functionality. |
Step-by-step guide
Note |
---|
|
...
Direct Connection API involves a simple, single server side call to process a transaction. In CSS, it is implemented with eWAY's Secure Secured Fields. This i nserts 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
...
Instead, when the buyer clicks 'Process Payment', they will see a popup box window for entering credit card information from eWAY.
...
Once payment is processed, the box window closes and the buyer will be taken to your site's Order Confirmation page.
...
Info | ||
---|---|---|
| ||
If using eWAY Responsive Shared Page:
|
Rapid API Version 3
This method keeps customers on your website as well as having the security of keeping card data off your own systems by eWAY's Transparent Redirect.
- 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
[ intro]
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 eWAY)
- Retain Payment Provider Customer ID Token: check the box for customers to be able to choose whether their information will be stored in 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 | ||||||
---|---|---|---|---|---|---|
|
...