|
LJBSecurityTraining
|
July 2, 2019 at 1:51 pm
I set up Payeezy (first data) in EE3 payment methods; the payments go through, but there’s a problem with confirmation.
The relay response page that EE gives you doesn’t work for Payeezy, as per their customer support.
EE’s relay response on my site is [url]/?type=firstdata_e4&page_id=8459 which leads into a redirect to [url]/espresso-payments/?type=firstdata_e4 , and Payeezy needs a URL that doesn’t redirect.
When I skip the redirect and enter [url]/espresso-payments/?type=firstdata_e4 into the Payeezy payment page settings, the process breaks because then the URLs don’t match with what’s in EE.
Thoughts?
|
|
Josh
|
July 2, 2019 at 2:18 pm
The process shouldn’t break if you use the redirected URL. May I ask did you include https or does the espresso-payments page even use https?
|
|
LJBSecurityTraining
|
July 2, 2019 at 2:38 pm
When you say use the redirected URL you mean the final URL, right? We tried it with Payeezy support, didn’t work…
I did include https, that’s the URL the EE payeezy page gives.
|
|
Josh
|
July 2, 2019 at 2:50 pm
That’s correct, the final URL.
May I ask is the URL for the EE3 Thank You page publicly accessible, or do you need to be logged into the site to view it?
|
|
LJBSecurityTraining
|
July 2, 2019 at 3:06 pm
It’s publicly accessible, tested in incognito window. I could send you the URL, just don’t want to expose our dev site publicly for now.
|
|
Josh
|
July 2, 2019 at 3:42 pm
If you check the box next to “Set as private reply”, just before the “Submit” button, your next reply will be private.
|
|
LJBSecurityTraining
|
July 3, 2019 at 7:57 am
This reply has been marked as private.
|
|
Josh
|
July 3, 2019 at 9:31 am
There are a few issues on that page that will need to be fixed to allow everything to work as expected:
1) Two copies of the jQuery library. There should only be one.
2) JS errors. One of the errors will likely be fixed by fixing item 1. The other involves using jQuery in no-conflict mode. This is a screenshot of the source of the homepage that shows the problem:
https://slack-files.com/T02SY781D-FKXLFGPT3-0ca2847a43
You could change the $ to jQuery and that will fix the issue.
Other potential issues that may need to be addressed are the reCaptcha on the page. I don’t see a contact form or comment form on that page, so maybe you could remove reCaptcha from that page?
I may also help to exclude that page from caching.
|
|
LJBSecurityTraining
|
July 8, 2019 at 7:32 am
Thanks Josh, looks like the issue may be fixed!
|
