# OnsideKit vs OnsideKitLite

OnsideKit ships as two products, built from the same source:

<table><thead><tr><th width="200">Product</th><th>Apple Pay / PassKit</th><th>Use it when</th></tr></thead><tbody><tr><td><strong>OnsideKit</strong></td><td>Included</td><td>The default. Use it unless you have a reason not to.</td></tr><tr><td><strong>OnsideKitLite</strong></td><td>Excluded</td><td>Your app cannot include the PassKit framework.</td></tr></tbody></table>

The two are **identical apart from Apple Pay**. Bank-card payments, login, products, the payment queue, attribution, event tracking, and the JS bridge are all present in both.

## What changes in Lite

* **No Apple Pay.** The purchase and payment-methods UI offer bank cards only — the Apple Pay option never appears.
* **No `applePayMerchantIdentifier`.** This API exists only in the full build. Referencing `Onside.applePayMerchantIdentifier` in an app that links OnsideKitLite is a **compile error**.

Everything else — the `Onside` API, models, delegates, and observers — is the same.

## Choosing and importing

The capability is fixed by which product you add as a dependency; there is no runtime or compile flag in your app. Add **OnsideKit** or **OnsideKitLite** as described in [Installation](/sdk/getting-started/installation.md), then import the matching module:

```swift
import OnsideKit        // full build
// or
import OnsideKitLite    // no PassKit / no Apple Pay
```

In both cases you use the same `Onside` API (minus `applePayMerchantIdentifier` in Lite).

{% hint style="info" %}
If you need Apple Pay later, switch the dependency to the full **OnsideKit** product and configure it as described in [Apple Pay](/sdk/purchasing/apple-pay.md).
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.onside.io/sdk/advanced-and-tooling/onsidekit-lite.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.