Curious about the actual application flow?

Membership Withdrawal

Understanding

STOVE membership withdrawal is a feature where the user deletes their entire STOVE platform account.
Unlike game cancellation, which deletes only a specific game's data, the data of all games linked to the STOVE account and the account itself are deleted.

Item	Details
Deletion scope	The data of all games linked to the STOVE account + the STOVE account itself
STOVE account	Deleted
Entry path	STOVE Account Management > Membership Withdrawal
CP-company handling method	Handle after periodically looking up via the withdrawal-completed-user list API
Grace period	15 days including the withdrawal-request day for the grace period, completed after a final 30 days

STOVE Membership-Withdrawal Progress Flow

STOVE membership withdrawal is handled by the platform itself, and proceeds from request to completion in the order below.

Step	Details
① Withdrawal request	Account Management > STOVE Membership Withdrawal → notice → agree to the cautions → request → request complete
② Grace period	15-day grace period including the request day (e.g., request on 5/1 → grace on 5/16)
③ Withdrawal complete	Completed on the final 30th day; the account is deleted + all games used are cancelled (e.g., complete on 5/31)
④ Data cleanup	The CP company periodically looks up via the completed-user list API, then deletes in-game data (recommended)

Withdrawal-Status Notifications

When a membership-withdrawal request occurs, the STOVE platform delivers a real-time event to the CP company's server.
The CP company must implement a Callback API to receive the event and handle it per its operating policy.

Event info	When the event occurs	CP-company-side response guide
STOVE withdrawal `PLATFORM_WITHDRAW`	When the user requests STOVE platform withdrawal	Handle user logout and game restart

User-state-change event handling flow

In-game event handling
ㅁ This flow doesn't apply only to membership withdrawal. Other user-state changes such as ID/password change, sanction, and remote logout are handled the same way.
ㅁ Only GUID-based service games are supported. Member_no-based games need to be confirmed in advance through the technical contact.

Frequently Asked Questions

Q1. How does STOVE membership withdrawal differ from game cancellation?

A. Game cancellation deletes only a specific game's in-game data and keeps the STOVE account.
STOVE membership withdrawal deletes the STOVE platform account itself and affects all games linked to that account.

Q2. How do I check which users have completed STOVE membership withdrawal?

A. Call the withdrawal-completed-user list API as a periodic batch job to look up the list of withdrawal-completed users.
If you don't enter a lookup date, it looks up based on yesterday's date, so we recommend looking up the previous day's data once each day.

Q3. How should I handle it when I receive a PLATFORM_WITHDRAW event?

A. It's an event delivered at the moment the user requests STOVE platform withdrawal.
On receipt, log the user out in-game.
The actual account deletion and data handling must be done separately via the withdrawal-completed-user list API.

Q4. Can games that aren't GUID-based also use the withdrawal-completed-user list API?

A. This API is used only in GUID-based services.
For Member_no-based services, request separate guidance from the technical contact.

Q5. Do I have to delete withdrawal-completed users' data immediately?

A. You don't have to delete it immediately. We recommend changing a flag in the in-game DB, then backing up and deleting the data later during maintenance or the like.
However, if you collect users' personal information, legal liability can arise, so deletion is essential.

Need to contact us directly? stove.developers@smilegate.com