Rapid 3.0 offers complete control over the look and feel of your payment pages while reducing the merchant's scope for PCI DSS compliance. For enhanced security, you can POST credit card data directly from the customer's web browser to eWAY, bypassing the merchant's website.
Download the security review of Rapid 3.0 from BAE Systems Stratsec, an external qualified security assessor (QSA).
Linking to eWAY
Sample code is available from within MYeWAY, along with many other resources for our development partners. Register for free today!
Follow our Help Desk article on how to create your sandbox API key and password - KB 22370486
Beagle (free) and Beagle Alerts Integration
Payments sent through Rapid 3.0 will pass through the Beagle system, and for those with the service enabled, also through the Beagle Alerts system (powered by ReD).
Using ReD's vast neural network of transaction data from around the globe allows eWAY to validate the transaction against a broad range of risk factors.
Token Payments Integration
Rapid 3.0 is also integrated into our Token Payments solution, allowing you to save your customers payment information for use on any future purchases. Through Token Payments, you can Create Tokens, update Tokens, and Process Payments for existing tokens.
Single Endpoint
Rapid 3.0 provides a single end point for all countries where eWAY processes payments. This means if you expand your business beyond Australia, the integration will be exactly the same.
eWAY uses a complex DNS technology to ensure your payment is routed to the correct country.
Available methods
- Process Payment – the transaction is processed immediately and confirmation is sent to your site
- Token Payment – the transaction is processed or stored for processing later, and the billing details are saved within eWAY so the customer can make future purchases from your site without having to re-enter their credit card number
- Create Token customer – create a token customer, which will store the customer and card details on eWAY's secure PCI-DSS compliant platform for future payments
- Update Token customer – the current transaction overwrites the details of an existing Token customer
To call the above methods, several fields will need to be specified in the transaction request.