Realex – Your transaction has been successful but there was a problem connecting back to the merchant’s web site

If your are trying to get realex e-payment integration working on your website and are getting the following message at the end of the realex redirect process:


Your transaction has been successful but there was a problem connecting back to the merchant’s web site. Please contact the merchant and advise them that you received this error message. Thank you.


Then the good news is that most of you integration is working and its just the very last step that’s failing, this means that you have sent to Realex correct values for: Merchant Id, Shared Secret, Account Id, Request URL etc. etc.


Now, nine times out of ten the above error is caused by a badly configured Return or Callback URL, this is a URL that you must tell Realex about by phone or email, Realex redirects back to this URL once the transaction is complete. So there are 3 possibilities why the redirect is failing:


1.) You haven’t yet told Realex what your return URL is. You need to find out what the URL should be and let Realex know, phoning them is often the most efficient route. The URL will depend on which CMS you are using etc. Ask Google for hints.


In ubercat you can get the URL by going to the Realex settings page (Store administration / Configuration / Payment settings / Overview / Payment Methods / Credit Card [realex] settings) and copying the URL from the ‘Realex Callback Page:’ field.


Details about the Magento return URL can be found here.


2.) You have told realex what the URL is but they forgot to configure your account or made a mistake while configuring it – this happens more often than you might think, phone up Realex and get them to confirm that the return URL is set correctly – double check the configured URL it in detail! Do you need to add or remove the www.?


Hopefully it is only a matter of short time before you get everything working as it should!

2 replies
  1. Dev
    Dev says:

    I am getting this error alert in onepage checkout

    This transaction XXXXXXX has already been processed! If you feel this is incorrect please contact the merchant

  2. Dimiona
    Dimiona says:

    In our case, when we switched to https, the payment didn’t work anymore and users got the error message you mentioned in the second paragraph. After four hours of debugging on our server, it turned out that Realex ONLY WORKS/HANDLE with TLS1.0 protocol. Our server handled only TLS1.1 and TLS1.2. When we enabled TLS1.0 and did another try on payment it finally worked!

    What was the worst thing in this nightmare?
    – Realex never returned any useful information why the redirection fails. We were in continuous contact with Realex via Email, but they can only refer to their error code which was useless for us. Realex Supports tried to clarify the Referring and Redirection URL that they are correct, or not. Over and over again. We knew that those urls are correct, because they are worked well on our demo and staging sites where we use http.
    All in all, it would have been nice that Realex would have sent a more accurate error, to be precise, “Sorry, we are unable to establish connection with your server. Reason: TLS connection failed” or something similar.

    What was good?
    – Their support team were available and we always got answers within minutes (via email), so we did not feel we are alone in this situation.

    To sum it up, if you use Realex with HTTPS, check your server supports TLS1.0 protocol. Hope it helps, too.

Comments are closed.