So I was able to test CreateAndSend Successfully in sandbox, and have now moved my credentials to the live versions.
I created a new business account for using the live version, and have gotten my api credentials for it.
Replaced API ID,PASS,SIGNATURE with those credentials.
Connecting to svcs.paypal.com/Invoice/CreateAndSendnvoice.
and an error I'm getting back is user is not allowed to perform this action.
I set the merchant and payeremail to my email (I tried the paypal email and then the api1 email)
I was wondering if my paypal account needs to be verified to do this API call.
Thank you.
Make sure that you have a live app id and that it is approved for this feature.
Following up on this. Having my business account verified fixed the "user is not allowed to perform this action" problem I was having.
Related
I am integrating paypal in android application.
There is one pair of credentials from which I am unable to login, but on the same code other pair of login/password credentials is working fine on live payment.
I want to know what could be an issue.
i want to know what could be issue.
Your credentials could be wrong, or the login/payment could have been denied, or one of the accounts involved could be unable to send or receive payments. Those are some possibilities.
You haven't provided any specific and detailed information about the error behavior, so one can only guess.
When I do a Paypal API signature request under business profile, the generated api is using my old website ---whateverAPI.my-old-website.com
I've updated all of my business information and see no instances of the old url in my paypal account or the developer or sandbox accounts.
I do not have the old login information for developer area where I created the original API information as it was changed to my new login/business.
I need to change the URL associated with my account so the api generated has the apicode.new-website.com
I know this is a low level expertise for most of you compared to what you are coding but I am completely stuck and have tried everything I can think of.
Thanks for taking the time to read!
When the API is first requested on an account, it is generated based on the email address associated with the account at the time. Even if you remove the email address and request new API credentials, it will still use that original email address. There is no need for concern, you only set this in your API call or in your shopping cart to use. Buyers are not going to see it or anything, and it's not something you would regularly share or have to use all that often. Once you set it in your code, you don't really mess with it again unless you need to set up the API credentials again.
When creating sandbox accounts through the developer.paypal.com dashboard, either individually or with Bulk Account Upload, the accounts that should only have a bank account are not created correctly. When I look at the account profile there is an error notice: "We experienced some issues on our end while creating this Sandbox account. Please delete it and try again." It was the same one that I was getting on all accounts created without a hard enough password. There is no payment methods in the created accounts. I can log into the accounts and they appear to work fine except trying to add payment methods to the "Wallet" does not work. Is there anyway to find out the actual error or get around this bug?
I believe this is an intermittent issue and clearing cookie and cache on your browser will help.
If the issue still persist, you might need to file a ticket via https://www.paypal-techsupport.com/app/ask and provide all the relevant information (e.g: screenshot of the error message, browser information, etc). Their technical support will check this for you.
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.
My application uses the SetExpressCheckout paypal classic API method. It is working fine when I use real accounts in a live environment.
It used to work fine using test accounts, but some weeks ago it has stopped working right. At some point, my application calls the "SetExpressCheckout" API method using curl in PHP. When I use the test seller account that I've always used for my tests, I always get the following error:
SetExpressCheckout API call failed.
Detailed Error Message: Security header is not valid
Short Error Message: Security error
Error Code: 10002
Error Severity Code: Error
I know that paypal has recently restructured its "developer network", and the issue seems to be caused by this but I have no proof of that. The API I used is now called the "classic" API.
I've read the documentation, and it says that I now have to create a new "real" paypal account, and then use it to log to https://developer.paypal.com. I did that.
Once logged to the developer website, there is a feature allowing us to import all the test buyer and seller accounts used in an old sandbox account. I did that, and my old test accounts appeared in a list.
One of them is the test seller account I used to test. When I check the details of this account, the username, password and signature used to authenticate to the paypal API are there. If I use them, it still returns the previous error.
There is also a feature allowing me to create test accounts. I've created a new seller, and still, I get the same error message.
When I search on google about this issue, most answers says that the username, password or signature are wrong or have hidden white spaces in them. That's not my case.
I don't know how to solve that problem. I am wondering if the API endpoint has changed. I currently use "https://api-3t.paypal.com/nvp" for tests. I am using the NVP API, version 64.
To make it short:
1) My test account used to work
2) The code has not been modified
3) Real accounts used to work and still work.
4) But test buyer account has stopped working
5) The issue chronologically coincide with paypal "developer network" restructuring.
6) I don't know what has changed exactly and might cause this.
7) Does anyone know what has changed and might has caused this (a new parameter in the query string? Endpoint URL changed?)?
8) According to my previous description, do I seem to have misunderstood something, and what?
I currently use "https://api-3t.paypal.com/nvp" for tests.
That's your problem. You're using test credentials, but the live API endpoint.
Change your endpoint to https://api-3t.sandbox.paypal.com/nvp and all should be fine.
Security header is not valid means that your credentials are incorrect. I've never once seen that error where this wasn't the case.
You need to make sure that if you're using sandbox credentials for testing that you're hitting the correct endpoint and using the correct credentials.
Lots of times people accidentally have sandbox credentials set but then send them to the live endpoint or visa versa. If you're hitting the correct endpoint and your credentials are indeed correct you won't get this error.