I am implementing server side payment verification on parse cloud code and so far it all works.
My question is with reference to the documentation -> https://developer.paypal.com/docs/integration/mobile/verify-mobile-payment/
Can I just implement the 'Looking up a payment using the REST API' for verification section or do i have to also do further requests and implement the 'How do I verify payments with MSDK version 1.x' sections as well?
Thanks!
You may skip the section of "verify payments with MSDK version 1.x", unless you've integrated with the old version 1.x mobile SDK.
*1.x msdk implements PayPal account payments with "Adaptive Payments" so the verification has to be slightly different from 2.x
Related
I am developing an app where users have to make appointments. In order to successfully book an appointment, they have to pay via PayPal or credit card. However, the SDKs for PayPal have been deprecated for a while. The alternative I am seeing, is integrating PayPal using Braintree. Will this alternative work for me being located in the Caribbean? If not, what other alternative is there for me to integrate payments via PayPal/credit card?
Express Checkout via Braintree SDKs will work. It uses credentials from https://developer.paypal.com / https://www.paypal.com -- not https://braintreepayments.com
Here is the guide: https://developer.paypal.com/docs/accept-payments/express-checkout/ec-braintree-sdk/get-started/
I have a task, I need append to my client project Apple Pay.
But we have integrated payment system Paypal.
I researched Paypal SDK and found official information about stopping support PayPal SDK in 2013 and then below advice, use Braintree SDK.
For using Braintree SDK I need create account in official web-site. where me need upload certificate and on page below a sow public and private key, merchantID.
My question, if I integrate Braintree SDK on my client application I can use PayPal gateway for my Braintree SDK.
If it real I will be grateful you for link on information.
Braintree definitely supports processing both Apple Pay and PayPal payments. For PayPal, you'll end up using the PayPal Business Account that you already have setup.
I recommend signing up for a sandbox account to test the functionality. Once you've signed up for a sandbox account, Braintree's developer docs have information on how to integrate PayPal and Apple Pay into your web/mobile app.
If you have any further questions while testing an integration, I highly recommend contacting Braintree's Support Team.
Is the a braintree iOS SDK for native iOS app payment system integration that uses paypal payments too?
I cannot seem to find one. Is there a third party sample code?
Or is there a guide on how to do it?
I work at Braintree. If you have more questions, please reach out to our support team.
Yes, the Braintree iOS SDK includes PayPal support:
PayPal
Braintree offers a few options when accepting PayPal payments. First,
you'll need to choose whether you would like to use our Drop-In UI or
a custom integration.
Vault vs. Checkout
Next, you can choose between our Vault and Checkout flows. Below is a
comparison of the two options:
Vault Compatibility: iOS, Android, and web
Checkout Compatibility: Web only
As of now, I'm able to link users to the desktop version of the payment preapproval page, where users can sign in or enter their payment information. Is there a mobile web version available?
here: https://developer.paypal.com/webapps/developer/docs/classic/mobile/gs_MPL/
"Because the Mobile Payment Libraries are build on PayPal's Adaptive Payments, you can accomplish many of the operations provided by that API with the MPL. For example, you can create mobile apps that provide for pre-approved and chained payments."
I can't find where the key to my Paypal Payments Pro API keys are. (I have a Pro account)
I need to do a DirectPayment, does anyone know where to find the right keys?
I know of this under My Profile > My Selling Tolls> API access
It says: "Manage API credentials to integrate PayPal Express Checkout."
But that is only for Express Checkout not Direct Payment. Is that the API info I use for direct pay? Because it seems like I cant get it to behave. Is there another setting I need to enable that Im missing?
The error I keep getting is:
Payment Error: This transaction cannot be processed due
to an invalid merchant configuration.
Cliff Note: I have gotten this to work on sandbox
I think you're getting confused (and don't worry, you're not the only one) because PayPal recently changed all their terminology for things.
It used to be called Website Payments Pro, and this used DoDirectPayment and Express Checkout. This was completely separate from their PayFlow Gateway that they acquired from Verisign years ago.
Now, they've dropped the word Website so they're just calling it Payments Pro, and they're actually putting people into the PayFlow Manager system instead of the "old" DoDirectPayment system.
From what you're saying here it sounds like you're actually setup with the new Payments Pro. That means you'll use the PayFlow Gateway to integrate the credit card processing instead of DoDirectPayment. PayFlow uses your manager.paypal.com credentials as opposed to the standard PayPal API credentials you're looking for.
Then, to add Express Checkout you would follow the instructions that you're seeing there, which generates the standard style (username, password, and signature) that you'll use with those API calls.
All of that said, technically, when you're approved for the new Payments Pro you're supposed to have access to all of the API's (PayFlow and regular PayPal), and when you generate your API credentials "for Express Checkout" these same credentials should work (in theory) for any other API's that hit PayPal directly as well. I can't promise that, though.
So...what are you supposed to do? Well, you either need to switch to the PayFlow gateway for your integration, or if you'd just rather use DoDirectPayment, you need to call PayPal and request that they convert your account from the new Payments Pro 3.0 to the old Website Payments Pro 1.0.
2.0 was actually called Payments Pro PayFlow Edition, which just confuses things even more.
Hope that helps.