> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/secure-card-display/es/integrate-d1-sdk/get-started/configuration/1-binary-integration/ios.md).

# iOS

This guide is tested with:

* Xcode 16.1
* Swift 6.0.2

To integrate D1 SDK into your issuer application:

{% stepper %}
{% step %}

### Copy the D1 SDK frameworks

Copy the `D1` folder (including `D1.xcframework` and dependencies) into your project.

<figure><img src="broken://spaces/62lLFDcmLCeqqwmy4Fee/files/qyUMpiRE0Npgfo0i3Uiw" alt=""><figcaption><p>D1 SDK frameworks added to the project.</p></figcaption></figure>
{% endstep %}

{% step %}

### Open your target settings

In Xcode, open your app target, then select **General**.
{% endstep %}

{% step %}

### Embed the frameworks

Drag and drop **all** frameworks from your configuration directory into **Frameworks, Libraries, and Embedded Content**.

<figure><img src="broken://spaces/62lLFDcmLCeqqwmy4Fee/files/8aWLvnH6JKmit8HT73Dp" alt=""><figcaption><p>Frameworks embedded in the target settings.</p></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Note**

* During SDK version updates, ensure that you replace D1 SDK and all existing dependency SDKs with the newer copies.
* `TPCSDKSwift.xcframework` and `D1Core.xcframework` are no longer required as they are now included in the SDK delivery.
* `IdCloudClient.xcframework` is only available for EMV 3-D Secure (3DS).
  {% endhint %}

{% hint style="danger" %}
**Warning**

Use Release frameworks when submitting your application to the App Store. Use Debug frameworks only for development purposes.
{% endhint %}


---

# 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.payments.thalescloud.io/secure-card-display/es/integrate-d1-sdk/get-started/configuration/1-binary-integration/ios.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.