Customer Registration

This service are collection of api which will use customer accounts

Customer Registration

This service is used to initiate customer registration process by client host. After this service has been performed, customer will receive authorization email and SMS token to confirm the registration process.

1. Registration Request

Customer input customer data from mobile apps and mobile backend will be forward the request to INVAS. System will generate token and send email containing complete registration and send SMS token to customer.

Canonical Path

/b2b/customer/register

Method

POST

Authorization

Bearer <host_access_token>

Query Param

-

Content-Type

application/json

Content

{
    "phone": <String, not null>, 
    "name": <String, not null>, 
    "birthDate": <Date, not null>, 
    "birthPlace": <String, not null>, 
    "email": <String>,
    "gender": <Boolean, not null>, 
    "countryId": <String, not null>, 
    "sourceId": <String>,
    "accountGroupId": <String, not null>
}   
// Sample Code:
{
    "phone":081234567890,
    "name": “Septian Cahyo”, 
    "birthDate":1990-12-31, 
    "birthPlace": “Jakarta”, 
    "email": “email@gmail.com”, 
    "gender": true, 
    "countryId":”ID”, 
    "sourceId":01011,
    "accountGroupId":01
}

Description

Field

Description

expiryMinutes

Expiry Time for Token (in minutes)

expiryTimestamp

Expiry Time for Token

requestTimestamp

Request Time

phone

Phone number

active

Token activation status

tokenPrefix

Token Prefix

id

Registration Request Id

tokenType

Token Type

attempt

Attempt

username

Username

accountGroipId

Account Group ID

2. Complete Registration

This api used to complete the registration process

Canonical Path

/b2b/customer/register/confirm

Method

POST

Authorization

Bearer <host_access_token>

Query Param

-

Content-Type

application/json

Content

{
    "username": <String, not null>, 
    "password": <String, not null>, 
    "token": <String>
}

Description

Field

Description

username

Customer Username : phone number

password

Customer Password (must be hashed by using MD5 UPPERCASE)

token

Registration Token (using prefix, example = UhY1234)

3. Verify Username

This service is used to verify whether a username has already used or not

Canonical Path

/b2b/customer/auth/verifyUsername

Method

GET

Authorization

Bearer <host_access_token>

Query Param

§ username

Content-Type

-

Content

-

Description

Field

Description

username

Customer username : Phone Number

exists

Will be true if username already exists and false otherwise

4. Verify Email

This service is used to verify whether a username has already used or not

Canonical Path

/b2b/customer/auth/verifyEmail

Method

GET

Authorization

Bearer <host_access_token>

Query Param

§ email

Content-Type

-

Content

-

Description

Field

Description

username

Customer username : Phone Number

exists

Will be true if username already exists and false otherwise

5. Resend Registration SMS Token

This service used to resend customer registration SMS token.

Canonical Path

/b2b/customer/resend/registration/sms

Method

POST

Authorization

Bearer <host_access_token>

Query Param

-

Content-Type

application/json

Content

{
    "username": <String, not null>, 
    "phone": <String, not null>
}

Description

Field

Description

username

Username merchant: phone number

phone

Merchant phone number

6. Resend Registration Email

This service used to resend customer registration email.

Canonical Path

/b2b/customer/resend/registration/email

Method

POST

Authorization

Bearer <host_access_token>

Query Param

-

Content-Type

application/json

Content

{
    "username": <String, not null>, 
    "phone": <String, not null>
}

Description

Field

Description

username

Username merchant: phone number

phone

Merchant phone number

Last updated