This document walks you through frequently asked questions you may have when you integrate Kakao Sync into your service.
If you cannot find such solutions, check Kakao Login > FAQ or search your question by clicking the Search icon at the top right of the Kakao Developers. If you cannot find the answer or have further questions, visit the forum for developers called 'DevTalk' and feel free to ask questions.
To change the DevTalk interface language to English, see How can I change the DevTalk interface language?.
When you apply Kakao Sync, your service can prompt a single Consent screen, called Simple Signup, that allows your service to obtain consent to all of the service terms, provision of personal information to third-party, and channel addition. Your service can also get the customer data that is required for a sign up unlike Kakao Login (Basic social login), and thus implement a signup process more easily with a few clicks.
To see more detailed differences, refer to Kakao Login > Concepts.
Of course. When you apply Kakao Sync, you can use the extended features of Kakao Login including Simple Signup. Refer to Kakao Sync for more details.
If you apply Kakao Sync Simple Signup, the signup process becomes very easy. You can get consent to the service terms and receiving marketing information through Kakao Talk Channel from users, and ask users to input their user information on the Consent screen. Kakao Sync also allows you to use other Kakao Open APIs, such as the Kakao Talk Social API, so that you can retrieve a list of Kakao Talk friends who use the same service or share product information through Kakao Talk Sharing.
Refer to Kakao Sync for more details.
Yes. After applying the Simple signup, the Consent screen is displayed again even to the Kakao Login users who logged in with Kakao. Thus, the users must consent on the Simple signup consent screen at least once more.
When a user consents on the Simple signup consent screen, the user's
user_id is passed. If the
user_id matches tge service user ID of a Kakao Login user, Kakao considers the user has already been signed up through Kakao Login, and the user information is updated to the information provided through Kakao Sync.
For more information, refer to Map existing users.
No. Kakao never accesses your service data. Kakao only provides information or performs internal processing in the Kakao platform as your service requests an API.
Yes. You can apply Kakao Sync to your test app, which does not affect the service you are operating. To see how to set a test app, refer to Test app.
No. If you already have a Biz app with which Kakao Login is integrated, do not create a new app to adopt Kakao Sync and use the existing app with its app key that your service is using because each app has its own app keys that are used to identify apps and permission.
If you create a new app, your service users must log in or sign up for your service once again, and then new
user_ids are assigned because
user_id is issued by app, not by user. Thus, you cannot use the information of the existing user who is linked to your existing app through Kakao Login.
Yes. You can implement the process using the Auto-login feature. Depending on the user's signup status, you can show different pages, either a page with a logged-in status or a page with a logged-out status. This feature only works in the Kakao Talk in-app browser.
You can use the Simple Signup function only from the app that has been passed the review. If 'Simple Signup' is inactivated in your app settings, your app does not have permission, and thus you must request Kakao Sync review.
If you are already using Kakao Sync, log in with the Kakao Account with permission granted, and select the app that is using Kakao Sync.
To figure out who has already been using the service, use one of the unique user information saved in Kakao Account received from Kakao. Usually, email or phone number is used. However, email and phone number cannot be identifiers because users can change their email or phone number at any time. Thus, we recommend using information that the Kakao platform provides as an identifier, service user ID. When a user's Kakao Account is linked to a service, Kakao issues a unique numeric value. This value issued for each user never changes even when the user deletes the account and re-create an account, which helps your service to identify users and check if a user has already been signed up.
It is difficult for Kakao to guide a specific method to handle this situation because each service has all different membership systems, user flows, and policies. Your service must create its own rules and policies to map users with the existing users to prevent users' confusion. Refer to Map existing users for more details.
No. Kakao Sync Simple Signup allows users to easily sign up without going through multiple signup pages. However, you may need to get consent to service terms or request user information additionally depending on the service situation. In this case, request consent or information on your service page after a user logs in with Kakao.
Make sure to implement a process to collect additional user information only when the information is required. Otherwise, users may give up signing up in the middle of the process for collecting information. Refer to Manage user accounts for more details.
To delete a user's Kakao Account in your service, the account must be unlinked from all of the services. To figure out who attempts to delete the Kakao Account, set unlink callback, which notifies you of the user's unlink status. When you get unlink callback from Kakao, you can process the user's account in your service.
Even when a user deletes a Kakao Account in the service that applies Kakao Sync, the user still can see the service name on the Manage Connected Service page. If an account is not unlinked from the service, the account is not completely deleted. Thus, request unlink API for the user to unlink the user's account from your service.
You can connect your app and channel only under the following conditions. If not, your channel is not displayed in the channel list on the page for connection between app and channel.
In the following cases, the option to add your Kakao Talk channel is not displayed.
The Consent screen is prompted only when you request consent to:
If the requested service term is not satisfied with both conditions above, the consent screen is not prompted even though you call the Getting consent to desired service terms API.
To resolve this problem,
After completing two things above, you can ask for consent to the service term by calling Getting consent to desired service terms API at the moment when the consent is required.
Even though a user signs up through Kakao Sync Simple Signup, you must register the user as a member in your service's member database. If not, then the user is not completely signed up. Because Kakao cannot access your member database, we cannot add new member information ourselves. Make sure to implement a process that stores new user information in the service database internally.
Refer to Manage user accounts for more details.
There are two reasons for this issue:
When a user deletes the account of the Kakao Sync service, you must:
If not complete the two things above, the user's account is not completely deleted. Make sure to delete the user information from your member database because Kakao cannot access your service database for deletion.
Even though users unlink from the service app, their status with the Kakao Talk Channel remains active. If your customers inquire about this issue, guide them to block the Kakao Talk Channel on the Kakao Talk app.
Check if the user information is completely deleted from your service's member database when the user deletes the account. For the user who used the same service with the same Kakao Account, the same user ID is assigned when the user is linked again. When unlinking from the service after deleting an account, all information related to the use of service is deleted, but the ID is reissued with the same value. If the information of the preexisting user remains, it may cause a problem. Thus, you must delete their information as soon as they delete the accounts in accordance with the service policy and related laws.