Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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


Note
  • This guide assumes that eWAY's services have been purchased and you have the relevant information required to set-up eWAY.
  • For Rapid API Version 3.0, you need to have created an API key in your eWAY Business Centre interface.

Payment Processing Overview

...

  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. They enter their card details and submit their order. 
  4. Commerce Vision does preliminary setup and checks, to:
    1. ensure the order is valid for submission
    2. set up payment information
    3. request an Access Code for the transaction from eWAY over a secure connection which needs to be posted with the card information.
  5. 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. Commerce Vision never handles or even sees the information at any point in the process.
  6. 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.

Step-by-step guide

...


Warning

CSS supports four eWAY versions:

  • Rapid API Version 1.1
  • Rapid API Version 3
  • eWAY Direct Connection API
  • eWAY Responsive Shared Page API

...