I'm writing an android app where customers can purchase tickets for the race track. I've got the whole paypal sandbox set up and it works to take payments. Only problem is, how would I get it to take the customers name so that I know who gets the tickets? How do I pull the info to determine exactly who gets the tickets ie shipping info etc... Where in the api are the screens for shipping etc?
Thanks
Jeff from PayPal at your service. The PayPal Android SDK does not yet support shipping addresses. Your best bet is to use MPL until the new SDK will support this feature.
Related
I'd like to use the paypal SDK for android in order to process real products available in my app. I would like the users to enter their card information only once, or at least only require a security code and for paypal to save these details so I need only send a token of some sort to refer to those saved details, rather than the user entering their card information again when purchasing a different product. Essentialy, I want to make the process of buying further products as easy as possible after the initial purchase.
Is this possible using the paypal SDK for android? or would I need to implement the Paypal REST API on my server, and communicate from the android to the server, and let that do the heavy lifting instead?
I actually don't understand the difference between the Paypal SDK for android, and the REST API available, as I imagine you could use both from android (using HttpClient for example)
Thank you,
Jonas
Sounds like you are wanting to enable future payments in your app. However, PayPal Mobile SDK 2.0+ only supports this feature as PayPal payments and not direct credit cards.
Currently if you wanted to store credit card details you would need to use REST API and the Vault.
Paypal SDK:
The PayPal Mobile SDKs enable native apps(Android, iOS) to easily accept PayPal and credit card payments.
For android: https://developer.paypal.com/docs/classic/mobile/ht_mpl-itemPayment-Android/
Paypal SDK is newer than PayPal Rest API, the best difference is the speed to implement in your aplication.
PayPal Rest API: include features like pre-approved payments, chained payments, and more support for non-U.S. accounts, and sometimes you really dont need that. And take more time de implementation.
I Recommend use Paypal SDK.
My startup is developing a real-time marketplace platform for taxi companies somewhat similar to Hailo, Get taxi, Uber and Lyft (more or less), etc.
We are shopping around for a mobile payment solution and so far, we looked at the products offered by PayPal, Intuit, Braintree, and Stripe.
We are having a hard time with finding the mobile payment solution that fits our requirements.
Requirements:
1) (Must have) Passenger should be able to pay within the app by using previously added payment methods such as Credit Cards (CCs), Paypal (optional). Passenger is asked to enter the CC information only once when they sign up (or add a new card), so the CC info needs to be stored somewhere and retrieved when needed seamlessly. However, we would really prefer not to apply for PCI compliance.
Q.1) Let’s say I use PayPal Mobile SDK 2.* for payment system in our app. In the above scenario (1), is the passenger required to have a PayPal account (even for just using CCs for payment) and link it to our app?
Note: I have spent a lot of time digging into PayPal Mobile SDK 2.0 documentation (also called their support). I was told by the support person that merchants cannot store credit card info with PayPal for mobile payments (which I thought was the whole point of SDK 2.0).
2) (Optional) Passenger should be able to pay with a physical credit card by swiping it in the reader plugged into the driver’s smartphone. However, we need to integrate this process into our app (which is not currently supported by PayPal Here and Square). So, basically we need an API provider that allows creating custom POS integrated with our app.
Q. 2) Am I right when saying that scenario (2) cannot be accomplished with PayPal, Braintree, Intuit, or Stripe?
Q.3) Do you have any suggestions regarding the payment system that would allow us to implement scenarios (1) and (2)? just scenario (1)?
Please help if you have dealt with similar problems or know more about the subject. Thank you
Q3. You can also check out LevelUp. Facilitates in-app payments similar to PayPal and Stripe.
Similar to PayPal, it will allow you to store an access token after the user links their account. You will not be able to charge the card directly, as this would subject you to PCI compliance. LevelUp does not support the ability to swipe a physical credit card.
A. to Q. 1) Yes, the passenger is required to have a PayPal account if you want to enable future payments. PayPal stores and charges the credit card, without the merchant having access to it. This is pretty much the core of the Digital Wallet industry. You might have thought that you could process the credit card yourself, after retrieving it from PayPal. This is not supported, and would subject you to PCI compliance-ness.
A. to Q. 2) PayPal Here does not have a publicly available SDK yet.
A. to Q. 3) Just scenario 1 can easily be accomplished by integrating the 2.0 PayPal SDK.
I'm writing an educational paper about the recent PayPal Android mobile SDK (link) and will have to implement an app with it.
While this is available only in the US for now, I've seen that you can set the country of the merchant and personal accounts in the Sandbox for test accounts.
Is it possible to try out the new Android SDK and implement an Android app with only a test account set to US for that cause (my physical location is outside US)? I'm not planning to use the app in live environment, only for testing purposes.
The recommended option is to set the environment to ENVIRONMENT_NO_NETWORK which is a fully mocked development mode that will not perform any network operations whatsoever. That should give you a chance to see the UI, card.io scanner, etc. but without any server dependencies.
As an FYI, the SDK does not check your location via GPS or device sensors. As long as the client_id and PayPalPayment objects are valid, the SDK should work.
I'm a non-U.S. developer. How does the site redesign affect me?
You can use our Classic APIs (like Checkout and PayPal Payments Standard) for new integrations. If you don't have a PayPal account, you can create a new Business account for your country.
If you've previously used our Classic APIs, you can continue to use them. You can import existing Sandbox accounts on the Sandbox Accounts page by using you old Sandbox email address and password.
Our REST APIs and the PayPal Mobile SDK are currently targeted only for the U.S. market. However, we'll be rolling them out to other countries over the rest of the year.
Ref: https://developer.paypal.com/webapps/developer/support/faq
I am planing to integrate paypal Mobile Express Checkout or Mobile Payment Library with my android application for in-app purchase.
I would like to know,
How can I proceed with the integration?
Google's "IN_APP BILLING" or PayPal's payment gateway. Which is better?
All the transaction fees that are applicable to me as a merchant.
Thanks,
Mith
I'd recommend starting with PayPal because as of today it's much more widely used than Google by buyers. That may change in the future and it may not, but at any time you could always add Google and offer both as payment options just to ensure you have options for buyers to pay however they want. You might even add Amazon and other options at some point.
PayPal provides a mountain of documentation. You might want to start with their SDK library. Click on the mobile tab and you can download the Android specific SDK. If you prefer, you can setup simple HTTP POST requests using NVP or SOAP API's.
PayPal's fees are based on your monthly volume and they start at 2.9% plus 30 cents. Once you do $3k/mo in volume that will drop to 2.5%, and if you do $10/mo in sales it'll drop to 2.2%.
I want to know if its possible/legal(not against terms of service) to use the google checkout api for an android app to support in app purchases. The types of items being purchased would be something like extra coins where they can be purchased multiple times.
I know that this would require getting the user's credentials or pointing them to the checkout page or something. I want to know if its possible to do this within the app by opening a webview to the checkout process, and then getting a callback to a custom url on my server that will allow the app to see that the purchase was successful. Something like what the android market does for app purchases.
Thanks for any responses. I don't currently have code to show as I am researching into this before devoting time to create something I won't be able to use. Also maybe android will support native in-app purchases in newer versions of the sdk.
Spoke to (Android evangelist) Reto Meier at Google Tech Days about this and he said it is perfectly OK to do inter-app purchases in the market. You should comply to other regulations - most common is that you need to only buy content that is consumed on the mobile. Virtual "coins" are on quite thin ice, some countries ban issuing "virtual money" but you can do essentially the same with just little different paradigm. Hope this helps.
Android market documentation explicitly states that you can do check it.
http://developer.android.com/guide/market/billing/billing_admin.html#billing-refunds
Important: You cannot use the Google Checkout API to issue refunds or
cancel in-app billing transactions. You must do this manually through
your Google Checkout merchant account. However, you can use the Google
Checkout API to retrieve order information.