Hi, I’ve gone through all the documentation for the Payments Pro setup, and I can’t make a successful transaction in Sandbox mode. My client has Pro setup on their business setup, SSL certificate is installed, the 3 pages have been SSL forced to process the transaction.
I’ve used an old and a new sandbox api credentials, and then I realised that you use the card details in the debug mode. Problem is, the year is 2012, and the years start at 2013! Would this explain the error – 10002, and how do we fix it to get test payments working?
Paypal standard has worked in Testing.
Here’s the code for your test –
Payment for: Harrell, Sidney|| attendee_session id: 6os174qd14cd72lhgdo0jb4n17-5230e0077e0b54.06355195|| registration id: 17-5230e019bece0|| transaction details: a:28:{s:9:"TIMESTAMP";s:20:"2013-09-11T21:27:28Z";s:13:"CORRELATIONID";s:13:"3f950dca57921";s:3:"ACK";s:7:"Failure";s:7:"VERSION";s:4:"64.0";s:5:"BUILD";s:7:"7645184";s:12:"L_ERRORCODE0";s:5:"10002";s:15:"L_SHORTMESSAGE0";s:14:"Security error";s:14:"L_LONGMESSAGE0";s:28:"Security header is not valid";s:15:"L_SEVERITYCODE0";s:5:"Error";s:11:"set_verbose";s:1:"1";s:14:"set_verifypeer";s:1:"1";s:11:"set_timeout";s:1:"1";s:7:"set_url";s:1:"1";s:18:"set_returntransfer";s:1:"1";s:14:"set_postfields";s:1:"1";s:23:"curl_ver_version_number";s:6:"462597";s:12:"curl_ver_age";s:1:"2";s:17:"curl_ver_features";s:4:"1597";s:27:"curl_ver_ssl_version_number";s:1:"0";s:16:"curl_ver_version";s:6:"7.15.5";s:13:"curl_ver_host";s:21:"i686-redhat-linux-gnu";s:20:"curl_ver_ssl_version";s:15:" OpenSSL/0.9.8b";s:21:"curl_ver_libz_version";s:5:"1.2.3";s:18:"curl_ver_protocols";s:46:"tftp,ftp,telnet,dict,ldap,http,file,https,ftps";s:10:"curl_error";s:0:"";s:6:"ERRORS";a:1:{i:0;a:4:{s:11:"L_ERRORCODE";s:5:"10002";s:14:"L_SHORTMESSAGE";s:14:"Security error";s:13:"L_LONGMESSAGE";s:28:"Security header is not valid";s:14:"L_SEVERITYCODE";s:5:"Error";}}s:11:"REQUESTDATA";a:42:{s:4:"USER";s:27:"Michele_api1.frommycity.com";s:3:"PWD";s:16:"V4GLBG9KAKSW2SCX";s:7:"VERSION";s:4:"64.0";s:9:"SIGNATURE";s:56:"AFcWxV21C7fd0v3bYYYRCpSSRl31AedWGapw9eH7iPLZ.qgN7VWZs0TB";s:6:"METHOD";s:15:"DoDirectPayment";s:12:"BUTTONSOURCE";s:23:"AngellEYE_PHP_Class_DDP";s:13:"PAYMENTACTION";s:4:"Sale";s:9:"IPADDRESS";s:14:"72.209.212.203";s:16:"RETURNFMFDETAILS";s:1:"1";s:9:"STARTDATE";s:0:"";s:11:"ISSUENUMBER";s:0:"";s:10:"SALUTATION";s:0:"";s:9:"FIRSTNAME";s:6:"Sidney";s:10:"MIDDLENAME";s:0:"";s:8:"LASTNAME";s:7:"Harrell";s:6:"SUFFIX";s:0:"";s:6:"STREET";s:16:"401 Burnside Ave";s:7:"STREET2";s:0:"";s:4:"CITY";s:14:"Fredericksburg";s:5:"STATE";s:8:"Virginia";s:11:"COUNTRYCODE";s:2:"US";s:3:"ZIP";s:5:"22405";s:8:"PHONENUM";s:0:"";s:3:"AMT";s:5:"35.00";s:12:"CURRENCYCODE";s:3:"GBP";s:7:"ITEMAMT";s:0:"";s:11:"SHIPPINGAMT";s:0:"";s:11:"HANDLINGAMT";s:0:"";s:6:"TAXAMT";s:0:"";s:4:"DESC";s:18:"2Q13 Women Artists";s:6:"CUSTOM";s:0:"";s:6:"INVNUM";s:0:"";s:9:"NOTIFYURL";s:0:"";s:7:"L_NAME0";s:18:"2Q13 Women Artists";s:7:"L_DESC0";s:18:"2Q13 Women Artists";s:6:"L_AMT0";s:5:"35.00";s:9:"L_NUMBER0";s:0:"";s:6:"L_QTY0";s:1:"1";s:9:"L_TAXAMT0";s:0:"";s:17:"L_EBAYITEMNUMBER0";s:0:"";s:23:"L_EBAYITEMAUCTIONTXNID0";s:0:"";s:18:"L_EBAYITEMORDERID0";s:0:"";}s:11:"RAWRESPONSE";s:646:"TIMESTAMP=2013%2d09%2d11T21%3a27%3a28Z&CORRELATIONID=3f950dca57921&ACK=Failure&VERSION=64%2e0&BUILD=7645184&L_ERRORCODE0=10002&L_SHORTMESSAGE0=Security%20error&L_LONGMESSAGE0=Security%20header%20is%20not%20valid&L_SEVERITYCODE0=Error&set_verbose=1&set_verifypeer=1&set_timeout=1&set_url=1&set_returntransfer=1&set_postfields=1&curl_ver_version_number=462597&curl_ver_age=2&curl_ver_features=1597&curl_ver_ssl_version_number=0&curl_ver_version=7.15.5&curl_ver_host=i686-redhat-linux-gnu&curl_ver_ssl_version=+OpenSSL%2F0.9.8b&curl_ver_libz_version=1.2.3&curl_ver_protocols=tftp%2Cftp%2Ctelnet%2Cdict%2Cldap%2Chttp%2Cfile%2Chttps%2Cftps&curl_error=";}
1) Your API credentials are invalid (extra spaces in any field make it invalid)
2) You’re sending the request to the wrong server (where the API username you’re submitting does not exist). In this case it may be that the API credentials are for a live account but they’re being sent to the PayPal Sandbox server. You will need sandbox API credentials to test the sandbox.
You can check your API Username, Password, and Signature for leading/trailing spaces
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)
10501 Invalid Configuration This transaction cannot be processed due to an invalid merchant configuration. Occurs when the billing agreement is disabled or inactive.
I’ve used both my own sandbox development, and also created and used the api details now from my clients details to marry up the user.
Would you say this error is now to with the Paypal account? My client hasn’t got the billing agreement signed??
If you’re using a sandbox account when you see this error it means you need to enable Payments Pro in your sandbox account by logging in to your developer.paypal.com account:
Go to Applications -> Sandbox Accounts
Click the sandbox account you want to upgrade to Pro, and then click ‘profile’
There should be an Upgrade to Pro option in the dialog that pops up
Note the paypal developer website has been changing quite a bit recently, so your mileage may vary…
If you’re seeing this error in live mode, then you can contact PayPal support to find out what action needs to be taken to accept the billing agreement for this account.
The support post ‘Paypal Payments Pro – Sandbox mode’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.
Support forum for Event Espresso 3 and Event Espresso 4.