> For the complete documentation index, see [llms.txt](https://doc.ecomm.api.tietoevry.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.ecomm.api.tietoevry.com/integrations/mobile-sdk.md).

# Mobile SDK

The Tieto Mobile SDK enables merchants to embed a secure payment experience directly into their native iOS and Android applications. Instead of building payment processing, security, and gateway communication from scratch, merchants integrate the SDK while Tieto handles the payment orchestration through the Payment Gateway.

The SDK provides a native checkout experience while maintaining PCI-compliant payment processing, authentication, and support for multiple payment methods.

## Benefits

The Mobile SDK is designed to reduce development effort while delivering a secure and optimized payment experience.

#### Native user experience

Customers complete payments without leaving the merchant application, providing a seamless checkout experience consistent with the application’s branding.

#### Faster integration

Merchants integrate a pre-built payment component instead of implementing payment security, encryption, tokenization, and gateway communication themselves.

#### Secure payment processing

Sensitive payment data is securely collected and transmitted to the Payment Gateway. The SDK supports PCI-compliant payment flows and tokenization, reducing the merchant’s PCI scope.

#### Flexible deployment

The SDK works alongside the Payment Gateway APIs, allowing merchants to combine mobile payments with existing backend services.

## Supported Platforms

| Platform    | Status    |
| ----------- | --------- |
| **iOS**     | Supported |
| **Android** | Supported |

## Core Capabilities

### Secure Card Payments

The SDK securely captures payment card information and communicates with the Payment Gateway for authorization.

Features include:

* Secure payment data collection
* Card tokenization
* PCI-aligned payment flows
* Payment authorization
* Payment status handling

### Alternative Payment Methods

The SDK supports additional payment methods through the same gateway integration.

Depending on gateway configuration, merchants can offer:

* Payment cards
* Account-to-Account (A2A) payments
* Alternative Payment Methods (APMs)
* Digital wallets (where enabled)

### Authentication

The SDK supports modern payment authentication mechanisms required by payment schemes and PSD2.

Capabilities include:

* 3-D Secure authentication
* Strong Customer Authentication (SCA)
* Merchant authentication
* Secure redirect and callback handling

### Customizable User Interface

Merchants can provide a payment experience that matches their application design.

The SDK supports:

* Native payment screens
* Application branding
* Custom colors and styling
* Localization
* Consistent iOS and Android user experience

### Gateway Connectivity

The SDK communicates directly with the Payment Gateway.

The gateway provides:

* Payment authorization
* Transaction processing
* Token management
* Payment status callbacks
* Error handling

## Payment Flow

<img src="/files/Unt8sqNuhyOfsytLWzih" alt="" class="gitbook-drawing">

## Typical Integration

The SDK is intended for native mobile applications.

<img src="/files/6C0x36ygMbBnNEi5gaZy" alt="" class="gitbook-drawing">

The merchant backend continues to manage:

* Order management
* Payment session creation
* Business logic
* Customer management
* Post-payment processing

The Mobile SDK is responsible for:

* Secure payment capture
* Authentication
* Gateway communication
* Payment status reporting

## When to Use the Mobile SDK

The Mobile SDK is recommended when merchants need:

* Native iOS applications
* Native Android applications
* Embedded in-app checkout
* Secure card data capture
* Reduced PCI compliance scope
* Faster mobile payment integration
* Consistent payment experience across mobile platforms

## Related Components

The Mobile SDK works together with the following Payment Gateway components:

* Payment Gateway – payment processing and routing
* Gateway APIs – Merchant backend integration
* Tokenization Service – secure card storage
* 3-D Secure Service – customer authentication
* Merchant Portal – transaction monitoring and reporting


---

# 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://doc.ecomm.api.tietoevry.com/integrations/mobile-sdk.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.