Registration Process

Step 1: Phone Number Registration

The user initiates registration by sending a request to POST /v2/mobile/signup, specifying the phone number and password in the request body.

🚧

When re-registering in the system, it is necessary to use a new phone number that has not been used before.

📘

💡The password must meet three conditions

• The password must be at least 8 characters long.

• The password must contain at least one digit.

• The password must contain at least one letter.

• The password must not be equal to the phone number.

• The password must not contain information from the user profile.

• The password cannot be the same as any of the previous five passwords.

• The password must not be too simple, for example, "12345678".

Step 2: Phone Number Confirmation

A SMS code is sent to the provided phone number for confirmation. The user confirms the phone number by submitting the verification code through the POST /v2/mobile/phone/confirm endpoint.

If the initial confirmation code is not received or its validity expires, the user can request a resend using the POST /v2/mobile/phone/verify/resend endpoint.

Upon successful confirmation, the system issues access tokens (access_token and refresh_token), allowing the user to authenticate.

• access_token: This token serves as a key for the client to gain access to secured resources.
• refresh_token: A special key that allows the client, whether it's an API or service, to obtain new access tokens without requiring the user to undergo a complete sign-in process.

Step 3: Account Creation

The system creates a user account, providing a unique userId.

Step 4: Adding Email Address

The user needs to add an email address to the account by sending a request to the PUT /v2/mobile/email/add endpoint.

Upon successful completion of the request with a 200 (OK) response code, the system automatically triggers the sending of a confirmation email. The email will be sent immediately after the request is successfully processed.

Step 5: Enter Personal Details

This step entails adding personal information to your profile, which is necessary to obtain KYC_0.

The PATCH /v2/customer/profile is used to send a request and update information in your profile.

The response with status code 204 No Content indicates that the request was successful, and there's no additional content to return.