> For the complete documentation index, see [llms.txt](https://docs.ecommerce.seb.ee/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecommerce.seb.ee/integration/mobile-sdk/ios-sdk.md).

# iOS SDK

Accept payments inside your iOS app with a native Swift SDK for hosted checkout and card entry.

The **iOS SDK** (`EGWPay`) takes a payment your backend has already created and gets it paid on the device.

It presents the hosted checkout page in a web view, or drives a card payment from a card form you built yourself, and reports one outcome back to your app. The SDK is written in Swift, works from Swift and Objective-C, has no third-party dependencies, and bundles no resources.

Two entry points are available, and both use the same backend contract:

* **Hosted checkout** - the checkout page runs inside a web view, so card, Pay by Bank, Click to Pay and the wallets all work, including EMV® 3-D Secure. Your app never sees card data.
* **Native card form** - you build the card form, the SDK encrypts the card data on the device and drives the card session and any 3-D Secure challenge.

### Getting started

If you are new to the SDK, we recommend the following path:

1. Read the [**Overview**](/integration/mobile-sdk/ios-sdk/overview.md).
2. Complete the [**Installation**](/integration/mobile-sdk/ios-sdk/installation.md) steps.
3. Work through the [**Quickstart**](/integration/mobile-sdk/ios-sdk/quickstart.md) to make your first sandbox payment.
4. Continue with [**Using the SDK**](/integration/mobile-sdk/ios-sdk/using-the-sdk.md).
5. Explore the [**Guides**](/integration/mobile-sdk/ios-sdk/guides.md) for security and error-handling detail.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ecommerce.seb.ee/integration/mobile-sdk/ios-sdk.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.