Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Elavon #15

Open
3dgroup opened this issue May 5, 2016 · 11 comments
Open

Elavon #15

3dgroup opened this issue May 5, 2016 · 11 comments

Comments

@3dgroup
Copy link

3dgroup commented May 5, 2016

Hey,
Elavon UK uses the Realex system, but your code only has a gateway url for payandshop. Do you think it would be better to clone your driver and replace the gateway url or can you change the code to allow the gateway(endpoint) to be changed.

@coatesap
Copy link

coatesap commented May 7, 2016

Hi, I actually did a extension of this driver to support Global Iris (https://github.com/coatesap/omnipay-global-iris), which also uses Realex. On reflection now though, it would be simpler to just allow the endpoint to be configured on the Realex driver, rather than creating completely separate packages that depend on it.
If you want to create a pull request for that change, I'll gladly merge it, and also ditch the Global Iris package.

@3dgroup
Copy link
Author

3dgroup commented May 11, 2016

I will try and find some time after i have completed the current section of my system. Did you know they also have sandbox URL's for the test environment? I think this could be implemented at the same time. I am not sure if Iris and payandshop also have the same sandbox link options? The sandbox URL are not in the Elavon UK documentation but their implementation team gave them to me.

@coatesap
Copy link

I wasn't aware that Realex had separate sandbox URLs. From memory, it's just the credentials supplied (merchantId, secret, etc) that determine whether the payment is treated as a test payment or not.

@3dgroup
Copy link
Author

3dgroup commented May 19, 2016

That's what I thought, but I have now been supplied with sandbox urls for testing and normal for live, but the full account is still currently in test mode. I will ask to see if the credentials change for the live server and confirm.

@3dgroup
Copy link
Author

3dgroup commented May 31, 2016

#16
Hopefully this has been implemented correctly for you

@slogsdon
Copy link
Contributor

To add some clarity (and to make sure this is documented here), Realex has separate URLs for live / sandbox environments for both API and HPP integrations. Here are the URLs:

API

Live URL - https://api.realexpayments.com/epage-remote.cgi
Sandbox URL - https://api.sandbox.realexpayments.com/epage-remote.cgi

HPP

Live URL - https://pay.realexpayments.com/pay
Sandbox URL - https://pay.sandbox.realexpayments.com/pay

The old URL that is used in this library (https://epage.payandshop.com/epage-remote.cgi) should still work today and point to the same live / sandbox environments based on account configuration, but as far as I'm told by my teammates in the Realex Dublin office, the URLs above should be used instead of the payandshop.com URL.

@3dgroup
Copy link
Author

3dgroup commented Dec 20, 2017

My fork allows you to provide the realex urls in the config which will overrive the payandshop urls. I use elavon URL's which uses the realex system. I would use the realex URL's.

@lewisvgd
Copy link
Contributor

This functionality is useful - Any news on the merge?

@coatesap
Copy link

@lewisvgd - agreed - this looks very useful. Are you able to address the comments in the PR review if @3dgroup are now using their own fork?

@3dgroup
Copy link
Author

3dgroup commented Apr 16, 2018

@coatesap everything is working on my fork with Realex/Elavon. I am using it on two different applications. I can look at the fork conflict so the merge can happen.

@coatesap
Copy link

@3dgroup - great, thank you. I'm keen to get it merged. I may release it with a new major version number, to avoid issues with the Global Iris driver which extends it. That can then be updated separately to benefit from the ability to set the endpoints (which I think is basically all it does anyway).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants