Setting up Global Payments (formally Realex) or Elavon

Global Payments (formally Realex's) & Elavon integration provides 2 options:

1. HPP using Full Page Redirect - where the user is taken to a different page to enter their credit card details 
2. HPP using an iFrame - similar to above except the user thinks they are still on your website (as the user enters their credit card details on Realex's servers but it uses an invisible iFrame in the middle of the page to host the credit card screen)

Global Payments claim that both options are fully PCI Compliant as the user enters their credit card details on their servers.

To switch on either option only takes a minute so you can try out both options.

OPTION 1: HPP using Full Page Redirect

This option seems to be more stable than option 2 as option 2 uses iFrames and there seems to be issues with iFrames and the iOS operating system where on rare occasions, the customer is charged but their order does not complete.

Note that some of our customers have used OPTION 2 below without any issues while others have had issues.  Our current suspicion is that customers without Nosto don't seem to have any issues while the customers with Nosto do - and we think it's because Nosto has automatic pop-ups for users leaving the checkout without completing their order as well as other javascript code that Nosto runs, which may be interfering with Reealex's iframe code.

NOTE that if you move to this from OPTION 2 below, you need to remove the fallback response set up for option 2 - as sometimes this causes an issue with 3D secure orders.  So just send a similar email to below but requesting that the response url is removed this time.

OPTION 2: HPP using an iFrame

This is the nicer looking option but is not fully stable.  On rare occasions, the customer can pay but their order does not complete successfully due to issues with iFrames and certain mobiles, so if using this option, you need to set up a validation check on each payment that is made so that if the order is not completed, you get an alert on your dashboard which should cover as a backup solution (which is not 100% secure either but is a large improvement).

To do this, send the following email to Global Payments or Elavon technical support and substitute the parts in bold:

"Hi,

We are using HPP using an iFrame - so please set up a fallback response, where you trigger your system to always post the response independently of the iFrame to the following url:

https://www.yourdomainname.com/realexval

Regards,

Your Name" 

Note that until you set up the above, the following alert will appear on your dashboard.  And also, when it is set up, this alert only disappears when the first order goes through.

A second issue with Realex / Global Payments with OPTION 2 above

There is a second issue with Global Payments when Realex notify us that a customer has paid but the information on our system is different from their system.  In 99% of these cases, the order is a valid order so we send you an email and let the order through telling you to double-check this order.  The most common reason for this is often that a mobile phone user's browser refreshes the page with the credit card details twice without you knowing so we generate 2 order numbers for the transaction and Realex/Global Payments have one order number and we have the other order number - and in this case, all order details are the same on both systems except the order number is out by 1.

Option to SAVE CREDIT CARDS

You can turn on the ability for your customers to save their credit card details if they have an account with you. 

If you wish to activate this feature on your site please take the following steps:

• Contact Realex to enable the auto saving of credit cards on your Realex account
• Once this is activated, contact the Magico Help Desk to activate the feature on your live site. 

The following screen shows an example of a customer who has 2 saved credit cards on their account: