Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Accept PayPal and credit cards in your Android app
Failed to load latest commit information.
SampleApp Release 2.9.1
docs Release 2.9.0
libs Release 2.9.1 first release! remove Samsung app store caveats in readme Release 2.7.0
paypal-proguard.cnf Release 2.9.0 Release 2.9.1

PayPal Android SDK

The PayPal Android SDK makes it easy to add PayPal and credit card payments to mobile apps.

This documentation is available in Japanese: 日本語のドキュメント.


Use Cases

The SDK supports two use cases for making payments - Single Payment and Future Payments - and a third use case for obtaining information about the customer - Profile Sharing.

Single Payment

Receive immediate payment from a customer's PayPal account or payment card (scanned with

  1. Accept a Single Payment and receive back a proof of payment.
  2. On your server, Verify the Payment (PayPal Developer site) using PayPal's API.

Future Payments

Your customer logs in to PayPal just one time and consents to future payments:

  1. Obtain Customer Consent to receive an authorization code.
  2. On your server, use this authorization code to Obtain OAuth2 Tokens.

Later, when that customer initiates a payment:

  1. Obtain a Client Metadata ID that you'll pass to your server.
  2. On your server, Create a Payment using your OAuth2 tokens, the Client Metadata ID, and PayPal's API.

Profile Sharing

Your customer logs in to PayPal and consents to PayPal sharing information with you:

  1. Obtain Customer Consent to receive an authorization code.
  2. On your server, use this authorization code to Obtain OAuth2 Tokens.
  3. On your server, Retrieve Customer Information using your OAuth2 tokens and PayPal's API.

Integration with the PayPal Wallet App

The SDK will now use the newest version of the PayPal Wallet App if present on the device to log in to a customer account. No additional configuration is required to enable this feature. This integration enables device-specific PayPal FIDO integrations, including login by fingerprint on the Galaxy S5. In addition, a user who logged in to the PayPal Wallet App and checked "Keep me logged in" may not need to log-in again when paying with your app. For more information on how this all works, please read the blog post from one of our architects.


  • The integration will not be enabled in any of the testing modes, as the Wallet app does not support this developer testing environonment.


  • Android 2.2 or later
  • card scanning available only on armv7 devices
  • Phone or tablet

Add the SDK to Your Project

  1. Download or clone this repo. The SDK includes a .jar, static libraries, release notes, and license acknowledgements. It also includes a sample app.
  2. Copy the contents of the SDK libs directory into your project's libs directory. The path to these files is important; if it is not exactly correct, the SDK will not work. (NOTE: If you are using Gradle, copy SDK jar file into your project's libs directory, add as library to project, and finally copy the SDK folders containing the *.so files into src/main/jniLibs.)
  3. Add the open source license acknowledgments from to your app's acknowledgments.


Your mobile integration requires different client_id values for each environment: Live and Test (Sandbox).

Your server integrations for verifying or creating payments will also require the corresponding client_secret for each client_id.

You can obtain these PayPal API credentials by visiting the Applications page on the PayPal Developer site and logging in with your PayPal account.


Once logged in on this Applications page, you will be assigned test credentials, including Client ID, which will let you test your Android integration against the PayPal Sandbox.

While testing your app, when logging in to PayPal in the SDK's UI you should use a personal Sandbox account email and password. I.e., not your Sandbox business credentials.

You can create both business and personal Sandbox accounts on the Sandbox accounts page.


To obtain your live credentials, you will need to have a business account. If you don't yet have a business account, there is a link at the bottom of that same Applications page that will get you started.

International Support


The SDK has built-in translations for many languages and locales. See javadoc files for a complete list.


The SDK supports multiple currencies. See the REST API country and currency documentation for a complete, up-to-date list.

Note that currency support differs for credit card versus PayPal payments. Unless you disable credit card acceptance (via the PaymentActivity.EXTRA_SKIP_CREDIT_CARD intent extra), we recommend limiting transactions to currencies supported by both payment types. Currently these are: USD, GBP, CAD, EUR, JPY.

If your app initiates a transaction with a currency that turns out to be unsupported for the user's selected payment type, then the SDK will display an error to the user and write a message to the console log.

Disabling card scanning

Future payments does not require card scanning, so it is safe to remove the camera scanner libraries by removing the following folders within the lib directory: armeabi, armeabi-v7a, mips, and x86.

Single Payments can be configured to accept credit cards through manual entry, but without card scanning. To do so, remove the same libs above, and remove android.permission.CAMERA and android.permission.VIBRATE permissions from AndroidManifest.xml. If you wish to disable credit card support altogether, follow the above steps to reduce the permissions and sdk footprint, and add the following to the PayPalConfiguration initialization:



During development, use environment() in the PayPalConfiguration object to change the environment. Set it to either ENVIRONMENT_NO_NETWORK or ENVIRONMENT_SANDBOX to avoid moving real money.


  • These docs in the SDK, which include an overview of usage, step-by-step integration instructions, and sample code.
  • The sample app included in this SDK.
  • There are javadocs available.
  • The PayPal Developer Docs, which cover error codes and server-side integration instructions.


User interface appearance and behavior is set within the library itself. For the sake of usability and user experience consistency, apps should not attempt to modify the SDK's behavior beyond the documented methods.

Dependency Conflicts

The Android SDK is built on top of the Apache HttpComponents library included within Android. This can lead to a conflict if you provide your own copy of either Apache's httpclient, httpcore, or a package that depends on either of these, such as httpmime. To resolve this, you must use httpclient-android instead of httpcore and httpclient. The following example is the Android equivalent of the httpmime, httpcore, and httpclient dependencies:

compile ('org.apache.httpcomponents:httpclient-android:4.3.5')
compile ('org.apache.httpcomponents:httpmime:4.3.6') {
    exclude(group: 'org.apache.httpcomponents', module: 'httpclient')

Moving to PayPal Android SDK 2.0

Upgrade from 1.x

As a major version change, the API introduced in 2.0 is not backward compatible with 1.x integrations. However, the SDK still supports all previous single payment functionality. Upgrading is straightforward.

  • Most of the non-payment-specific extras of PayPalPaymentActivity have been moved to the PayPalConfiguration class, and the service startup has changed to take such a configuration object.

Older Libraries

PayPal is in the process of replacing the older "Mobile Payments Libraries" (MPL) with the new PayPal Android and iOS SDKs. The new Mobile SDKs are based on the PayPal REST API, while the older MPL uses the Adaptive Payments API.

Until features such as third-party, parallel, and chained payments are available, if needed, you can use MPL:

Issues related to MPL should be filed in the sdk-packages repo.

Developers with existing Express Checkout integrations or who want additional features may wish to use Mobile Express Checkout in a webview.

Next Steps

Depending on your use case, you can now:

Something went wrong with that request. Please try again.