|
Dan Noe
|
August 27, 2013 at 2:38 pm
I’ve searched this topic and followed instructions for various posts, but I’m having issues getting the Paypal Payments Pro option to work for a payment method. The error I’m getting is:
Attention: Your transaction was declined for the following reason(s):
Error Code: 10002
Short Message: Security error
Short Message: Security header is not valid
Severity Code: Error
I purchased an SSL certificate for the site. I also installed WordPress HTTPS (SSL) to force SSL on the Espresso_Events page, the Espresso_payments page as well as the Espresso_cancelled page. The site is still using a temporary URL. When I was issued the SSL certificate they required that I go to a Static IP. If I change the site URL and wordpress url to the new static ip I was issued it breaks the entire site. Likewise, if I go into the HTTPS plug-in and enter in the static IP in the SSL Host field it breaks the pages I’m performing the force SSL calls on.
One of the registration pages can be viewed here:
http://69.195.124.59/~iowasctp/shotgun-coach-education/iowa-dnr-basic-shotgun-coach-certification
The static IP I was given is: 173.254.106.100
-
This topic was modified 4 years, 8 months ago by
 Garth.
|
|
Josh
|
August 27, 2013 at 2:44 pm
The 10002 error only means 1 of 2 things.
- Your API credentials are invalid (extra spaces in any field make it invalid)
- You’re sending the request to the wrong server (where the API username you’re submitting does not exist)
Check your API Username, Password, and Signature for leading/trailing spaces
Check that your shopping cart does not have ‘test mode’ on, or ‘development mode’ or anything like that. It should be sending the API requests to .paypal.com if you’re using live credentials. (.sandbox.paypal.com if you’re using sandbox credentials)
You can actually use the PayPal Pro gateway without SSL for testing and configure SSL *after* the real domain goes live.
|
|
Dan Noe
|
August 27, 2013 at 3:23 pm
I turned off the sandbox mode and checked for leading/trailing spaces. Now when I try and enter in my sandbox credentials for testing I get this error upon submitting the form:
Attention: Your transaction was declined for the following reason(s):
Error Code: 15005
Short Message: Processor Decline
Short Message: This transaction cannot be processed.
Severity Code: Error
|
|
Josh
|
August 27, 2013 at 3:38 pm
If you’re using sandbox credentials then sandbox mode needs to be turned on.
|
|
Josh
|
August 28, 2013 at 8:05 am
Hi Dan,
I’m looking into this right now. If I don’t see anything configured incorrectly, is it okay to plug in a set of our own test credentials and run a test?
|
|
Dan Noe
|
August 28, 2013 at 8:38 am
Yes, please go ahead and test it.
|
|
Josh
|
August 28, 2013 at 8:55 am
I plugged in a set of PayPal Pro sandbox test credentials and the test payment was marked as complete. So the issue that you’re having with the 10002 error is either:
1) The PayPal Pro API credentials entered in Event Espresso>Payment settings are not correct
or
2) These are live PayPal Pro API credentials being used in sandbox mode.
What you’ll need to do is log into the PayPal Sandbox via your PayPal account and verify that the credentials you are using for testing are from the Sandbox account. Live PayPal Pro credentials will not work in sandbox mode.
As an aside, there was a lot of extra white space on the payment page due to the active WP theme’s custom content filters that are stripping out the WPautoP filter function. So I wrapped the [ESPRESSO_EVENTS] and [ESPRESSO_PAYMENTS] shortcodes with raw tags.
Which looks like this.
[raw][ESPRESSO_EVENTS][/raw]
So the payment pages look better now.
I also set the payment page and main registration page to not be forced as SSL for now. These should be set back to use SSL when the site goes live or when you’re on the real domain.
I will also advise to avoid using the WordPress HTTPs plugin to secure pages if you intend on using the JSON API and ticketing add-ons. In the past we would recommend using WordPress HTTPs (and still do in cases where ticketing is not installed). However, a recent update to WP HTTPs has caused conflicts with the JSON API when trying to log into the site. The Better WP Security plugin can be used for securing your WP pages where payment info is captured.
|
|
Dan Noe
|
August 28, 2013 at 9:52 am
I just verified the paypal sanbox API credentials and plugged those in. I left the sandbox mode on after my first test I got a new error code:
Attention: Your transaction was declined for the following reason(s):
Error Code: 10501
Short Message: Invalid Configuration
Short Message: This transaction cannot be processed due to an invalid merchant configuration.
Severity Code: Error
|
|
Dan Noe
|
August 28, 2013 at 10:02 am
It appears the paypal account isn’t verified yet. I’m working with my client to get the PayPal account verified so I can continue testing.
|
|
Josh
|
August 28, 2013 at 9:10 pm
Hi Dan,
Glad to hear you’re closer to getting this resolved.
|
|
Dan Noe
|
August 29, 2013 at 2:09 pm
Josh,
The account is now verified and it’s still failing. Here’s the error code I’m getting:
Error Code: 10501
Short Message: Invalid Configuration
Short Message: This transaction cannot be processed due to an invalid merchant configuration.
Severity Code: Error
Here’s a page with all of the events:
http://69.195.124.59/~iowasctp/shotgun-coach-education/nra-usa-shooting-civilian-marksmanship-program-level-i-coaches-course
Can you please advise me on what is going wrong. They’re supposed to push this site live next week.
|
|
Josh
|
August 29, 2013 at 2:22 pm
Hi Dan,
The Invalid Merchant Configuration error can be from one of two things according to the paypal api error codes
* Occurs when you have not agreed to the billing agreement.
* Occurs when the billing agreement is disabled or inactive.
In either case you will want to contact PayPal and ensure that your account is set up to process Website Payments Pro transactions and that the billing agreement is accepted. You can also search PayPal’s forums for information specific to this error code.
|
