Paypal is a joke..
So for a client we integrated with the Website Payments Pro, using the NVP API and using the API Signature method. Now if you don't know exactly what those services/api's are, it doesn't really matter, you should still get a chuckle out of this story.
So we integrated it with the sandbox and everything worked fine.
We obtained the 'live' api credentials and slapped them into our configuration file. We then ran a test. The results we got back were: 'Security header is not valid'
Now none of the code was changed except our configuration which we copy and pasted from Paypal's site. So confused as why this wasn't working we called their tech support (had a number for the account rep), explained the situation and he said he'd put in a ticket.
So late the next day we finally hear from their support guy, and what he told me cracked me up. I tried not to laugh at him when he told me what to do:
So I tried it, and after generating the 4th credential it still didn't work (imagine that).
I called him back letting him know it didn't work, he said email me your request and I'll take a look at it.
I emailed him the curl request I was using and this was his email back:
I did a test on the new API credentials and get the same error. I recommend that you create a few more and let me know if you’re still getting the error.
Regards,
XXX XXXXXX
Merchant Technical Services Integration
So it's still not working, but at least I have a funny story out of it.

9 comments to "Paypal - Security header is not valid - Website Payments Pro"
You indicated that I was simply using the wrong credentials in the wrong place.. wouldn't you think their support would have picked up on that instead of giving me some ridiculous advice? I would hope so, and if not, that strengthens my case.
Would you not agree?
I'm glad your credentials worked for you, and you had no issues, congratulations.
Leave a Comment