|
Debra McElroy
|
August 16, 2013 at 9:47 am
When I input my PayTrace username and pw, I get an error message that says: “Attention: A valid SSL Certificate is required on your website in order to process payments using this gateway!” I thought SSL is part of why one uses PayTrace.
Would it be the same with Authorize.net?
[It would be good, EE, if you spelled this out clearly somewhere on your sales pages, so the client knows all their expenses up front. I (the developer) hate having to tell my nonprofit client there are yet more expenses after they’ve already purchased their license.]
|
|
Debra McElroy
|
August 16, 2013 at 9:48 am
Also, I’m getting this error message at the top of the page. Are they related?
Warning: file_get_contents(/home/northrid/public_html/wp/wp-content/plugins/event-espresso/gateways/atos/default/pathfile) [function.file-get-contents]: failed to open stream: No such file or directory in /home/northrid/public_html/wp/wp-content/plugins/event-espresso/gateways/atos/settings.php on line 75
Warning: file_put_contents(/home/northrid/public_html/wp/wp-content/plugins/event-espresso/gateways/atos/default/pathfile) [function.file-put-contents]: failed to open stream: Permission denied in /home/northrid/public_html/wp/wp-content/plugins/event-espresso/gateways/atos/settings.php on line 117
|
|
Josh
|
August 16, 2013 at 3:07 pm
With SSL and PayTrace: The customer does not get redirected to the secure page at Paytrace.com where they would enter credit card information, they stay on your site and enter their payment information. That’s why it needs to be secured. You can get free SSL certificates from startssl.com if the client’s budget dictates a lower cost option.
We try to spell this out clearly on our sales page:
https://eventespresso.com/features/payment-options/
In a nutshell it explains that if the payment is taken on your site (ie. On-site) an SSL certificate is required. PayTrace is labeled as an on-site option.
The atos errors that you are seeing should go away after deactivating/reactivating one of the other gateways.
|
|
Debra McElroy
|
August 16, 2013 at 6:44 pm
Re: spelling things out… Ah! So you did. My mistake.
If I may, I suggest a “don’t make me think” improvement: Create two different lists w/ headings; one for the gateways that require a SSL and one for the gateways that don’t.
Thanks for the help. 🙂
|
|
Debra McElroy
|
August 20, 2013 at 11:20 am
I’ve gone back and looked at the page more closely, and I hope you might be willing to heed this usability advice.
The way you’ve conveyed the info on this page assumes that every user will read every word of every paragraph. Many or most users (myself included) will skim the page, see this at the top of the page:
“Collect Payments
Integration with 30+ payment gateways allow you to collect money…”
…then jump down to the array of logos, see the one or two they’re wondering about and if they find them, think “Okay, great! That’ll work.”
The last line of text under each logo saying “On-site” or “Off-site” is not sufficient. It’s too easy to overlook, and doesn’t speak the lingo of the noobie user.
My suggestion: create two subheads…
1. These payment gateways are all-inclusive; you will not need a separate SSL certificate to use them.
2. These payment gateways require the separate purchase of an SSL certificate.
This is a simple change, and would greatly improve the clarity of the information.
|
