First off. I want to make clear that even though I messed around with the certificate method I was never going to get anywhere because I had already setup API credentials back in 2007 using the signature method so therefore any cert I downloaded was incomplete with no key information and just overall an invalid pem file. In order to use the certificate method I believe I would have to delete my API credentials and start over selecting the certificate method. I could not do this because I have other stores running on CRELoaded that can only use the signature method.
So, the signature method now works perfectly. Here’s how this went down.
When trying my signature method using my old tried and proven API credentials from PayPal I receive this error in the logs (I’m not pasting all of the post data from the logs but only the final error):
[quote]Response: HTTPS: libcurl error(35): error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure[/quote]The response from the help desk was this:
[quote]It is a well-known problem in standard CS-Cart. In order to fix it you should replace the “paypal_pro.php” file located in the “payments” directory of your CS-Cart instalaltion with the file attached to this message. Please check it and let us know the result.
Thank you.
—
Sincerely yours
Pavel Zyukin,
Technical support engineer
[/quote]The file he had attached (which I will post a difference in just a minute) worked perfectly. I am appreciative of their quick help but had to take a bit of exception with the ‘well known’ remark as a couple of the ‘veteran’ users above didn’t have an answer … well, just read my response:
[quote] Ok… the new file you gave me works perfectly. Thank you for your help.
Now… not to be combative but I spent HOURS searching the forums, KB and Google and never found an answer to this so I might have to take exception to the ‘well known’ remark. I posted to the forum at the link in this ticket with a few veteran forum users responding but no solution. You can bet I’ll post the solution now.
Also, I had just downloaded this 2.0.12 on Feb 12 so it’s not like it’s an old installation.
Where would I find reference to this problem so maybe I can help myself better in the future?
Again, I appreciate your help.
[/quote]So, anyway, it’s fixed. But my problem is as I stated above. My install was only a few weeks old and I couldn’t find the solution to this on my own and it sure wasn’t from a lack of trying. Thus endeth the whining…
So what was changed?
Lines 67-82 of the new /payments/paypal_pro.php file are:
Actually less coding. This dovetails nicely with the little information I could find on the PayPal dev forums but was quite frankly over my head to correct on my own.
Any way. Hope this might help someone. If I could attach a file here I would. Maybe I’ll copy paste the file in full in the next post.
Here’s the full paypal_pro.php file that support provided me to fix this problem. Notice that it has no date within the file in the //$Id$ line like the old file which said:
Hopefully, you are getting the paypal_pro.php that will be part of 2.0.13 - it sounds like they recently fixed the problem but did not circulate their solution.
[quote name=‘indy0077’]If you do use this method as in the screen shots then it works fine with CSC.[/QUOTE]
you say “this” method, as in one, but you have 2 screen shots, one showing using a certificate, and the other screen shot shows using a signature method. this confuses me.
[quote name=‘norm111’]you say “this” method, as in one, but you have 2 screen shots, one showing using a certificate, and the other screen shot shows using a signature method. this confuses me.
its one or the other , no?[/quote]
It’s still the same, just second one shows up after you will click on the link below.
I got PayPal pro to work like a charm in cs-cart 2.0.14
My situation:
using certificate method, certificate obtained from PayPal and uploaded to site in payments/certificates/ folder. its called cert_key_pem.txt
im using the api username and the password given by PayPal api process.
orders are processed and payments from users credit cards go straight to PayPal. it appears like you are using a credit card merchant account. seamless.
now question is client is currently not using a SSL certificate being under impression that as it goes to PayPal it is encrypted prior to sending. is this true? is date safe for all intensive purposes?
also, i don’t like the fact that the cart saves the credit card info in the order section. although it comes in handy if you have to resend the order or something.
what is best way to prevent cards numbers being saved again?
If you do not want the credit card information saved, check "Remove CC info’ for each order status that should not save this information. For instance, if an order is in ‘Processed’ status (payment already made), there is no need to have the CC info.
[QUOTE]now question is client is currently not using a SSL certificate being under impression that as it goes to PayPal it is encrypted prior to sending. is this true? is date safe for all intensive purposes?[/QUOTE]
No… They need to invest in an SSL cert!
You claim you are using Paypal Payments Pro which is essentially a credit card payment gateway. Your customer is referring to traditional Paypal payments of which the customer is sent to Paypals site to complete the payment transaction, and then returned (hopefully) back to your site.
OK the problem was that I had been over-zealous in my pursuit of PCI compliance and had selected “Remove CC Info” for the “Open” order status. This meant that the credit card information supplied by the customer was being passed to the payment processor as “XXXX” thus causing the error.
Just thought I would post this for anyone experiencing the “mismatch in element 'ExpMonth” error.
This problem is recurring intermittently. I just lost a $100 order from a very frustrated customer. I have no idea how to fix this. This is the second customer in three days that has not been able to place an order because of this error.