For the first time, merchants in Australia, New Zealand and the United Kingdom can connect their websites to a single, global gateway. This means that our development partners need only integrate with eWAY once before they can start selling their carts and applications to international clients. Rapid 3.0 is a payment product that allows merchants to post credit card data from their customer’s browser directly to eWAY without it passing through the merchant’s server.
Beagle Alerts (powered by ReD)
Beagle Alerts is our most advanced fraud prevention product. Once enabled on an account, each transaction is checked against a global database of credit card transaction activity, providing the merchant with real-time recommendations to accept, challenge or deny each payment. A short questionnaire helps us create a rule profile which is tailored to the needs of the business. This service is provided by the world leaders in online payment risk management, ReD, which protected 17 billion transactions in 2011. No additional integration is required to use Beagle Alerts; the merchant simply activates it using MYeWAY.
Beagle (free) uses numerous external services to give you control over the payments made through your website, blocking or flagging high-risk transactions based on factors such as the location of the customers computer, country associated with the credit card, and their billing address. Note that Beagle (free) requires two specific fields to be passed; IPAddress and the Country field within the Customer element.
3-D Secure provides an additional layer of security by redirecting customers to a bank-hosted page which requests a PIN before processing a payment. This reduces the likelihood of fraud and reduces the liability of the merchant. If 3-D Secure is not enabled on the customer’s card, the transaction will be processed normally. No additional integration is required to use this solution, but it does need to be compatible with your Internet Merchant Facility. Rapid 3.0
Token Payments creates a unique Token ID for each customer when eWAY receives the billing details. This token refers to the customer and card data stored on eWAY,s PCI DSS compliant platform, and whenever you subsequently need to charge the customer, you can use this token instead of asking the cardholder to enter their details a second time. This solution is particularly useful when a repeat purchase is required or expected from the customer, such as with a subscription or payment plan. Supported technologies The following data interchange standards are supported by Rapid 3.0:
Simple Object Access Protocol is a protocol for invoking web service methods. It uses HTTP as its transfer layer and XML as its markup language. SOAP is an established protocol and most programming languages already have SOAP client classes available, which means that requests and responses do not have to be manually created or parsed.
Representational State Transfer is a model for invoking web services based solely on HTTP. It can access any information available using just a URL. REST’s simple structure makes application interoperability easier. REST is supported with both JSON and XML. Rapid 3.0 offers one integration to support payment processing in Australia, New Zealand and the UK, with support for payments in other countries coming soon. Rapid 3.0 also supports multi-currency processing provided the merchant account includes this functionality.
Rapid 3.0 supports both regular one-off payments, token payments, Beagle and Beagle Alerts. Additionally, merchants can create or update their token customers through Rapid 3.0 by sending the appropriate value in the initial request.
This method allows merchants to process payments in such a way that the customer remains on the merchant’s website at all times while processing occurs behind the scenes.
This method allows merchants to process payments using token customers they have stored with eWAY. Merchants can either load an existing token customer by passing in their TokenCustomerID in the initial request, or create a new token customer by leaving the TokenCustomerID field blank. Any values passed in the Customer part of the initial request will be used to either create or update the token customer, depending on the TokenCustomerID value. When loading an existing token customer, the customer’s details will be returned by eWAY, including the masked credit card details. The masked card can be sent back to eWAY when the payment is processed if the customer wants to process the payment using the card on file.
This method allows merchants to create token customers without processing a payment. This is a two-step process, requiring the customer’s details in the initial request, and then the card details in the form POST. This allows merchants to create new token customers without having to process card data themselves.
This method allows merchants to update existing token customers without processing a payment. Similar to the CreateTokenCustomer method, this is a two-step process with the customer’s details in the initial request, and then the card details in the form POST.