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 and . It conforms to PSI DSS (Payment Card Industry Data Security Standard)

...

The process that a payment using eWAY goes through can be briefly stated outlined as follows:

  1. The user

...

  1. builds an order and

...

  1. goes through checkout.
  2. They select credit card as their payment

...

  1. option, and assuming eWAY is configured

...

  1. , they will be presented with

...

  1. credit card input fields. They enter details and submit their order
  2. We do

...

  1. preliminary setup and checks such as

...

  1. :
    1. Ensure the order is valid for submission

...

    1. Set up payment information
    2. Request an Access Code for the transaction from eWAY over a secure connection which needs to be posted with the card information.
  1. Once our checks and

...

  1. set up 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 and we never

...

  1. handle or even see the information at any point in the process.
  2. eWAY processes the payment and then redirects the user to our return page which finalizes their order and

...

  1. triggers the

...

  1. appropriate Success or Fail

...

  1. page to be displayed.

Step-by-step guide

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

...

Content by Label
showSpace
showLabelsfalse
max5
spacesDRAFT
showSpacefalse
sortmodified
falsereversetrue
typepage
cqllabel in ("payment","orders") and type = "page" and space = "KB"
labelspayment orders