- Last Updated
Guide to the integration scope and workflow for mobile, PC, and web environments supported by the STOVE platform.Supported Platforms Guide
The STOVE platform supports three integration methods depending on the game service environment: mobile, PC online, and web. Since the SDKs used and the required integration items vary by environment, please check the integration details according to your service characteristics.
To release a mobile game, you need to implement common features such as user authentication, billing, promotions, and notifications. The STOVE platform provides features like member registration and authentication, payment systems (billing), promotions, push notifications, and community in the form of SDKs and server APIs, allowing game companies to implement most functions simply by calling the SDK and integrating the APIs without direct development.
We provide STOVE SDKs for each game engine and STOVE server APIs. The SDK supports Unreal / Unity / Native engines, and the server API is provided in the form of Rest API / Event Callback API.
| Category | Type | Integration Item | Required |
|---|---|---|---|
| Authentication | STOVE SDK | Sign-up, Authentication (Email, Guest, 3rd-party, etc.), Profile Changes, STOVE Account Deletion | Required |
| (Server) Access Token Validation | Secondary validation of the User Access Token acquired from the client on the server | Required | |
| (SDK/Server) Identity Verification | Provides identity verification features (e.g., mobile phone) for specific flows like server transfers or new character creation | Optional | |
| Payment | STOVE SDK | Integration of in-game direct purchase payment window for paid items | Required |
| Billing | (SDK) Abnormal Refund Repayment Popup | Integration of STOVE repayment store feature when users with abnormal refunds access the game | Optional |
| (Server) Payment Item Delivery Processing | Validation via billing middleware after user payment completion, and request to game server to deliver paid items | Required | |
| Promotion | STOVE SDK | Support for popups, coupons, push notifications, and community integration | Required |
| (Server) Itembox Integration | Processing receipt of reward items (Itembox) on the game server after participating in STOVE coupons and web events | Required | |
| Character | (Server) STOVE Character Integration | Synchronizing character information used in the game with the platform for use in displaying nicknames on the web/community and for PC billing RM checks | Required |
| Security | (SDK) Mobile Security Module | Prevent app tampering and block abnormal access/manipulation via the STOVE mobile security module | Required |
Mobile integration proceeds in the following 5 steps.
- SGP
- Developer
- Developer
STOVE Partners is the back office used for service management and operation.
Everything from app information registration to QA environment operation is handled through Partners.
PC integration covers the entire technical flow from a game entering the STOVE platform to being serviced. It includes overall integration procedures and precautions such as integration items with the game client and server, SDK usage, launcher settings, authentication, payment, and additional features.
The items that require integration in the PC environment are as follows.
| Target | STOVE Integration Items | Details | Required |
|---|---|---|---|
| Launcher | Execution Method | Running PC games via STOVE Launcher | No separate integration required |
| SDK | Game Engine and SDK Version | PC SDK Version (Unreal / Unity / Native) | Required |
| Authentication | (SDK) Access Token Retrieval | Retrieve Game User Access Token received via launcher | Required |
| (Server) Access Token Validation | Secondary Authentication Secondary verification of the User Access Token received via launcher on the server | Required | |
| Billing | (SDK) Billing Integration Method | 1) Direct Payment (Game Item Purchase) Method Direct payment for items sold in-game (Required for multi-platform) 2) Select from Game Currency Platform Payment Methods Method where the game's secondary currency (game cash) is managed by the platform | Required |
| (Server) Payment Item Provision Processing | After user payment is complete, validate via billing middleware and request paid item provision to the game server | Required | |
| Additional Features | (SDK) Optional Shutdown | (Korea) Usage restriction during specific times of the day for games for users under 19. Send shutdown events during gameplay to the game server | Required in Korea |
| (SDK) Over-immersion Prevention | (Korea) Display notification message every hour regarding elapsed game usage time (Based on Article 12-3 of the Act) | Required in Korea | |
| (Server) Membership | Member information inquiry, member sanction information inquiry | Optional | |
| (Server) Character | If character information used in the game is synchronized with the platform, it is used for displaying nicknames on the web/community and for PC billing RM checks. Multi-platform can reuse mobile character integration server code | Required for multi-platform | |
| (Server) Item Box Integration | Processing receipt of reward items (Itembox) on the game server after participating in STOVE coupons and web events | Required |
PC integration proceeds in the following 5 steps.
- SGP
- Developer
- Developer
Multi-platform games can reuse mobile integration assets.
Server APIs such as character integration and Item Box operate with a common structure for both mobile and PC. If a game has already completed mobile integration, development on the PC side can focus on the launcher and SDK sections.
By integrating web services (official website, etc.) through the STOVE platform, you can utilize key functions such as authentication, game execution, membership, characters, coupons, and web logs on the web. Web integration is provided via GNB or API methods without a separate SDK, and you can select only the necessary functions according to the service characteristics.
The items that require integration in the web environment are as follows. Authentication and game execution are mandatory, while the others are optional depending on the service characteristics.
| Category | Type | Integration Item | Mandatory |
|---|---|---|---|
| Authentication | GNB Method / Login URL Method | Utilize STOVE authentication on the web. The GNB method allows for quick integration, while the URL method is suitable for custom UI configurations. | Mandatory |
| Game Launch | STOVE JS Service Method / API Method | Download and launch the launcher from the web. Launch the game while logged in on the web without needing to log in to the launcher. | Mandatory |
| Member | (Server) Member Information API | Verify user authentication token validity and retrieve member information. | Optional |
| Character | (Server) Character API | Display character information used in the game on the web. Change the main character name displayed on the STOVE community, etc. | Optional |
| Billing | (Server) Billing API | Retrieve game cash balance information for the logged-in account. | Optional |
| Coupon | (Server) Coupon API | Register coupons issued by the STOVE platform on the web to provide in-game rewards (items, cash, etc.). Choose between the direct delivery method or the item box reception method. | Optional |
| Web Log | (Server) Web Log API | Record event logs on the web. Check them via STOVE Analytics. | Optional |
STOVE web services operate based on registered application (app) information. Therefore, you must register information for each service in advance via Partners.
| Item | Description |
|---|---|
| Basic Service Information | Register basic information required for WEB service integration, such as GAME_ID and launcher. |
| Terms and Conditions Information | Register terms and conditions required for game execution (manage terms type, exposure, and content). |
| Coupon Issuance | Register coupon policies and issuance via Partners when integrating coupons. |
To check registration information, you must first be registered as a partner and have been granted menu access permissions.
You can check how to register as a partner and grant permissions in the onboarding procedure guide.
Web integration proceeds in the following 5 steps. Select only the necessary items for each function according to the service characteristics.