- Last Updated
Onboarding Procedure Guide
This is the common workflow from applying for onboarding to launching your service.

Detailed workflows vary depending on the service onboarding contract and platform type.
Required preparation items and the scope of inspection may vary based on contract terms and platform type.
If the contract terms include SGP infrastructure and server setup, server infrastructure construction and performance testing procedures are added to the mobile, PC online, and multi-platform onboarding processes.
This is a conditional procedure added to specific onboarding types.
In this case, we first confirm the construction scope and performance test standards through an architecture review, then proceed with construction and verification tailored to the QA and live environments.
This is the onboarding workflow based on Android and iOS market releases.
For contracts that include SGP infrastructure and server setup
In addition to this onboarding workflow, architecture review, server infrastructure construction, QA environment verification, and performance testing are additionally conducted.
Perform performance testing if SGP infrastructure/server setup is included in the contract terms.
Implementing integration features is a mandatory step
This is the stage where the STOVE technical team and the partner company review the platform integration specifications together. If the contract includes infrastructure/server construction, an architecture review will be conducted during the technical meeting, and the scope of construction and performance test criteria will be finalized.
This is the PC game onboarding flow based on the STOVE launcher.
For contracts that include SGP infrastructure/server construction
In addition to this onboarding flow, architecture review, server infrastructure construction, QA environment verification, and performance testing are additionally conducted.
If the contract includes SGP infrastructure/server construction, proceed with performance testing
Operate on mobile and PC online simultaneously, with a structure where the PC integration process is added to the mobile development workflow.
For contracts that include SGP infrastructure and server setup
In addition to the onboarding flow, architecture review, server infrastructure setup, QA environment verification, and performance testing are also conducted.
| Category | Description |
|---|---|
| Workflow | For simultaneous operation via mobile + PC online expansion. A structure where the PC integration process is added to the mobile development workflow. |
| Platform Type Settings | The platform type in the basic service information must be registered as a mobile game only. Please be careful not to select other game types. |
| Integration Order | Mobile integration first, followed by PC integration is recommended. ① Mobile area (SDK + Mobile Billing + Common APIs) integration first → ② PC area (SDK + Billing) integration. |
Caution when setting platform type
The platform type in the basic service information must be registered as Mobile Game only. Please be careful not to select other game types.
All 12 steps of the onboarding process are grouped into 4 phases.
These are the developer consoles for each launch market.
It is a back-office for partners where vendors manage service registration and environment settings.
Permissions are managed based on roles.
Operated by separating into two environments: Sandbox and Live.