> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/2checkout-apis/2checkout-apis/mobile-sdks.md).

# Mobile SDKs

## Overview  <a href="#overview__00a0" id="overview__00a0"></a>

Verifone's Mobile SDKs enable you to encrypt and validate card payments, handle 3D Secure verification, and interact with PayPal. Mobile SDKs also provide an optional customizable UI that can display available payment methods and collect card data. For more information on our technical integration, code snippets and examples, check our public [**iOS SDK**](https://github.com/2Checkout/2checkout-ios-sdk)/ [**Android SDK**](https://github.com/2Checkout/2checkout-android-sdk) GitHub README pages.

Mobile SDKs can be used to facilitate:&#x20;

* Card payments (with 3DS support and customization)&#x20;
* PayPal&#x20;

## Availability  <a href="#availability__00a0" id="availability__00a0"></a>

Mobile SDKs are available to all users with a 2Checkout account and a card payment setup. &#x20;

Your application or system should have the following requirements or higher to apply the SDKs:&#x20;

* iOS 12&#x20;
* Android 8.0+&#x20;

## Benefits  <a href="#benefits__00a0" id="benefits__00a0"></a>

As a merchant, mobile SDKs allow you to:&#x20;

* Safely tokenize card data&#x20;
* Enhance UI customization&#x20;
* Integrate PayPal&#x20;
* Simplify payment acceptance across different sales channels&#x20;

## Payment methods  <a href="#payment-methods__00a0" id="payment-methods__00a0"></a>

This screen allows customers to select their preferred payment method. The payment method selection UI component can be customized to display only the methods that your system and business support. This component is optional, and you are free to create your own UI.&#x20;

<figure><img src="/files/c1BDwcMxkjZC011IFU0s" alt=""><figcaption></figcaption></figure>

## Card Payments  <a href="#card-payments__00a0" id="card-payments__00a0"></a>

The SDKs provide support for collecting and tokenizing card data. We recommend building your own Thank you page to process the result of the transaction as in the example below.&#x20;

<figure><img src="/files/xa4eA1oaulAhWsinOlOM" alt=""><figcaption></figcaption></figure>

### Customizing card forms  <a href="#customizing-card-forms__00a0" id="customizing-card-forms__00a0"></a>

The mobile SDKs' customizable UI enables you to edit the font and color of the card form fields.&#x20;

## 3DS  <a href="#id-3ds__00a0" id="id-3ds__00a0"></a>

The SDKs provide a native 3DS experience using a Cardinal native SDK, which comes bundled into our own SDKs.&#x20;

<figure><img src="/files/aJsi9IgRqH7j3AdJcSL5" alt=""><figcaption></figcaption></figure>

## PayPal  <a href="#paypal__00a0" id="paypal__00a0"></a>

For PayPal, we use a webview to display the customer PayPal confirmation details and provide the necessary information to finalize the payment.&#x20;

<div><figure><img src="/files/9qKhpoFOunaNz4m08kVn" alt=""><figcaption></figcaption></figure> <figure><img src="/files/c2TnAt9jfpRTysnezRmP" alt=""><figcaption></figcaption></figure></div>

Check out our public [**iOS SDK**](https://github.com/2Checkout/2checkout-ios-sdk)/[**Android SDK**](https://github.com/2Checkout/2checkout-android-sdk) GitHub README pages for code snippets and examples.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.2checkout.com/2checkout-apis/2checkout-apis/mobile-sdks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.