HI,
I'm just testing the Paypal standard plugin, but the CC keeps reporting as invalid. Can you please help me out? Have I done everything correctly?
This is the link. Password is [removed - see Chris Hajer]
HI,
I'm just testing the Paypal standard plugin, but the CC keeps reporting as invalid. Can you please help me out? Have I done everything correctly?
This is the link. Password is [removed - see Chris Hajer]
I just tested using Firefox and I made it to PayPal. Screenshot: http://minus.com/m8L8t1GT6/1g
The test credit card number you posted IS invalid and is flagged as such:
http://creditcardity.com/?number=1234123412341234
The test number I was using is VALID and worked fine:
http://creditcardity.com/?number=6011000990139424
Are you testing with a valid number and it's being flagged as invalid?
I thought it said not to use a valid number? So if I put my real CC in there, there will be no payment actually made?
Also how do I add GST and AU$?
Thanks.
Please begin a new topic for your GST and AU$ question as it is unrelated.
You should NOT use a valid credit card, because the page is not secured. The information could be intercepted. However, you need to use a card which appears to be valid, at least mathematically, so you can test your form. Here are some sources of mathematically valid credit cards:
http://www.paypalobjects.com/en_US/vhelp/paypalmanager_help/credit_card_numbers.htm
http://www.merchantplus.com/merchant-resources/credit-card-test-numbers/
You can use those for testing.
Before your form goes live and you start accepting credit cards, you need to secure your page with an SSL certificate, and ensure the URL use SSL/HTTPS. There are WordPress plugins to force SSL in your installation. Here is one such plugin: http://wordpress.org/extend/plugins/wordpress-https/
Have I done this correctly? http://cl.ly/image/2E113W1c3h1O
When I add the shop URL to either the URL filters section or if I tick the "secure post" option when editing the actual page, I get this result:
http://cl.ly/image/0F1G0h271a18
For the record I tested with password protected page and without.
@Jane, I'm not familiar with the plugin enough to say if it's set up correctly or not. I would suggest that you contact that plugin author for their support.
However, in your first screenshot, it appears to me that the domain name should not be there. That box appears to allow you to secure all pages that are sub-pages of a specific URL. I don't think you need that, because you do not (I don't think) have any sub-pages of /registration to be protected. This would be for stores where you have URLs like
/store/clothing/
/store/clothing/mens
/store/shoes/
/store/shoes/childrens/
In that case, everything beneath "store" needs to be protected with SSL. In that case, this box would contain ONLY /store/ on one line, and all the pages I listed above would be protected. You're not trying to do that. You want to force SSL on the registration page only. In that case, I believe there is a 'secure post' on the WordPress page "Registration" to force SSL for the one page only.
It's possible the error in the second screenshot is related to the configuration. I would remove everything you entered in the URL Filters box, and then just secure the one page by ticking the 'secure post' box for that page. However, I've never used that plugin to know if my understanding is correct.
Please let me know if that helps.
Chris it's best if I give you the login details privately. Could you please tell me how to do that?
Or please email [email protected] - login here: http://eccellenvironmental.com/wp-admin/
This is the shopping cart https://eccellenvironmental.com/registration/ Have done as you suggested only 'secure post' is ticked, still no joy.
Otherwise which plugin do you suggest? I thought I used the recommended one...
Thanks.
Please send the details via email to [email protected] - thank you.
Jane - are you using the PayPal standard plugin for an australian site ? If so you don't have the credit card field on your form. Cc details are entered on a PayPal checkout page hosted by PayPal.
If you want to use the PayPal pro version (so customers don't leave your site and enter their cc details on your form) you need to have a bank account in another county (eg America) as the last time I looked at all of this Australian PayPal customers could only use PayPal hosted payments.
Does your site have an ssl certificate ? It looks like a lot of those errors are due to no ssl cert or ssl cert configuration problems perhaps. You don't need an ssl cert to use PayPal standard payments anyway as they take the credit card details on their system.
Have you checked the PayPal end of things as I think you can do gst there and definitely currency is set like $au and it sends invoices for you etc.
Depending on your needs you can also look at the gravity forms eway plugin (free). I find it works great.
Jane, replying to this response from you:
I did everything I could think of with the plugin, and I don't think it has anything to do with your problem. I would contact your host and ask for their assistance. I can reproduce the error even on pages that are NOT secured by the plugin, which leads me to believe it's Not the plugin at all.
Can you contact them and explain the error and see if there is additional configuration that needs to be done?
Additionally, I found this advice online:
http://support.servertastic.com/error-code-ssl-error-rx-record-too-long/
Thanks for all the help Chris, do I need to do anything else to the form/page to make it live? Or is it all working that you can tell?
I did not have any of the previous issues when submitting the form this time. The form was accessible only via https.
However, after I entered my credit card information, I thought the card would be processed (or return an error, since it was a valid looking card, but not a real card) but after a couple seconds I was directed to PayPal. Did you have have PayPal standard active at some point? My expectation was that the whole transaction would take place on your site, which was the whole reason for the SSL cert in the first place.
I chose to go with the free version, so a paypal signup will be required I realise. Because we don't know if online payment is worth it, I didn't want to go all out with Pro just yet.
This is how I set it up... http://cl.ly/image/0T310f1L0625
Does this mean something's wrong with Paypal?
What free version are you talking about?
If you are using PayPal Payments Standard Add-On (here) then you do not need an SSL cert at all. All the payment processing is done off your site, at PayPal. There is no need to add a credit card field to your form, as the credit card data is collected by PayPal.
I'm sorry I misunderstood you originally regarding the add-on you were using and the credit card fields you had added to your form. With the PayPal Payments Standard add-on, do not add a credit card field to your form.