I want to use the Uber API to initiate a trip for a user. However, I want to pay for the trip (using my preset pickup and drop-off locations). It would be acceptable to launch a ride request with a prepaid promotional credit of my ride budget.
Is this possible in the Uber APIs? I appears that the payment methods endpoint returns payment methods for the rider. It also appears that the payment_method_id option to the ride request endpoint wants a rider's payment method.
Is there a way I can initiate a trip to/from preset locations, while also ensuring that I pay (up to) $XX for the trip?
Thanks!
There is not any publicly available way to do this currently. The Uber Developer platform are working on making this option available. I am not able to share any timeline on that, but it is indeed being worked on.
In the meantime, I would direct you to non-API solutions that may in some way fit into your use-case of paying for another user's uber ride:
https://www.uber.com/events
https://uber-central.com/
https://www.uber.com/business/
Hope that helps.
Related
I am starting a business and I would like to offer Paypal as a payment option, but for my business it is essential to be able to block an amount of money, just like a car rental or a hotel does on a credit card. Would it be possible to block an amount from my users PayPal account and release it or book it for good later?
My business is of course an online service, and I want to do this pragmatically in a Spring based application.
I think what you are looking for is Authorization and capture.
I haven't used that feature from Paypal, but have used it elsewhere. What you are looking for is usually called card authorization, preauthorization, or preauth.
Yes it's possible
PayPal's REST API offer 3 primary ways to ensure you paid for product/services that you give to your customers
sale. Makes an immediate payment so you get paid immediately
authorize. Authorizes a payment for capture later.(this is what you see in a car rental or hotel)
https://developer.paypal.com/docs/integration/direct/payments/authorize-and-capture-payments/
order. Creates an order. - which gives you the flexibility to
multiple to do multiple authorizations and captures (these are for
complex use cases such as when you buy a computer from Dell you would
be authorized for the desktop, monitor, keyboard at different points
of time based on availability and then the funds captured when they
are shipped)
Does the paypal fee applicable to any call within their apis or a particular call?
For instance, if I use any call within the /billing-agreements apis, do I get charged the 2.9% or less, plus $0.30 per transaction?
If not, which api do I use that charges me?
In the case, it only charges me a particular api, does that mean all other apis are free to use? how many calls can I make per day/month/year?
Thanks for your help!
PayPal will only charge you on successful transaction, Meaning they will not charge you for setting up a billing agreements nor for looking up a transaction with API, They will only charge you when the transaction of that billing agreement go through.
They are not charging the API call directly.
I coundn't find anything on limits in the documentation and as far as I know you can do an unlimited number of API call to paypal
Check the following link for PayPal documentation
https://developer.paypal.com/docs/api/
EDIT After Comment
Im not exactly sure how it works.
But I think PayPal system is somewhat queued based, In the sense that some API call are for creating subscription, They wont charge on the API call, But they will charge on every transaction recurring every month.. You don't need to make a API call every month to make the charge go through,
but still you'll see charges on your account.
Some call like create_payment will have a response with "Successful"
But only after you also called payment_execute but wont tell you what transaction_fee you had.
To get what transaction_fee you had You need to call with an other API call after to get that information
payment_get
I am working with paypal first time.
I have a product and I want to integrate paypal with it.
I want to achieve the following tasks :
Client comes to my website and select a plan,which is a monthly recurring plan.
Then client is redirected to Paypal for payment.
Client makes payment.
Return backs to home page.
I have gone through the documentation of paypal and I have the following questions.
What should I use REST API or Classic Sdk, as I want to create Recurring Profile,Work with EXPRESS-CHECKOUT and REFERENCE TRANSACTIONS.
I have customers all over globe and it is stated in the documentation that, for the customers in Germany and China , I have to use REFERENCE TRANSACTION.
Some where in the documentation of Merchant SDK it is stated that the classic API's will be deprecated, so is it a good approach to use Classic SDK
I also wanted to track the transactions(payment) made by user, so that I can show him the amount that is deducted in each month in his profile details.
Please suggest a feasible solution to my problem.
Thanks in advance.
Here's what I use. I went to Web Payments Standard and created a Subscription button. (I like the unencrypted variety, but you can encrypt if you want.) In there, you set the terms of the subscription, as well as where to post the IPN message. When the IPN message comes back, you deal with it. You'll get a subscr_signup at the start along with a subscr_payment. Then, on renewals, you'll get a subscr_payment again. What I like to do is store every verified IPN message in the database for my customer.
For handling the management of those subscriptions for things like tracking info, refunds, subscription cancellations, and voids, you'll need to use NVP API, which is a very simple API. If you stored in a database every IPN message with all those fields, then you should be able to pass certain fields of those to the NVP API in order to get what you need done.
If you're worried about longevity of the APIs, then don't. All they do when they deprecate APIs is stop giving you good docs on them. They still let those older versions run. If they didn't, there would be major upheaval on the web with web commerce products breaking all over the place. However, that said, if you want to prepare for the future, then get on the Braintree Payments API because PayPal bought Braintree and that's the future of their API.
I would like to know if there is a way for invoking payment facebook API, from server side, without user intervention. I.e. Once the user approves one payment, server side acts by itself, without regarding (and annoying) the user for approvals for subsecuent payments.
This could apply to services which its business is based on repetition, e.g. in a monthly basis or weekly basis.
Thanks in advance.
PS: I think the only way to do this is by susbcriptions, but it limits the usage of one or more services.
I think this is not possible, I mean, if you payment method is Facebook credits then users will have to deal with payment gateway. On the other hand, if you have some business based on repetition then you will have to use Facebook subscriptions, as you said.
Perhaps you could perform something based on SOAP-WS, but I don't know if Facebook has services available for that.
I'm trying to integrate a payment mechanism to my site. The scenario that I need is not trivial and can be explained by the following example:
User pays upfront for a subscription program (i.e. receiving Netflix). User is able to make changes to the subscription (i.e. change number of movies checked out each time from 4 to 2)
User is able to buy additional one time purchases via the provider's site (Netflix) supplied by 3rd parties. These items (i.e. popcorn, snacks) get billed to the same credit card as the subscription without having to go through the process of resubmitting the credit card information.
Of course, my site takes also a small fee for the transactions :-)
I was wondering if this is supported by PayPal, Google Checkout or someone else.
Thanks.
The Paypal api can handle all of those processes.
I seem to have dropped the ball on what kind of answer you wanted so I'll leave it at that.
If you have some feedback, more direct questions I will try to answer as much as I can
--
The money would best go through you first, unless somehow you can convince your customers its normal to bill them per item. Also if they pay by credit card you should only bill them once as you would incur fees on every payment. I don't know of anyway to bill once but distribute the payments.
As for the paypal docs..
Very good resource, there is also some sample code for most major web languages
Also this will get you started if you don't have a developer login
Their developer support is also pretty good. One thing a lot of people seem to screw up when starting out with the paypal api is not setting the latest version in the configs so don't forget to update that to the latest release. :)
Disclaimer..
Yea I know there is a lot of bad press about paypal and crazy stuff happening, but they do get the job done most of the time, its not my fault the customers love to use it.