> 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/console/monetization/faq.md).

# Monetization FAQ

***

Here are answers to some common questions about monetization on Onside.

<details>

<summary>What fees apply to sales through Onside?</summary>

Sales processed through Onside are subject to a **10% payment commission**. No separate payout fee applies.

</details>

<details>

<summary>Are there any fees besides the Onside commission?</summary>

No. Onside charges a **10% payment commission** for sales processed through the platform. No separate payout fee applies. This commission helps cover platform operations, including infrastructure, team costs, and Apple's Core Technology Fee (CTF).

</details>

<details>

<summary>Who is responsible for taxes like VAT?</summary>

If Onside processes the payments for your app, Onside handles the collection and remittance of Value-Added Tax (VAT) for sales made through the platform in the EU. However, you are responsible for any other taxes on your income (such as corporate or personal income tax) in accordance with the laws of your country. We always recommend consulting with a local tax advisor.

</details>

<details>

<summary>Do I have to sign the Paid Application Agreement for free apps with In-App Purchases or Subscriptions?</summary>

Yes. The Paid Application Agreement covers all forms of monetization on Onside. You will need to review and accept this agreement before you can set a price for your app or offer any In-App Purchases or Subscriptions.

</details>

<details>

<summary>Can I change an In-App Purchase from 'Consumable' to 'Non-Consumable' after creating it?</summary>

No. The type of an In-App Purchase (Consumable or Non-Consumable) is permanent and cannot be changed after it has been created. This is because our system architecture and user entitlement records depend on this initial setting. If you have chosen the wrong type, you will need to delete the incorrect IAP and create a new one with the correct type.

</details>

<details>

<summary>Do I have to use the Onside Payment SDK for my purchases?</summary>

Using the Onside Payment SDK is the standard, recommended, and most straightforward way to implement In-App Purchases and Subscriptions. It's designed to work seamlessly with our platform.

However, we offer the flexibility for developers to use their own payment infrastructure. Please be aware that this option is subject to different commercial terms, which may affect your commission rate. For more details, please contact <support@onside.io> to discuss your specific needs.

</details>

<details>

<summary>What happens to existing subscribers if I delete a subscription's base plan?</summary>

When you delete a base plan, it becomes unavailable for new purchases immediately. Existing subscribers who are on that plan will **retain access** to their subscription content until the end of their current, already-paid billing period. After that, their subscription will **not auto-renew**, and it will expire. Before deleting, you must make the plan unavailable and ensure users have been notified, as prompted in the developer console.

</details>

<details>

<summary>How are prorated refunds for subscription upgrades calculated?</summary>

Onside's system handles all prorated calculations automatically. When a user upgrades to a higher-tier base plan within the same subscription group, our system calculates the value of the unused time on their current (lower-tier) plan. This amount is credited to the user and applied toward the price of the new, upgraded plan. The user pays the difference, and a new billing cycle begins immediately for the upgraded plan.

</details>


---

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

```
GET https://docs.onside.io/console/monetization/faq.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.