> For the complete documentation index, see [llms.txt](https://developers-apps-in-toss.toss.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers-apps-in-toss.toss.im/guide/en/operation/service-termination.md).
# End Service
At Appintos, mini app service termination takes place upon a partner company's voluntary request or in the event of a violation of laws or policies. Please check and strictly comply with the process for each termination type, notice obligations, refund handling method, and post-termination screen handling below.
***
### 1. Service termination types
Service termination is categorized into the following types.
| Type | Description | Advance notice obligation | Refund and withdrawal processing |
| ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | -------------------------------- |
| **Termination at the partner company's request** | When the partner company directly requests service termination | 30-day advance notice (partner company → user) | Partner company handling |
| **Termination due to policy/law violations** | Immediate termination due to policy/regulatory violations (including termination for failure to implement improvements) | Notice for 30 days after termination (partner company → user) | Partner company handling |
| **Termination due to business closure** | Immediate termination due to business closure | Notice for 30 days after termination (partner company → user) | Partner company handling |
***
### 2. Process by termination type
**2-1. Process when the partner company voluntarily requests termination**
1. Appintos [Channel Talk](https://apps-in-toss.channel.io/workflows/787658)Please let us know your intention to terminate the service through
2. For users of the service, the partner company must, from the scheduled termination date **30 days before service termination, an in-mini-app advance notice and a functional message must be sent**are required.
* The displayed screen and functional message must include the scheduled service termination date and customer support contact information.
* Please contact us via Channel Talk after reflecting the relevant details.
{% hint style="info" %}
**Please be sure to check**
If you do not use Toss Login, you cannot send functional messages. Please be sure to notify users within the mini app so they can check the termination notice when accessing the service.
{% endhint %}
3. The partner company must promptly process subsequent in-app payment (or Toss Pay) refund requests and immediately handle user withdrawal requests.
* If a user requests service withdrawal and deletion of related information, it must be destroyed without delay.
* In-app payment and Toss Pay refund requests must be processed without delay.
4. Please submit the termination request via Channel Talk in line with the service termination date.
5. Afterwards, the withdrawal of consent to the relevant terms in the Appintos console will be carried out.
**2-2. Termination when improvements are not implemented due to policy/regulatory violations**
1. We notify the partner company of the improvement period and service termination according to the violated policy.
2. If not implemented within the improvement period, post-termination notice and functional messages will be sent after service termination.
* The displayed screen and functional message include **the service termination date, reason for service termination, and customer support contact information**will be notified.
3. The partner company must promptly process subsequent in-app payment (or Toss Pay) refund requests and immediately handle user withdrawal requests.
* If a user requests service withdrawal and deletion of related information, we destroy it without delay.
* In-app payment and Toss Pay refund requests are processed without delay.
4. Afterwards, the withdrawal of consent to the relevant terms in the Appintos console will be carried out.
**2-3. Immediate termination due to regulatory violations, etc.**
{% hint style="info" %}
**Please note**
In cases of serious violations such as regulatory violations or intellectual property infringement, the service is made unavailable immediately without a guidance period.
{% endhint %}
1. As soon as the violation is confirmed, post-termination notice and functional messages are sent after service termination. (for 30 days after termination)
* The displayed screen and functional message include **the service termination date, reason for service termination, and customer support contact information**will be notified.
2. The partner company is notified that the service has been terminated due to violations of relevant laws and regulations, and this can also be checked in the console.
3. The partner company must promptly process subsequent in-app payment (or Toss Pay) refund requests and immediately handle user withdrawal requests.
* If a user requests service withdrawal and deletion of related information, we destroy it without delay.
4. Afterwards, the withdrawal of consent to the relevant terms in the Appintos console will be carried out.
**2-4. Termination due to business closure**
1. If the business is closed, you become a non-business entity, so monetization features and Toss Login features cannot be used.
2. Accordingly, if the timing of business closure is confirmed, the mini app in operation will be automatically terminated.
3. If the service is terminated, the partner company must promptly process subsequent in-app payment (or Toss Pay) refund requests and immediately handle user withdrawal requests.
* If a user requests service withdrawal and deletion of related information, we destroy it without delay.
4. If you wish to launch the service as a non-business entity, create a new workspace and register the mini app again to launch it.
***
### 3. Toss Pay and in-app payment refund processing
**3-1. Refund responsibility principle**
The obligation and responsibility to refund Toss Pay and in-app payments **are the partner company's**responsibility. In principle, Appintos does not directly get involved in refund processing.
* When service termination is announced, we clearly inform the partner company of its refund obligations.
* If a refund complaint occurs, Appintos may contact the partner company individually to request refund processing.
**3-2. Google Play Store refund processing**
{% hint style="info" %}
**Please note**
Since Appintos cannot directly verify whether a refund is possible (whether the goods or service have been fully used), please handle it directly.
{% endhint %}
* After payment **within 48 hours** case: refunds may be processed at Google Play Store's discretion.
* After payment **After 48 hours** case: the partner company must directly approve or reject the refund in the Appintos console.
**3-3. Apple App Store refund processing**
Refunds may be processed at Apple App Store's discretion without a separate deadline.
***
### 4. Toss Login
**4-1. Toss Login handling**
* Display a screen when accessing the service **member withdrawal channel**and guide users, and if the user requests service withdrawal and deletion of related information, destroy it without delay.
* Responsibility for related communication and issues with users **are the partner company's**lies with
***
### 5. Withdrawal of consent to Appintos-related terms
**5-1. Withdrawal of consent to terms**
* After the service ends, **withdraw consent within the console regarding the terms for each feature and service partnership**in that way.
* Since terms consent for each feature such as Toss Login and in-app payments is managed in the console, it is withdrawn sequentially after termination.
---
# 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, and the optional `goal` query parameter:
```
GET https://developers-apps-in-toss.toss.im/guide/en/operation/service-termination.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.