71. Reach Kakao
- kate.psy (Unlicensed)
- KG_SDKDEV
Guide how to use Reach Kakao.
What is Reach Kakao?
If you are developing games over the age of 19, you can get a user's age information by using authentication API.
In the game of GoStop and poker, there are legal limitations on the purchase in the game. Use this function, and you can set limit same user can not purchase large amount of game goods.
Implemetation methods
The KakaoGameSDK supports Reach Kakao interactions in two ways:
Authenticate at a specific time
Authenticate in Kakao login process
Developers can choose the appropriate method based on their game.
For users who have completed their own authentication, their authentication will automatically proceed once a year in the KakaoGameSDK.
Authenticate at a specific time
This is used when the developer wants to proceed with the authentication at a certain point (eg, shop entry).
When a user logs in, he has already authenticated himself but he is underage, his login will fail.
If the user has not yet authenticated himself or if the user has passed 365 days since the authentication, the login succeeds.
Authentication Status | Description | Login Result |
|---|---|---|
Unknown | A user is not yet authenticated. | Success |
Underage | A user has already authenticated but he is underage. | Fail |
Adult | A user has already authenticated and he is adult. | Success |
At a certain point when you want to authenticate, you can call KGKakaoProfile.requestAgeVerification API. (hereafter referred to as the authentication API)
Please refer to the figure as below.
If the result is the underage after completing SMS authentication, an UnderAgePlayer error will be returned.
At that time, you should quit your game after expose the guidance message to the user and call logout.
If that user logs in again with the same account, the login fails and the game ends automatically because of the age information.
2. Authenticate in Kakao login process
The KakaoGameSDK handles personal authentication during the Kakao login process. In this case, you don't have to do anything special.
If you want to authenticate in this method, add 'key = "ageAuthOnLogin"' to kakao_game_sdk_configuration.xml and specify 'value = "true"'.
Ex)
<?xml version="1.0" encoding="UTF-8"?> <configuartion-list> <configuration key="appId" value="YOUR_APP_ID" /> ... <configuration key="ageAuthOnLogin" value="true"/> </configuartion-list> |
|---|
After the SDK handles the authentication internally, if the result of the authentication is the underage, the user is exposed to a warning popup and the game is terminated.
If the user is a adult, login will succeed. Please refer to the figure below for the work that the SDK handles internally.
Implementing purchase restrictions
If your game is legally required to implement a one-person purchase restriction, the game must implement the following processes, which are essential.
CI values are used to distinguish the user with multiple IDs as one person. The user who has completed the authentication of himself gets one CI value per person.
You can get the CI value of the user by calling KGLocalPlayer.getCurrentPlayer after proceeding with personal authentication.
What is CI? CI is a value that allows one user to be identified as one user when he or she has generated multiple IDs.
You can identify users by checking the CI value so that you can restrict users who have a number of Ids not to purchase goods when the payment amount per person is legally set.
In the case of a game that requires such an limit, you must implement a purchase constraint by storing the CI value for each game player. You have to manage CI value and purchase amount on your game DB.