Skip to main content

AuthResult

Data structure

caution

If the game uses the FirstLogin field to determine whether the player is a new user, when clearing data, the game needs to inform Player Network SDK to clear the relevant data.

FINTLAuthResult: Inherits from FINTLBaseResult, include login information.

NameTypeDescription
OpenIDFStringPlayer Network SDK unique user ID
TokenFStringUser token generated by Player Network SDK
TokenExpireint64Token expiration timestamp
For example, 1600844518
FirstLoginint32Whether this is the first login
-1: Unknown
0: No
1: Yes
UserNameFStringUser defined nickname
Genderint32Gender
0: Undefined
1: Male
2: Female
BirthdateFStringReturns empty, collection of player birthdate is not allowed according to compliance requirements
PictureUrlFStringUser avatar URL
PfFStringpf value
For Midas payment
PfkeyFStringpf key
For Midas payment
NeedRealNameAuthboolWhether real-name verification is required
ChannelIDint32Channel ID
ChannelNameEINTLLoginChannelChannel name
ChannelInfoFStringThird-party channel login information
JSON data, each Channel has its own value
BindListFStringLinking information
JSON data in array type
LegalDocumentsAcceptedVersionFStringThe accepted version of legal documents
DeleteAccountStatusint32Account deletion status
For more information, see DeleteAccountStatus.
DeleteAccountInfoStringReach out to the Player Network representative if DeleteAccountInfo is required
Delete account information, JSON data.
For more information, see DeleteAccountInfo.
TransferCodeFStringTransfer code
TransferCodeExpireTimeint32Expiration time for transfer code
DeleteLIAccountStatusintLEVEL INFINITE PASS account deletion status
For more information, see DeleteLIAccountStatus.
EmailstringEmail address

The ExtraJson in FINTLAuthResult contains the JSON strings for the protocol version and compliance result of the player queried from the backend.

DeleteAccountStatus

caution

Reach out to the Player Network representative to configure DeleteAccountStatus, otherwise DeleteAccountStatus returns -1.

ValueDescriptionRemark
0No account deletion or account deletion has been canceledAllow player to enter the game
1Account deletion cooling-off periodStop player login, prompt player whether to cancel account deletion and enter the game
2Account deletion completedStop player from entering the game
3Account deletion in progressStop player from entering the game
4Account deletion failedStop player from entering the game
-1Status not returned from backendRecommend allowing player to enter the game
-2Network unstable for the account deletion status serviceRecommend allowing player to enter the game
-3DMCS response data format is wrong (return status or err_code fields missing in JSON)Recommend allowing player to enter the game
-4Internal error (parameter verification is incorrect or configuration verification is not equal to internal authorization logic)Recommend allowing player to enter the game
-10 or -11Internal error in the account deletion status serviceRecommend allowing player to enter the game
>= 5UndefinedRecommend allowing player to enter the game
note

Games should review the consequences of allowing players to enter the game when the return value is negative, and if the game data may be impacted.

Stopping players from entering the game while the return value is negative may affect other players, and is therefore not recommended as an essential step in account deletion.

DeleteAccountInfo

JSON data:

{
"ret": 0, // int, return code, 0 indicates normal
"err_code": -10, // int, error code for INTL, games no need to pay attention
"msg": "", // error message, empty when the request is successful
"status": 0, // int, 0: no record or account deletion is cancelled; 1: cooling-off period; 2: account deleted successfully; 3: deleting account; 4: account deletion failed
"created_at": 12345678, // int64, timestamp when the account deletion request is created (when status is 0, timestamp is 0)
"target_destroy_at": 12345678, // timestamp to execute the account deletion (when status is 0, timestamp is 0)
"destroyed_at": 12345679 // int64, timestamp when the account is actually deleted (when status is not 2, timestamp is 0)
}

DeleteLIAccountStatus

ValueDescription
-1Account deletion query failed or status not returned from backend
0No account deletion records or deletion has been withdrawn
1Account deletion requested
2Account deletion succeeded
3Account deletion in progress |
4Failed to delete account