API endpoints?
I need information about the get/post/put/del and authorization.
How do the customer order?
After customer paid and he/she choose Uber eat service, does he/she pick from my website or from the Uber eat app?
How does the customer pay? How does the business owner get paid? What kind of payment service can they use?
Related
I am creating an app where sellers can sign up on an app, and sell products (think Etsy). Local users can view and purchase the product from the seller.
What would be the best approach for doing this? I was looking at the Square API. I looked through Square's Merchant API but could not find an endpoint to create a new Merchant account (which I would ideally create for each seller). Another option might be to create one Merchant account (for the app) and a new Location for each seller. Does this seem like a good idea?
At this time the ability to create merchant accounts with Square APIs isn't currently available. We’re constantly working to improve our features based on feedback like this, so I’ll be sure to share your request to the API product team.
It isn't recommended to have all payments run through one Square account cause you'd have to deal with all of the chargeback risk for every payment and all the payouts of funds to the sellers.
I'm exploring how to develop some g-suite applications (eg. gmail add-on, spreadsheet add-on, etc...). It's not clear to me whether the g-suite platform offers a payment API to let me charge customers $2.99 USD per installation? Then google will automatically settle the sales revenue into our bank account? I can't find any technical literature that confirms or denies the existence of this feature.
Or do I need to take a more traditional approach by directing the customer (eg. in the form of an iframe or something) to a page on my web server, where I integrate my own merchant service provider of choice (eg. paypal, stripe, etc...) to handle credit card payments? Then I need to oauth2 authenticate them on my server, confirm their billing is in good standing, before providing access to paid features?
I think for your case you should go and read carefully the G Suite Marketplace Developer Agreement.
In there you have this line which explicity says that you would need to pay Google a "Listing Fee"
3.2 If you choose to distribute Products through the Market for a fee, you will pay Google a non-refundable listing fee ("Listing Fee") as set forth at https://code.google.com/googleapps/marketplace/fees.html.
i want to develop an App with Uber API to provide a service, collect payments from the customer and book the ride for them automatically through my App. Is it possible to use feature like book for a friend and pay for the ride from a single developer account? or does the customer have to pay for the ride separately ?
Background
We are developing a webshop that we sell to other companies.
The companies hosts the webshops and sell their products on their own servers.
The webshop uses the Paypal Rest API for the customers to make payments.
https://developer.paypal.com/docs/api/
To activate Paypal as a payments method the companies provide their Paypal details in the webshop admin area.
How we do it now
Right now the companies need to create a Paypal Developer account, and then create a new App in developer.paypal.com to get their own Client ID and Client Secret Code.
They then provide their Client ID and Client Secret Code in the webshop admin area.
Question
Is this the correct way to do it?
We think it feels a bit strange to tell our customers (the companies) to create "Developer Accounts" in Paypal, when they are not actually developers, just webshop owners selling their products.
I found this information about setting a parameter called "payee", which means you can set the receiver of the payments, see: https://devblog.paypal.com/setting-payee/ and https://developer.paypal.com/docs/api/payments/#definition-payee
Is it possible to use the "payee" as a solution instead, like this?:
We as developers of the webshop have a Paypal developer account, and provide our Client ID and Client Secret Code, which are then used in all our customers webshops? Then the companies would only need to provide their Paypal Account Email in the webshop admin area, which is then used as the "payee" parameter.
Is this a good and ok solution? Or is the same App, Client ID and Client Secret Code not allowed to be used for multiple companies and their webshops? How can we solve this then?
Thanks!
This is solved after communication with PayPal support.
This is some information from the communication that answers my questions:
"Do not use then the payee field as you will be able to deal with all the transactions created, that you don't want as you are an external "actor" in the payment process."
"About creating a developer account and App it does not mean that they are developers. The developer portal is a tool that allow to manage the Apps and deal with Sandbox test accounts. It is the only way to create an App."
So the conclusion is that we are doing it the correct way today, which is like this:
"Right now the companies need to create a Paypal Developer account, and then create a new App in developer.paypal.com to get their own Client ID and Client Secret Code.
They then provide their Client ID and Client Secret Code in the webshop admin area."
I have a Digital Service Providing website. This service allows user's customers to take appointments for the services user is providing. Now the customers must be able to Pay for the service before confirming the appointment.
My requirement is each user of my website have different services and different price for it.
They have already configured these services on my web application. I have all details in the database.Now how can i integrate Pay Now buttons for this scenario? I do not want the user to configure the service price again on Paypal account?
There are a number of ways you can handle that. Do you have a shopping cart system setup on the site so people can browse and add service items and checkout all at once, or how exactly is that setup?
If you're tracking items and order price within a shopping cart you can use Payments Standard Cart Upload Method to easily gather order details and send the user over to PayPal for payment.
You could also use the Express Checkout API if you prefer web services. If you want to offer credit cards directly (without any PayPal redirect) you could include Payments Pro as well.
If you want to stick with standard buttons, but you want to automate the process, you can use the Button Manager API.