I have a client who I made an app for, is it possible for me to publish via my developer account, but have the revenue from the app go to them? The client does not have a developer account, does he need one to have full control of the App on Appstore?
The main issue would be the payment, statistics and such.
No it is not possible to publish on your account but have the info, stats, and payments go to your client. If he wants to directly get the payments and info he would need his own account.
You can publish on your Dev account and then transfer the payments to him manually. Also there are several services which you could use to give him access to statistics (appfigures.com, appannie.com etc).
Related
I am trying to find out how to give a developer the least amount of access they need to my business PayPal account for my app. How should I set this up so I protect my private account information from the developer while allowing them enough access to develop?
They need access to test and develop with the PayPal APIs. I created a sandbox account for the app, I gave the developer the Sandbox ID and API Credentials along with the sandbox test accounts I created.
The developer asked if I could give them the login for my PayPal developer account so they can see the Dashboard for testing and see can transactions. I don't think this is the right way or they could access my bank, and company information.
I have read the PayPal documentation for information about this but can't find much. This guide has the most information I've found but not exactly what I am looking for.
In your account, go to your profile settings and find Manage Users. There you can add a user and select the amount of access they can have. Give them the username and password you make for them, NEVER give your email and password.
To get started using adding users to your account and managing their levels of access, log in to your PayPal account, go to your Profile, and click Manage Users under Account Information.
https://www.paypal.com/cgi-bin/webscr?cmd=p/sell/permissions-outside
Your developer does not need access to your account at all, regular paypal.com or developer.paypal.com.
They would simply login to developer.paypal.com with their own PayPal account and create their own test accounts for use in the sandbox. They can build your app using their own test accounts, and then hand it over to you so that you can simply update the API credentials with your live values and ensure the code is running live instead of against the sandbox at that point.
developer from India can create Paypal sandbox account as i am also from India and created sandbox account.
Use this,
https://www.paypal.com/businessprofile/mytools/apiaccess
go to paypal, all tools, you can see manage API, press update, then you'll see that screen. Im doing it right now, i don't know if it will work.
I have created and submitted a Paypal application ( using the classic API). The application is in a conditionally approved state. Paypal reached out and asked additional questions which I responded back with details. The application does not use the Paypal API to make payments. It only reads transactions related data and shows useful reports and insights for users. The API permissions requested are
1.Obtain transaction specific information.
2.Obtain your paypal account balance
3.Search your transaction specific information.
4.Search your transactions for items that match specific criteria and display the results
I was able to get a live app id and also have the API username, password and API signature. However since our app uses Paypal oauth, the permissions part doesn't work . My guess is this is because the app is conditionally approved. Is this the right assumption? Also what is the typical timeline for an app to get approved? My Paypal account from which I created and submitted the app is a verified account. I have sent messages from within my developer portal to support but I haven't heard anything back.
So far we have been working with a sandbox account. The live application I created is in a different account than the sandbox account. I am not sure if this is an issue.Would be great if someone who has been through the process can confirm.
Unfortunately there is not really a "typical" time frame for app approvals as too many factors go into the approval process. The best thing would be to call in to PayPal to inquire on the status.
I am having another developer do the PayPal integration for an app. I want to allow them to do this without giving them access to the real bank account information or anything about the PayPal account which would allow them to have access during production. They requested that I make a PayPal Developer Account and provide the Client ID, Client Secret Key., and Merchant Name.
Do I create a PayPal developer account and give the developer full access to it by giving them the login? Then when the app goes into production how does it use the live PayPal business account without the developer being involved?
Can someone explain the correct process in having a developer do the PayPal integration for development and testing but not have any access to accounts during production?
I've read the PayPal documentation and similar stackoverflow posts but can't find the answer I'm looking for.
You can check the sample app by downloading it from here. It includes both the things sandbox enviornment & real account. You can take reference from this sample app.
we're not using the API - we just need to integrate a pre-made plugin for our CMS and help our client setup their account.
We've been looking here:
https://developer.paypal.com/webapps/developer/docs/classic/lifecycle/ug_sandbox/
But are having trouble understanding a few things:
If you live outside the US, you can't create a developer account on: https://developer.paypal.com
Do we somehow create a developer account (and dummy sandbox accounts) on paypal.co.nz?
Once we have a developer account, can it granted developer access to the client's PayPal account so we can login and test/trouble shoot any integration issues?
Sorry if this is easy, but we're having trouble finding a good overview or step-by-step of the process.
Any pointers in the right direction would be much appreciated.
Cheers
First off, Ebay and PayPal have different APIs and different accounts. So creating an account on Ebay would only let you test against the Ebay API.
Can't comment on the NZ vs US thing. The signup form didn't ask me for a country. But, in theory, the developer site shouldn't care (it's a developer site, not live PayPal).
Granting third party access isn't something you do through the Developer site. That's done with your live PayPal credentials and their authorizing you. Not sure if this can be done in REST but it is possible in Classic
Because the sign up form on developer.paypay.com won't accept non-us addresses, you have to sign up by doing the following:
Go to your local paypal site e.g. paypal.com.au or paypal.co.nz
Sign up for a normal account
Go to developer.paypal.com
Sign in with the normal account you just created
Paypal will then use your new normal account details to create a developer account.
From then on, just login at developer.paypal.com.
I was using Paypal Sandbox for testing transactions last year using my PayPal developer account.
I just checked last week that I cannot access my old account, so I decided to sign up for a new account. However, you need now to sign up for a business account. Business account is only available to U.S. businesses (I came from outside the US).
I was hoping if you can suggest an alternative and free developer account (similar to PayPal), but with a different payment gateway.
Thank you.
How about stripe ?
Stripe
Uses a JavaScript based API to complete transactions.
Simpler to integrate with multiple platforms.
You don't need a US Business account to use developer.paypal.com.
Simply sign up via https://www.paypal.com/ for a live PayPal account, either Premier or Business, and you'll be able to log in to developer.paypal.com with it.
Note however that the new REST API is currently available for live US Business accounts only, but this won't affect the availability of other Sandbox products or functionality.
I'll look into why the messaging states that you do, because that's not correct. Thanks for pointing this out!