Login Callback Information (AuthResult)

Data Structure

caution

Business needs to use FirstLogin field to determine if new user.Then business must also remind Player Network SDK to clear relevant data during file clearing.

FINTLAuthResult: Inherits from FINTLBaseResult and contains login information.

Name	Type	Description
OpenID	FString	Player Network SDK User Unique Identifier
Token	FString	Player Network SDK User Token
TokenExpire	int64	Token expiration timestamp For example, 1600844518
FirstLogin	int32	Is first login Unknown: -1 No: 0 Yes: 1
UserName	FString	Nickname
Gender	int32	Gender 0: Undefined 1: Male 2: Female
Birthdate	FString	Returns empty due to compliance not allowing collection of player's birth date
PictureUrl	FString	Avatar URL
Pf	FString	pf value Used for Midas payment
Pfkey	FString	pf key Used for Midas payment
NeedRealNameAuth	bool	Requires real name authentication
ChannelID	int32	Channel Number
channelName	EINTLLoginChannel	Channel Name
ChannelInfo	FString	Third-party channel login information JSON Data, values differ per channel
BindList	FString	Binding information JSON Data, array type
Accepted Version of Legal Documents	FString	Legal documentation version info
DeleteAccountStatus	int32	Account deletion status See DeleteAccountStatus for more info.
DeleteAccountInfo	String	If `DeleteAccountInfo' is needed, contact Player Network Assistant Account deactivation info, JSON data. See DeleteAccountInfo for more.
transferCode	FString	Visitor transfer code for special areas
Transfer Code Expiration Time	int32	Visitor transfer code expiration time for special areas
Delete LI Account Status	int	LEVEL INFINITE PASS account cancellation status See DeleteLIAccountStatus for more.
Email	string	Email address
Health Score	int	Current account security level. The higher the value, the more secure the account is.
Health Score Return	int	Return code. 0 indicates success.

The ExtraJson in FINTLAuthResult contains a JSON string with the user's protocol version and compliance status obtained from the backend.

DeleteAccountStatus

caution

For businesses that require DeleteAccountStatus, please contact Player Network Assistant for configuration. Otherwise, DeleteAccountStatus will return -1.

Value	Description	Note
0	No account deletion performed or account deletion canceled	Allow player to enter the game
1	Account Deletion Cooling-off Period	Block player login, prompt the player to decide whether to cancel the account deletion and enter the game
2	Account deletion complete	Do not allow player to enter the game
3	Account deletion in progress	Do not allow player to enter the game
4	Account deletion failed	Do not allow player to enter the game
-1	No account deletion status returned from the backend	Recommend allowing player to enter the game
-2	Account deletion status service network anomaly	Recommend allowing player to enter the game
-3	DMCS response data format is incorrect (missing return status or err_code fields in JSON)	Recommend allowing player to enter the game
-4	Internal error (incorrect parameter verification or configuration does not match internal authorization logic)	Recommend allowing player to enter the game
-10 or -11	Account deletion status service internal error	Recommend allowing player to enter the game
> = 5	Undefined	Recommend allowing player to enter the game

note

The game side needs to evaluate whether allowing players to enter when the return value is negative would have any other impact on the game data.

If players are not allowed to enter the game with negative return values, this may affect other players, so it is not recommended to treat this as a key path for account deletion.

DeleteAccountInfo

JSON data:

{
    "ret": 0, // int, return code, 0 means normal.
    "err_code": -10, // int, Player Network SDK error code, not needed by the game 
    "msg": "", // Error message, empty if the request was successful 
    "status":  0, // int, 0: no record or account deletion canceled; 1: cooldown period; 2: account delete successful; 3: account deletion in progress; 4: account deletion failed
    "created_at": 12345678, // int64, timestamp when account deletion request was created (timestamp is 0 when status is 0)
    "target_destroy_at": 12345678, // timestamp for executing account deletion (timestamp is 0 when status is 0).
    "destroy_at": 12345679 // int64, timestamp when account was actually deleted (timestamp is 0 when the status is not 2)
}

Delete LI Account Status

Value	Description
-1	Account deletion status query failed or backend did not return status
0	No account cancellation record or delete request has been withdrawn
1	Account cancellation requested
2	Account cancellation successful
3	Canceling account
4	Account cancellation failed