This is the same problem as Error 0x1408F10B: “SSL3_GET_RECORD:wrong version number” with PayPal SDK The version of PayPal API we are using hard codes CURLOPT_SSLVERSION to 3. Our fix is to insert this before any PayPal calls. PPHttpConfig::$DEFAULT_CURL_OPTS[CURLOPT_SSLVERSION] = 4;
You need the scope https://uri.paypal.com/services/reporting/search/read .. if it’s not there in the oauth2 response, double check your REST App’s permissions. Refreshing an access token Existing access tokens are cached for 9 hours–so if you already requested an API token and then just added this permission to your app, it can take up to 9 hours … Read more
I was looking for the same issue, here’s what is working for me. Tested in ‘sandbox’ mode and using NVP (instead of SOAP). Your server must support CURL, in order to verify it use: <?php echo ‘curl extension/module loaded/installed: ‘; echo ( !extension_loaded(‘curl’)) ? ‘no’ : ‘yes’; echo “<br />\n”; phpinfo(INFO_MODULES); // just to be … Read more
Try add CURLOPT_SSL_CIPHER_LIST => ‘TLSv1’ to your PPHttpConfig.php file. I had the same issue with you and spent hours to find the solution. This worked for me.
I’m using VS 2008 with .net 3.5.30729.4926. All I had to do was: Add imports: Imports System.Security.Authentication Imports System.Net Add this to my code (C#): public const SslProtocols _Tls12 = (SslProtocols)0x00000C00; public const SecurityProtocolType Tls12 = (SecurityProtocolType)_Tls12; ServicePointManager.SecurityProtocol = Tls12; VB.net version: Const _Tls12 As SslProtocols = DirectCast(&HC00, SslProtocols) Const Tls12 As SecurityProtocolType = DirectCast(_Tls12, … Read more
That’s because Express Checkout and Website Payments Standard are fundamentally different products. To use Express Checkout, you would call the SetExpressCheckout API. In the API call, you specify the details of the products, amounts, and the RETURNURL. Once you post this data to PayPal’s API endpoint, you receive a token in return. You would then … Read more
I just ran into this same problem in my testing environment as well (luckily my live payments are going through). I fixed it by changing: public PayPalAPI(string specialAccount = “”) { System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls; to public PayPalAPI(string specialAccount = “”) { System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12; They disabled support for SSL3 a while ago: https://www.paypal.com/uk/webapps/mpp/ssl-security-update, specifically stating … Read more
Edit: Now that I can see the array you’ve outputted, try replacing this to get rid of the PHP array error: foreach ($_POST as $key => $value) { if (!is_array($value)) { $value = urlencode(stripslashes($value)); $req .= “&$key=$value”; } else if (is_array($value)) { $paymentArray = explode(‘ ‘, $value[0]); $paymentCurrency = urlencode(stripslashes($paymentArray[0])); $paymentGross = urlencode(stripslashes($paymentArray[1])); $req .= … Read more
The Security header is not valid error is only caused for two reasons: Wrong credentials Make sure that you’ve put your API Username, API Password and API Signature correctly. Sometimes it happens that during copy and paste there is accidently a space added, this would trigger this error. Doublecheck this settings in the SDK or … Read more
So, it looks like I’ve found possible answer while combining JAX-WS & JAXB related answers from SO (I would really appreciate if somebody experienced in these technologies can check whether following is correct): The obvious thing for me is to add SOAP message handler and alter header of SOAPMessage instance in it: import javax.xml.ws.Binding; import … Read more