Closed cokodude closed 7 years ago
@Cokodude thanks for the request.
I've changed the title of this issue from Support changing clientIDs
to Support more than one payee
, because that's really what you need.
A clientId
is tied to the merchant responsible for an app. It is used by that app when the app signs itself into PayPal. Conceptually, the clientId is unchanging for a given app.
PayPal's servers track apps and clientId
s; it's possible that an app that keeps switching its clientId
might trigger an automated fraud concern.
At the moment the PayPal REST APIs, on which our mSDK is based, support payments to only the merchant associated with the app's clientId
. At some point in the future (no date available yet, unfortunately), the REST APIs will also support payments made to a third party. Once that feature is supported by the REST APIs, we will add it to our mSDK as well.
In the meantime, if you really need to change payees within your app, you might consider the older PayPal MPL library.
Hi. Is there any progress on the REST API regarding this issue? Maybe you've even got a clue of some date when this might going to happen in the meantime? Any info is highly appreciated. Thanks!
@maxyha Sorry still no update on this one :(
This is a serious issue preventing third party services (SaaS, ecommerce, etc) from implementing the REST API. It's unreasonable to request that non-technical users create their own "App" in their paypal account and copy/paste their client_id/secret here. There needs to be a way to do this via OAuth, similar to the Permissions Service - but I cannot find any information on an equivalent.
Hello Any update for Support more than one payee? means this functionality added with SDK ?
@dgoldman-ebay
Hi,
Any Update for this issue ?
can we get client_id and change payee at runtime in android SDK?
@moonandroid @Trusharbhatt Unfortunately, no updates at this time.
Does @dgoldman-ebay s comment on Apr 23, 2014 still apply? I.e. to use Paypal's MPL library to support user to user Paypal transaction. In our case within an Android app. Or do you have any new guidelines?
In case you still recommend using the MPL library, do you have any information re how long you will suppor this?
Yes, MPL is still our recommendation at this time. MPL will be deprecated at some point in the not-so-distant future, once we have a suitable replacement for it.
@braebot ok thanks for the info. Can you share with us if you are planning to keep the functionality to facilitate 'user to user' payments (where the app owner is not sender or receiver) in the replacement solution?
Yes. We call those 3rd party payments, and there's plans in the works to deal with that scenario.
Continuing this subject, is is possible to receive part of amount sent to payeeEmail as a fee for using the app? I cannot see this code, but it's possible to do in web SDK.
@Coobers Not currently. You can follow similar feature requests at https://github.com/paypal/PayPal-REST-API-issues/issues/2 .
I come back on this post, is this working with future payment (capture / void) or not ?
There's no plan to add this feature to REST API. PayPal marketplace will be product providing this feature instead.
Hi, I'd like to request a feature to change the pay-to account. From this SO question, there isn't a way to change this after preconnecting: http://stackoverflow.com/questions/22717432/changing-the-pay-to-account-for-paypal-mobile-transactions
I'm making an app for merchants to sell things, and I'd like the mobile SDK to pay the merchants directly. The clientID would change depending on which merchant is selling the item. Thanks!