Need a more detailed development guide?

Feature Guides / Sign-in

·

Authentication

·

Identity Confirmation Service

Signing In

STOVE Sign-up

STOVE Login

Device

Game Entry

Payment

Other Settings

Cancel Game

Withdrawal

Service Introduction

This is the whole flow from a user creating a STOVE account to accessing a game. To use STOVE services, a user can sign up as a regular member with an email or SNS account, or start as a guest in a mobile game without formal sign-up.

The STOVE platform provides both the login/sign-up screens (Auth UI) and per-region regulation handling (identity verification, child protection). So the game studio doesn't need to build separate login/sign-up screens and only needs to prepare the required per-scenario integration logic.

Member Structure

Member types

STOVE members are divided into regular members and guests depending on whether they hold a STOVE account (MemberNo). The MemberNo is the account-unique identification number issued at STOVE sign-up and is the basis for distinguishing users. Here, sign-up means creating a STOVE account. Regular members are divided into email accounts and SNS simple accounts by sign-up method, and guests start per game without an account and can convert to a regular member later.

Distinguishing sign-up and cancellation concepts

In STOVE integration, 'sign-up' and 'cancellation' are divided into the STOVE-account unit and the game unit. In particular, a user first entering a game and agreeing to the game terms is 'game sign-up', at which point a per-game identifier (GUID) is issued. STOVE sign-up (account creation) and game sign-up (agreeing to game terms) are separate, so clearly distinguish the four during integration.

Sign-up paths and methods

An account signed up with an email/SNS account to use STOVE services is called a 'regular member'. Regular-member sign-up can be done anywhere on the STOVE platform (web, STOVE app, PC client) and in mobile games, while guest entry is possible only in mobile games the game studio allows. The issued identifier and usage scope differ by member type.

Regular members can use all services—login, community, payment, security services, Customer Center inquiries, game cancellation/STOVE withdrawal, etc.
Guests can play mobile games and use in-game payment, the in-mobile-game community, game cancellation, regular-member conversion, and Customer Center inquiries, but can't use PC/web/app login, web/app community activity, STOVE payment, or STOVE withdrawal.

A GUID is also issued when a regular member signs up for a game, and since it's issued per game, one user can hold multiple GUIDs.

Sign-up Policy

Let's look at the sign-up procedure and the age criteria applied at sign-up. Sign-up is divided into regular-member sign-up and guest entry; a regular member holds both the platform ID number (MemberNo) and a per-game identifier (GUID), while a guest can hold only a per-game identifier (GUID).

Regular-member sign-up

When sign-up completes, a unique identifier (MemberNo) that identifies the user is issued and becomes the basis for using STOVE services such as games, payment, device registration, and coupons.

Guest-member entry

On first entry as a guest, a per-game unique identifier (GUID) is issued, and you can start the game without a separate regular-member sign-up procedure.

Terms agreement

A terms-agreement procedure is provided at STOVE-service/game sign-up. The terms agreed to here are divided into the STOVE service terms and the game terms. The STOVE service terms cover use of the entire STOVE platform, and the game terms cover use of an individual game.

Sign-up age and policy

The age criteria applied at sign-up differ by country/region. In South Korea, a guardian-consent/verification procedure is added for minor users.

Core Concepts

Usage Scenarios

Regular-Member Sign-up

Regular-member sign-up can be done with an email or SNS account. Selecting a sign-up method on the login screen starts the sign-up flow. Logging in with an already-signed-up SNS account is automatically handled as a login without separate sign-up. The sign-up flow differs by access region (South Korea/global) and sign-up method.

Email Sign-up (KR)SNS Sign-up (KR)Email Sign-up (Global)SNS Sign-up (Global)

Step	Screen the user sees	Details
1	Terms agreement	STOVE service terms, and consent to personal-info collection and use (required) Receiving useful game/service news (optional) Minors (under 19, at PC sign-up): game-use guardian consent and guardian personal-info collection/use consent items are added
2	(step 1/2) Enter email address	After entering the email address, validity/duplication checks run automatically If the email is already registered, a duplication notice is shown
3	(step 2/2) Enter password	Enter at least 8 characters including letters and numbers Validity is checked as soon as text is entered Match with the password-reentry field is checked in real time
4	Sign-up complete	MemberNo issued and auto-switch to logged-in state For web sign-up, a sign-up-completion notice email is sent (not sent for mobile SDK sign-up) STOVE nickname auto-issued
5	Email verification At first login after sign-up completes	For mobile games, email verification runs at first login after sign-up completes A 4-digit verification code is sent to the entered email (valid for 10 minutes), resend up to 5 times per hour; on 5 wrong entries the verification session expires (no resend for 10 minutes) (PC) For non-KR access, a captcha pop-up is shown before the verification code is sent
＋	Identity verification Added at PC sign-up (South Korea)	A step done only at PC/South Korea sign-up. Absent from the mobile-game sign-up flow Mobile-phone real-name verification is done (PASS, Toss verification supported) Sign-up not possible if 5 accounts are held with the same CI Under 19: after identity verification completes, guardian consent and guardian identity verification are additionally done

Guest Start and Regular-Member Conversion

Guests can start the game without sign-up and later convert to a regular member to protect their game data. Let's look at the guest-start and regular-member-conversion flows in order.

Guest start

Connect right away without sign-up using the 'Start as Guest' button at the bottom of the login screen. Whether guests are allowed is set by the game studio; if not allowed, the button isn't shown.

Regular-member conversion

Enter the regular-member-conversion screen via an in-game banner, button, or menu. The entry point is set directly by the game studio (e.g., payment attempt, device-registration attempt, reaching a certain level). When you create a regular-member account via email sign-up or SNS linking, the existing guest game data is linked automatically.

Signing In

Running the app or game shows the login screen. Login methods used within the last 90 days appear first, then the per-country default order applies.

Email / SNS LoginQR Code LoginOne-Time Login Number

Screen the user sees	Details
Email login	Enter the email address and password (case-insensitive, spaces auto-ignored) After mobile-SDK sign-up, email verification runs once at first web/app login
SNS login	Select an SNS button → SNS-platform authentication → login complete Logging in with an SNS account other than the one already signed up creates a separate new account
Keep logged in	Mobile games keep you logged in automatically with no option to choose (PC/web) if you choose to stay logged in, the login state is kept even after closing and re-entering the browser AT valid for 6 hours, RT valid for 30 days. Continuous use enables semi-permanent login
Duplicate-login handling	In multi-platform games, logging in on a new device automatically releases the existing device's login connection Only the last logged-in device stays active
Wrong-entry limit	On 15 wrong password entries, the account switches to protected state, released after identity confirmation (email-verified accounts: email verification / identity-verified accounts: identity verification); unverified accounts have login restricted for 5 hours Mobile games don't support instant login via a one-time login number (PC) on 6–9 wrong entries, instant login via a one-time login number is possible

Integration Overview

Overall Application Flow

From the planning team's decision on the application method to QA verification and deployment, integration proceeds in the following order.

Decisions Before Starting

These are items the game-planning department must decide directly before the game service starts. Deliver the decisions to the publishing technical contact to apply them to the SDK settings.

Whether to allow guests and the regular-member-conversion timing

Whether to allow guests is decided by the game studio; if allowed, a 'Guest Login' button appears on the login screen. To protect guest users' game data, we recommend showing a regular-member-conversion notice at the moments below.

Mobile-game SNS display methods and order

For mobile games, the game studio can set the SNS methods and order shown on the login screen. PC games are applied across the board by the platform, so no separate setting is needed. It follows the per-country default order, but a method the user used within the last 90 days appears at the very top first.

Target country	Default display order
South Korea	EmailGoogleFacebookAppleNaverSteamLine
United States, Canada, UK, Germany, France, Russia, Brazil, Australia, etc.	EmailGoogleFacebookAppleSteamLineNaver
Japan, Taiwan, Thailand, Macau	EmailGoogleFacebookLineAppleSteamNaver
Other global	EmailGoogleFacebookAppleSteamLineNaver

Role Division

Distinguishing what STOVE handles and what the game studio implements in login/sign-up makes it easier to communicate with the dev team. The login screen and sign-up flow are included in the SDK Auth UI, so the game studio doesn't need to implement a separate login screen.

What the STOVE platform provides8

Login-screen, sign-up, and terms-agreement UI (SDK Auth UI / email, SNS, guest)

Sign-up-method display control

Domestic and overseas identity-verification and guardian-verification handling

Global age-limit blocking

Account-protection measures for wrong password entries

PC-environment login convenience features (QR login, one-time login number)

MemberNo/GUID issuance and management

Access Token/Refresh Token issuance and renewal

What the game studio must implement3

In-game regular-member-conversion entry-point UI

Multi-platform duplicate-login exception handling

Real-time User Access Token validation logic (no caching)

Required-implementation details

① Handling multi-platform duplicate login

For security, STOVE activates only the most recently logged-in device and automatically expires the existing device's session. When the existing device's client receives a token-expired error, you must implement exception handling that safely disconnects the game, moves to the title screen, and shows a notice pop-up. (recommended text: "A login was detected on another device, so the game will close.")

② Real-time User Access Token validation

To prevent abuse, don't store (cache) the session token on the game server. You must call the STOVE authentication server on every user API request to check in real time whether the token is valid.

③ Token-validity reference

AT/RT expiry handling is done automatically by STOVE, so the game studio doesn't need to implement it separately. The Access Token (AT) has a 6-hour validity and STOVE auto-reissues it on expiry, and the Refresh Token (RT) has a 30-day validity and auto-renews with continued access, keeping you logged in.

Environment Distinction

Always run integration tests in the Sandbox environment first, then apply to the Live environment after verification completes.

Checklist

Before the game launches, check the items the game studio set or implemented directly. STOVE handles the login/sign-up screens, age limits, and authentication, so you only need to check the items below.