I spent the last few days researching this problem to no avail. I found many similar problems, but none that exactly address my issue. I am attempting to integrate Payflow Pro with transparent redirect, but cannot successfully complete a transaction. I am using the test environment with a test Payflow Gateway account. I can successfully retrieve a secure token by posting the following from my test server to https://pilot-payflowpro.paypal.com: PARTNER=[hidden]&VENDOR=[hidden]&USER=[hidden]&PWD=[hidden]&TRXTYPE=S&TENDER=C&CREATESECURETOKEN=Y&SECURETOKENID=[hidden]&URLMETHOD=POST&SILENTTRAN=TRUE&AMT=2&BILLTOFIRSTNAME=John&BILLTOLASTNAME=Doe&BILLTOADDRESS=123TestDr.&BILLTOCITY=Testcity&BILLTOSTATE=TN&BILLTOZIP=55511&BILLTOEMAIL=[test email address]&USER1=3&USER2=&USER3=0&USER4=2 to which I receive the following response: RESULT=0&SECURETOKEN=[hidden]&SECURETOKENID=[hidden]&RESPMSG=Approved NOTE: I have configured a Return URL using PayPal Manager, which is why RETURNURL is not included in the secure token request. However, I also have tried with RETURNURL specified, and I have obtained the same end result. I use the results from the secure token request to create a cc collection form. I input test credit card details using acct# 510 etc (can't post full test number since the community will not allow it??), then post the following from the browser directly to https://pilot-payflowlink.paypal.com: fund_id=3&ACCT=[test account #]&CVV2=555&EXPMONTH=01&EXPYEAR=20&EXPDATE=0120&SECURETOKENID=[hidden]&SECURETOKEN=[hidden]&feeTokenID=[hidden]&feeToken=[hidden] The response is properly redirected to the Hosted Page error URL I have specified in my Payflow Manager Service Settings. My problem is that I do not understand why it is redirecting to the error url with the following message: RESPMSG: Failed to connect to host Input Server Uri = https://pilot-payflowpro.paypal.com:443 To clearly state the problem: I have already successfully connected from my test server to the link specified in the error message when obtaining the secure token. The post that results in the error message was sent from the browser (in this case, on the same physical box as my test server) to https://pilot-payflowlink.paypal.com, which is not the URL specified in the error message. Finally, the error seemingly occurs during the Payflow process - to my understanding, there should not be a call from my server to the link in the error at this point during the process. I mention this specifically to address the many search results I found relating this particular error message to PayPal's requirement for TLS1.2, which is already properly configured on my server (I should mention for the sake of completeness, I do still have TLS1.0 enabled on my test server, but cannot disable it for unrelated reasons. Nonetheless, I was able to successfully connect to obtain a secure token). I should mention that I also have tried to complete this same transaction on our production server, still using test credentials and endpoints at PayPal, with exactly the same results. The test server is also set up for TLS1.2 with TLS1.0 enabled. This problem may be the one that pushes me full-on into insanity, so any help would be greatly appreciated!!
... View more