> For the complete documentation index, see [llms.txt](https://docs.onside.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onside.io/sdk/purchasing/ctc.md).

# CTC (Core Technology Commission)

Set up Core Technology Commission reporting for purchases made with OnsideKit: configure your app and give Onside access to report on your behalf.

When your app is distributed through an alternative app marketplace such as Onside, Apple requires you to report eligible purchase offers related to your app for the **Core Technology Commission (CTC)**. Every offer is identified by a Core Technology token from Apple's MarketplaceKit, and each token must be reported to Apple, **even if the customer doesn't complete the purchase**. See Apple's [Reporting transactions for the Core Technology Commission](https://developer.apple.com/documentation/marketplacekit/reporting-transactions-for-core-technology-commission).

For purchases made through OnsideKit, **Onside handles CTC reporting for you**:

* OnsideKit requests a Core Technology token from Apple each time a customer starts a purchase. You don't call MarketplaceKit yourself, and there is no CTC-specific API, setting, or callback in OnsideKit.
* Onside reports every token to Apple, together with its transaction, including offers that didn't result in a completed purchase.

To enable this, complete two one-time steps:

1. [Declare `MKSellsDigitalGoods`](#step-1-declare-mksellsdigitalgoods) in your app's Info.plist.
2. [Give Onside an In-App Purchase key](#step-2-give-onside-an-in-app-purchase-key) so it can send reports to Apple on your behalf.

{% hint style="warning" %}
**Onside reports only purchases made through OnsideKit.** If your app also offers digital goods or services through another payment provider, your own checkout, or a website, you are responsible for requesting tokens and reporting those offers to Apple yourself.
{% endhint %}

## Step 1: Declare MKSellsDigitalGoods

Add the Boolean [`MKSellsDigitalGoods`](https://developer.apple.com/documentation/bundleresources/information-property-list/mksellsdigitalgoods) key to your **app target's** Info.plist and set it to `YES`:

```xml
<key>MKSellsDigitalGoods</key>
<true/>
```

In Xcode, open your app target, select **Info**, and add **MKSellsDigitalGoods** as a Boolean with the value **YES**.

{% hint style="info" %}
OnsideKit doesn't add this key for you. Make sure it ends up in the final app's Info.plist — adding it to a framework or extension target doesn't configure the app.
{% endhint %}

## Step 2: Give Onside an In-App Purchase key

Onside sends CTC reports through Apple's [External Purchase Server API](https://developer.apple.com/documentation/externalpurchaseserverapi), which requires an **In-App Purchase key** from your App Store Connect account.

### Generate the key in App Store Connect

You need the **Account Holder** or **Admin** role to generate the key.

1. Sign in to [App Store Connect](https://appstoreconnect.apple.com) and open **Users and Access**.
2. Select the **Integrations** tab.
3. In the sidebar under **Keys**, select **In-App Purchase**.
4. Click **Generate In-App Purchase Key**, or the **Add (+)** button if you already have an active key.
5. Enter a name for the key, for example `Onside CTC Reporting`, and click **Generate**.
6. Find the new key under **Active** and click **Download Key**. Save the `.p8` file.
7. Note the key's **Key ID** and the **Issuer ID** shown on the same page.

{% hint style="warning" %}
App Store Connect lets you download the private key **only once**. Store the `.p8` file securely and never include it in your app or source code repository. See Apple's [Creating API keys to authorize API requests](https://developer.apple.com/documentation/appstoreserverapi/creating-api-keys-to-authorize-api-requests).
{% endhint %}

### Send the key to Onside

Email <merchant-support@onside.io> and include:

* the **Onside developer account** for which CTC reporting should be enabled
* the `.p8` private key file
* the **Key ID**
* the **Issuer ID**

{% hint style="info" %}
Onside uses this key to report on your behalf. If you revoke it in App Store Connect, send Onside a new key so that reporting continues.
{% endhint %}

## Availability

Apple issues Core Technology tokens on **iOS and iPadOS 26 and later**. On earlier OS versions, purchases work as usual without a token.

The purchase flow doesn't depend on CTC: if Apple can't issue a token, the customer can still complete the purchase. CTC also doesn't change how you handle transactions — continue to validate purchases, grant content, and finish transactions as described in [Making a Purchase](https://docs.onside.io/sdk/purchasing/making-a-purchase.md).

## See also

* [Reporting transactions for the Core Technology Commission](https://developer.apple.com/documentation/marketplacekit/reporting-transactions-for-core-technology-commission) — Apple Developer Documentation
* [Reporting tokens and transactions to Apple](https://developer.apple.com/help/app-store-connect/making-payments-to-apple/reporting-tokens-and-transactions/) — which offers require reporting, deadlines, and corrections
* [Making a Purchase](https://docs.onside.io/sdk/purchasing/making-a-purchase.md)


---

# 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.onside.io/sdk/purchasing/ctc.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.
