Merchant Registration Request

Merchant user input merchant 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 toke

Request

Canonical Path	/b2b/merchant/register/request
Method	POST
Authorization	Bearer <host_access_token>
Query Param	-
Content-Type	application/json
Content

{
    "phone": <String, not null>, 
    "name": <String, not null>, 
    "email": <String>, 
    "partnerId": <String>,
    "countryId": <String, not null>, 
    "sourceId": <String, not null>
}

// Example
{
    "phone": “081200001234”,
    "name": “Surya Abadi”, 
    "email": “[e-mail]”, 
    "partnerId": “0001”,
    "countryId": “ID”,
    "sourceId": “02001”
}

Response

Content-Type	Application/json
Content

{
    "merchantRegistrationId": <String, not null>, 
    "tokenPrefix": <String, not null>, 
    "username": <String, not null>, 
    "accountGroupId": <String, not null>
}

Description

Field	Description
name	Name of merchant
email	E-Mail address
phone	Merchant phone number
partnerId	Partner Id (will be given by E2Pay)
countryId	Country ID of merchant
accountGroupId	Account Group ID
merchantRegistrationId	Merchant Registration ID
tokenPrefix	Token Prefix
username	username