Both Mobile Express Checkout and Adaptive Payments allow me to specify account for money receiving explicitly. I just need to set PAYMENTREQUEST_n_SELLERPAYPALACCOUNTID for Express Checkout or receiverList.receiver(0).email for Adaptive Payments.
Is there same functionality for PayPal Mobile SDK? Looks like I can only create payment to my account (linked to client_id in PayPalConfiguration), not to other merchants accounts. Did I miss something?
Dave from PayPal here. You are correct: at this moment, the PayPal Mobile SDK does not allow you to choose at runtime the merchant who will be paid. We do expect that in the coming months this ability will be added to the PayPal REST APIs on which the Mobile SDK relies; when that happens, we'll definitely add this functionality to the SDK.
Related
I am entirely new to making E-commerce website. Already I have built the basic interface and all required features. I am stuck in one thing. Basically I am working on Paypal integration. At the moment, the money comes to my account after checkout since I have setup with my credentials. But in my Website, one can be a publisher too. How do I ensure that the money goes from the customer to the publisher account? As for the admin, since I am the admin so I already configure with necessary credentials. But what about those publishers who sign up in my website? Thanks. Just give me an idea. I am using React.js in my front end.
You can use the official react-paypal-js
When creating the order, specify the recipient payee with an email or merchant id.
A server integration to create the order is not required, but more robust for the usual reasons.
I have a Unity Mobile app that has a web UI that we are using PayPal IPN. I was wondering if anyone knows if PayPal has to approve the app before it goes live if its using IPN and not the mobile SDK?
In order for you to use IPN, you do not need any approval from PayPal. All you need to have is a PayPal account and some integration with the IPN listener. From there you are good to go with the IPN. I hope I answered to your question.
I am setting up an App Engine application, and I want to register all my users based on their phone number (like Whatsapp).
The server will need to send an SMS to the user to authenticate. Then the user can log in with a combination of their phone number + password.
Does Google Apps support this type of authentication model, or do I have to use a Google Account?
I saw Twilio support, but that seems more for setting up an app that sends a bunch of SMSes/VoIP server side. I just need to receive one SMS per user to confirm their phone number.
Note: this will be a iOS/Android app, with possible web support in the future.
The App Engine does not force you to use any authentication mechanism. You can choose Google Account option when creating your app, and you may find it useful for admin logins, for example, but you don't have to use it for all users of your app.
The App Engine does not offer a built-in support for SMS authentication, but there is nothing that prevents you from using it. Twilio API offers all the tools that you need.
Note that SMS authentication model has major limitations. For example, people tend to change phones and sometimes their phone numbers, and they typically lose access to the previous phone/number immediately upon switching, which makes it difficult to transfer their accounts. This is one of the reasons why more apps choose a two-step verification (username/password with SMS confirmation) as opposed to a single-step SMS-only approach.
How can I send mail using Google's mail API without adding that email address to the project? Right now Google says you need to add them as a developer but I don't want the user to see anything about the project.
Example would be a contact form email coming from sales but I don't want sales to find their way into the google dev console and see our costs.
You could use services like SendGrid which give you a lot more features than GAE's Mail API.
See a more detailed answer here:
send email on Google App Engine from custom domain
You could create a new account sales-mailer#whatever that looks like it is coming from sales, but for which only you have access. Then give that account View-only access to your project.
I never used Google technologies to develop webapps before, and I'm a bit overloaded and confused. A lot of information.
My scenario: Developing a webapp for, say, company.com, using Google App Engine (Python, Webapp2, Jinja2...). The domain company.com is Google hosted (e-mail and calendars are the important parts here). So, I want my GAE-based app to add events to the domain users' calendar, send them e-mails, etc. The basic flow is:
A user of this domain logs into the web app, using his/her mail: myname#company.com. (IMPORTANT: Users CAN'T use their private GMail accounts, or any other OpenID-based authentication. Just their domain accounts). I know this can be configurated from the admin console, when creating the app.
The user fills a form, and a new calendar event is created. This event is added to his/her calendar, and to his/her manager's calendar too. The user receives a confirmation e-mail (event created) and the manager a notification e-mail (someone invited you...).
I've been reading a lot about authentication, authorization, google app engine and google apps, but I still don't have a clear image about what technologies/libraries/apis I should use.
I've seen a lot of examples using oAuth and Calendar API v2, but oAuth is deprecated, and seems that I should use oAuth2. Calendar API v2 is deprecated too, and v3 is recommended... I see a lot of entry points in the documentation, and I don't know where to start.
Any piece of advice is strongly appreciated. Many thanks in advance.