i connected several projects... but this one gives an error. Can anyone help?
Screenshot of error
This issue seems to be related to an internal project/billing configuration. Since this kind of messages can be thrown when the accounts have payment issues, I think that you should firstly verify that your billing account is in a good status; however, if you continue getting this error message after this validation, I suggest you to take a look the Issue Tracker tool that you can use to raise a Dataprep ticket in order to verify this scenario with the Google Technical Support Team.
Related
My Adsense was working fine since last 7 years. One fine day I tried to change the bank account from Individual to Company bank account. Since then I am getting the error - "An unexpected error has occurred. Please try again later. [or-ieh-01].
I have tried-
Submitting the valid documents for the new bank account.
Reverting to the old working bank account (with the valid document for that account).
Deleting both the accounts and then try adding any of the bank account.
Neither of the above worked. Now my earned amount is stuck and I cannot use other Ad providers also as they required Google Ad Manager that is linked with a working Adsense account.
Please help me resolve this issue.
You're not the only one. Unluckily this is a known issue since mid-2021 and still unresolved. The cruel truth is, that there seemingly only exists a generic answer to this issue:
Try the path described on the official GooglePay issue fix site. Do exactly as demanded and double-check everything. In most cases that will work.
If that doesn't work contact the GooglePay Support. That's meh but you probably won't have another choice.
Or you might, as written in the official issue post, "try to use another form of payment or bank account for now".
You have my sympathy :-/
Edit: As mentioned in the comments below further ideas would be:
In case you're using it, disable VPN while you're using GooglePay as it seems to lead to conflicts.
Associate a new mail address.
Not sure, how esoteric that is, though. Those ideas came up after talking to friends and some web research.
Have you tried disabling adblocker and trying again?
I spent the last day and a half 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=20180916085333999&URLMETHOD=POST&SILENTTRAN=TRUE&AMT=2&BILLTOFIRSTNAME=John&BILLTOLASTNAME=Doe&BILLTOADDRESS=123TestDr.&BILLTOCITY=Testcity&BILLTOSTATE=TN&BILLTOZIP=55511&BILLTOEMAIL=johndoe#test.com&USER1=3&USER2=&USER3=0&USER4=2
to which I receive the following response:
RESULT=0&SECURETOKEN=[hidden]&SECURETOKENID=20180916085333999&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# 5105105105105100, then post the following from the browser directly to https://pilot-payflowlink.paypal.com:
fund_id=3&ACCT=5105105105105100&CVV2=555&EXPMONTH=01&EXPYEAR=20&EXPDATE=0120&SECURETOKENID=20180916085333581&SECURETOKEN=[hidden]&feeTokenID=20180916085333999&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
NOTE: The value above is only one part of the response sent to the error page. The rest of the return values include information from my original secure token request, which I would assume could only be returned if a successful connection had been established with the link in the error message??
To clearly state the problem:
I have already successfully connected from my test server to the link specified in the error message, when first I obtained 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 or the browser to the link in the error message 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, and my server passes PayPal's own TLS test at https://tlstest.paypal.com/).
I should mention that I also have tried to complete this same transaction on our production server, still using test credentials and test endpoints at PayPal, with exactly the same results. The test server is also set up for TLS1.2 with TLS1.0 enabled, and also passes PayPal's test.
This problem may be the one that pushes me full-on into insanity, so any help really would be appreciated!!
Disabling TLS1.0 has helped others with this issue. If you keep having problems, contact PayPal's support
For anyone who might find this question and be similarly frustrated, I want to share that I was able to solve the problem by creating a new Payflow Gateway test account.
I spent a great deal of time on trial and error solutions with no success, and PayPal Merchant Technical Services was able to duplicate the problem but was also unable to find a solution. Finally, after simplifying my test app as much as possible (two bare-bones HTML forms filled in and submitted manually), I came to the conclusion that there might be something wrong with my test account. Upon creating a new account with new credentials, then inserting them back into my original code, everything worked perfectly.
As of this morning, PayPal MTS is continuing to research the problem, since others have reported similar issues.
For others with similar problems, it is worth noting that I am now able to complete transactions while TLS 1.0 remains enabled.
I am getting the following error in the transactions section of the dashboard (since days, I am not able to test anything):
We’re sorry, something went wrong while fetching sandbox transactions. Please try again.
Does anyone know how to fix this?
I talked to the PayPal support and it seems to be a global issue at the moment which should be fixed until tomorrow. There is another solution to create a sandbox account right now (see Unable to use sandbox accounts), but then I am not able to verify those accounts because the notification email with the confirmation link is completely broken. So unfortunately it seems we all just have to wait for it to work again.
I am seeing the same issue this morning. I am getting UNKNOWN_ERROR when trying to process via the Sandbox from .NET using SDK as well. Even the .NET Sample SDK is returning a UNKNOWN_ERROR. I sure hope they get this fixed soon.
I have the same issue on the transactions dashboard. Additionally Mass Payout's are not processed, but regular Payment's are working.
Sandbox mode, using Node.js REST API
I am facing the same problem as seen in this http://forge.prestashop.com/browse/PNM-1165
It says this following message after I click on 'pay with paypal'
Error occurred:
Please try to contact the merchant:
PayPal response:
->
I don't know what to do T^T
Im using prestashop 1.5.4 and paypal module 3.5
There is one reply suggestion from Francois Gaillard added a comment - 29/Mar/13 9:29 AM
He said that
This issue occurs when your server IP has been blocked by the PayPal's API. If you are running share hosting environment the server can be banned blacklisted by PayPal.
Please, try to contact PayPal support they should be able to help you.
Let us know when you have more details please.
Thank you,
Kind regards.
That answer is incorrect in as much that we do not block IP addresses to our API endpoints without making the merchant aware.
It is correct, from our experience, that the above error occurs in PrestaShop when your server is unable to establish a successful HTTPS connection with our API endpoint.
I suggest you take a look at General troubleshooting - API timeout and run the tests provided in it.
Pay special attention to the AT&T block we mention in there, as we've seen a large number of API callers getting blocked at that level.
Unfortunately that block is beyond our control - but we've heard good reports of merchants getting in touch with AT&T and getting that block lifted (if confirmed to be blocked there).
I'm looking to use a PayPal hosted Gateway page to accept payments for a site I'm working on (based in the UK)
After a lot of difficulty, I've managed to set up an test-only Payflow account using this guide: https://www.x.com/developers/community/blogs/pp_integrations_preston/testing-paypal-payflow-gateway
But when I log in and try and change the hosted checkout settings to "test", I'm getting:
"Error: 102 error content"
and no settings will update.
I can find anyone else who's seeing this same error message, but PayPal's documentation doesn't mention this error in the manager, but says that error 102 with transactions is the payment processor not being available - so I think there's a chance it's that.
The guide I used to set up the account only linked to a US version of the registration page, so I just changed the countrycode parameter in the query string attached to the link so I could use a UK address, but the Payment Processors all seem to be based in the US, I've tried 2 different ones (FDMS Nashville and WorldPay) and I'm getting the same error on both.
I've had so many problems trying to set this up, I've been reading various guide and the official documentation solidly for 3 days and haven't even opened my IDE yet - what am I doing wrong?
Do you have link to your checkout that you can provide, so that we could walk through and test it and see what the issue may be? It's hard to see say what the issue is at this point, with out seeing what you are passing over, where at specifically the error is getting generated at during the checkout, and without knowing how your account is set up.