My code for my PayPal integration has worked for a decade or so with no problems.
Today I've generated a new public certificate as the old one was due to expire. I did it exactly the same (documented) way that I've always done it, and uploaded it to PayPal. Stupidly, I deleted the old one before testing the new one.
And now I get this message when I try to make a purchase:
The email address for the business is not present in the encrypted blob. Please contact your merchant.
Any idea what's happened? My only thought is that PayPal are trying to force me into using a more modern way of integrating their payment gateway with my site, and are giving this error based on me having a newer public cerficiate now. But PayPal, if that's really what it's about, have a link to a help article on the subject FFS!
I'm stumped, any suggestions welcomed.
If you have this problem it might be worth checking the file permissions of your new private key. Mine was 600 and needed to be changed to 644 to match the old outgoing file. Problem solved.
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'm quite a noobie at Firebase. I'm asking for a sort of step by step guide to setup email verification.
Currently, my app uses basic email password login. I want users to be verified so I'm hiding content based on a user's emailVerified property. I'm calling the .sendEmailVerification() and it sends to the current user's email but, whenever I click the link in the email it says the link has expired or someone has used it, this also doesn't change the property. I suspect it has something to do with the api manager. I currently have my website hosted to the built-in Firebase hosting URL.
Based on this link in the docs (which refers to a similar function but not the exact one): https://firebase.google.com/docs/reference/js/firebase.auth.Auth#sendPasswordResetEmail
p.s. I can't find anything regarding this exact function in the docs.
I think I need some sort of listener at the link of the email or on my website?
Thanks in advance, any answers are appreciated.
there could be an issue with your browser api key. You may have some referrer restrictions on it. This could cause the misleading error (code expired or used) to occur. Either fix that issue or generate a new one in the Google console.
I really need your help guys. Since two hours I'm facing with a very strange problem related to Paypal Sandbox. I read lot of answers here on stack overflow but none of them helps me.
I'll try the explain my problem: when I create a new sandbox account (respecting all rules like password strength, load balance etc.) I receive the "success" message, the account is created and visible in the list, but when I open it using "Profile" button I receive this error message (and is really a problem because I need to get the username, password and signature to work in sandbox mode):
Account Details
Your request is still processing, please wait...
No difference between "Buyer" or "Seller" account, it always fail.
I've tried in many ways (using notes, changing email address, using custom numbers into email) but nothing is work for me.
Someone can suggest me what can I do?
Thank you very much.
I think I've found a temporary solution to works with PayPal sandbox.
Instead of create an account using "Create Account" button you have to register a new account using sandbox website.
In details:
Go To: https://sandbox.paypal.com
Register a Business Account
Go To: https://developer.paypal.com/developer/accounts/ and click con "Click Here". This link is placed in the Second paragraph of the page:
Want to link existing Sandbox Account with your developer account? Click Here and provide credentials of your sandbox account
You will be redirect to sandbox paypal web site, if you don't do anything it will recognize your previous register account (anyway, if not, you have to login with the new created account), procede with linking process and after you will have, in the list of accounts, a new one with "Profile" button ready to show you informations necessary to works.
I don't understand way paypal release an important tool like this with a lot of bugs. No response received from no one.
BugPal your are luky because we needs you but please, improve your development process! :#
Looks like a general problem on Paypal side. We see same issues with two of our accounts. It was working last friday.
I dont have access anymore to the sandbox.paypal.com
In Developer Account I tried:
Want to link existing Sandbox Account with your developer account? *Click here* and provide credentials of your sandbox account.
After few redirections it refuses to sign me in:
Error
Relying Party Validation error: client_ID or redirect_uri provided in the request does not match any of the registered clients. Please check the request.
I've tried with two differents accounts, one of them do not have a live account, and it give me each time the same error without further explanation.
#paypaldev filed a ticket on the issue but I'm not sure what to expect.
Do am I the only one ?
An update here for everyone else as I followed up with François via Twitter. The internal teams were able to track down the issue that was causing the relaying party validation error, and it should now be fixed without needing a workaround. If anyone is still seeing an error, please let me know and I'll circle back with the teams working on the fix.
After paypal updated their interface (sandbox.paypal.com for example is not working, now you have to go to developer.paypal.com) many of the things are not working: 2 of them are particularly frustrating and I was hoping someone here knew how to get around them:
Am I the only one whose sandbox customer test accounts are not able to make purchases? The transaction page says they are not available.
IPN validation is not letting me send a https request. When I do it says there is something wrong with the server name. Yesterday however before the update I could get verified status. If I dont put https, now my handler gives me an invalid responde status, code: 400. What does it mean?
To fix the HTTP 400 error, follow the instructions in https://www.x.com/content/bulletin-ipn-and-pdt-scripts-and-http-1-1 and update your code to pass "Host" information. Ideally, things should work with just the recommended changes from the above link. Apparently, thats not the case. Here is a fix from one of the PayPal MTS person - PalPAL sandbox IPN processor rejecting all messages?
Remove the "cmd=notify-validate" option from the validation URL. I tried this and it worked. Though it doesn't return the right string, atleast it doesnt break with the 400 error.
While we wait for a fix from Paypal, I wonder how a company like PayPal can cause such a huge blunder and not post anything on their status page - https://www.x.com/developers/paypal/documentation-tools/site-status/pp-cri. It just makes you think that even smaller companies can do a better job than companies like PayPal.
For the code:400 issue, you have to update the post to version 1.1. That information is located here.
https://www.x.com/content/bulletin-ipn-and-pdt-scripts-and-http-1-1 in this bulletin.
However, as I posted before the asp.net example uses a call, that does not exist, so I was only able to get mine partly working. After fixing this, the servers appear to be rejecting calls to https, or the cert they have installed is invalid.
Action Required before February 1, 2013
Merchants need to update their IPN and/or PDT scripts to use HTTP 1.1, and include the “Host” header in the IPN postback script. In addition to this bulletin, these merchants will be notified via a direct email.
Alright, seems to be fixed!
If you are having trouble logging in, like suggested above, clear cache and cookies and try again.
Regarding the error 400, seems to have been solved by paypal!