|
Stefanie Goldstein
|
March 30, 2015 at 7:31 pm
I have switched from Quickbooks to PayPal Pro (at some expense to my client) because of problems connecting.
NOW. I have set up PayPal Pro in the payment settings with the correct API information and yet I get an 10002 – Security header is not valid error.
I have double checked my API Username, Password, and Signature for accuracy and leading/trailing spaces.
I and PayPal support have checked that our shopping cart does not have ‘test mode’ on, or ‘development mode’ or anything like that.
I have made sure that the Sandbox log in name is different from the main account login.
His account has been verified and is ready to go.
We don’t have a dedicated IP address or private SSL so I have unchecked “use https” in the Event Espresso interface for PayPal Pro.
Still….no way for customers to pay for services and we have just announced new programs for them. My client is very upset with me.
Can you help???
|
|
Lorenzo Orlando Caum
|
March 30, 2015 at 8:03 pm
Hi!
When you made this switch, did you register for a PayPal Pro merchant account?
This question isn’t meant to be confusing. PayPal uses similar API credentials for PayPal Express as for PayPal Pro.
A business or premier account has access to PayPal Express automatically. However, PayPal Pro requires additional setup and a billing agreement for American Express. It is not automatically included with business or premier accounts with PayPal.
—
Lorenzo
|
|
Stefanie Goldstein
|
March 30, 2015 at 8:24 pm
I’m sure it’s PayPal Pro.
|
|
Stefanie Goldstein
|
March 30, 2015 at 8:31 pm
I meant to say, yes, it’s a PayPal Pro merchant account with Payflow and access to PayPal Manager.
|
|
Stefanie Goldstein
|
March 30, 2015 at 9:55 pm
Is this something that I need to do? What would I enter in the Third Party Permission Username field?
|
|
Tony
|
March 31, 2015 at 3:55 am
Hi Stefanie,
No you do not need to enter 3rd party permissions.
10002 – Security header is not valid error.
Happens for 2 reasons:
1) Incorrect credentials ( usually leading/trailing spaces which I see you have checked for)
2) Wrong endpoint, using a sandbox account on live or a live account on sandbox.
So just to confirm, are you logging into https://www.sandbox.paypal.com/ or https://www.paypal.com/
This issue appears very similar to the issue you were having with QuickBooks which was Authentication failure, so I’m wondering if something on the server is altering the request somehow.
Do you have a test event I can run a registration on?
|
|
Stefanie Goldstein
|
March 31, 2015 at 11:27 pm
Ah… PayPal gives you a Certificate number rather than a signature id. You have to remove the Certificate and then you get the signature. Finally! Thank you for your quick attention to this matter.
|
|
Tony
|
April 1, 2015 at 4:04 am
Thank you for letting us know, I’m glad it now working for you.
Have a great day 🙂
|
