The PayPal iOS SDK makes it easy to add PayPal and credit card payments to mobile apps.
- Use Cases
- Add the SDK to Your Project
- International Support
- Moving to PayPal iOS SDK 2.0
- Next Steps
The SDK supports two use cases: Single Payment and Future Payments.
Receive immediate payment from a customer's PayPal account or payment card (scanned with card.io):
- Accept a Single Payment and receive back a proof of payment.
- On your server, Verify the Payment (PayPal Developer site) using PayPal's API.
Your customer logs in to PayPal just one time and consents to future payments:
- Obtain Customer Consent to receive an authorization code.
- On your server, use this authorization code to Obtain OAuth2 Tokens.
Later, when that customer initiates a payment:
- Obtain an Application Correlation ID that you'll pass to your server.
- On your server, Create a Payment using your OAuth2 tokens, the Application Correlation ID, and PayPal's API.
- Xcode 5 and iOS SDK 7
- iOS 6.0+ target deployment
- armv7, armv7s, and arm64 devices, and the simulator (not armv6)
- iPhone and iPad of all sizes and resolutions
- Clone or download the SDK, which consists of header files, license acknowledgements, release notes, and a static library. It also includes a sample app.
- Add the
PayPalMobiledirectory (containing several .h files and libPayPalMobile.a) to your Xcode project. We recommend checking "Copy items..." and selecting "Create groups...".
- In your project's Build Settings (in the
TARGETSsection, not the
Other Linker Flags
Enable Modules (C and Objective-C)
Link Frameworks Automatically
- In your project's Build Phases, link your project with these libraries. Weak linking for iOS versions back to 6.0 is supported.
- Add the open source license acknowledgments from acknowledgments.md to your app's acknowledgments.
CocoaPods users: see this note.
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
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 iOS 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.
The SDK has built-in translations for many languages and locales. See the header 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 payment card versus PayPal payments. Unless you disable payment card acceptance (via the
PayPalConfiguration.acceptCreditCards property), 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.
During development and testing, set the environment to Sandbox or NoNetwork/Mock mode, to avoid moving real money around. See the header files for more information.
- 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.
- Header files are thoroughly documented; refer to them as needed for extra details about any given property or parameter.
- 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 adjust appearance properties or attempt to modify the SDK's behavior beyond the documented methods in the provided headers.
Specifically, if you are using
UIAppearance to modify the appearance of any UI elements in your app, you should reverse those changes prior to presenting our viewcontroller, and set them again after dismissing the viewcontroller.
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.
- Initialization of the SDK is performed via methods of a new
- Most of the properties of
PayPalPaymentViewControllerhave been moved to
PayPalConfiguration, and the
PayPalPaymentViewControllerinitializer has changed to take such a configuration object.
PayPalPaymentDelegateprotocol methods have also been altered to include a
PayPalPaymentViewControlleras a parameter.
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.
If you use CocoaPods to keep up with new versions of the PayPal iOS SDK, we strongly recommend that you include your Pods directory in source control, as for security reasons we may sometimes stop distributing old versions of the SDK. For details, see this discussion of the card.io SDK pod.
Note: We're delighted that developers are using CocoaPods to help provide easy access to our SDK, and we'll help where we can. But we leave the creation and maintenance of the Specs to developers such as yourself. See http://guides.cocoapods.org/making/specs-and-specs-repo.html for details.
Depending on your use case, you can now: