Add Merchant

This API allows you to add a merchant, either for CLABE (Mexico) or CVU (Argentina) channels.

Endpoint Information

• Request Header: X-BH-TOKEN: ******

• Request Header: Content-Type: application/json

• Request Method: POST

• Request Path: /v2/merchant

• Authorization Required: Yes

Request Parameters

For CLABE Merchant (Mexico)

{
    "trench": "CLABE",                        // (string: Channel [CVU/CLABE])
    "merchantName": "Rrturo Tellez",         // (string: Merchant Name (Unique))
    "email": "[e-mail]",               // (string: Email (Unique))
    "merchantType": "COMPANY",                // (string: Merchant Type [PERSONAL, COMPANY])
    "remark": "",                             // (string: Remark)
    
    "curp": "ATA891028HDFNLR06",              // (string: CURP)
    "rfc": "",                                // (string: RFC)
    "cardIssueDate": "2019-06-01",           // (string: Card Issue Date (yyyy-MM-dd))
    "cardExpireDate": "2029-06-01",          // (string: Card Expiry Date (yyyy-MM-dd))
    "address": "Celle Lagu Wenner 50",       // (string: Address)
    "city": "Ciudad de Mexico",               // (string: City)
    "state": "CMX",                           // (string: State)
    "zipCode": "09060",                       // (string: Zip Code)
    "phone": "35580481683",                   // (string: Phone)
    
    "companyName": "Rrturo Tellez",          // (string: Company Name)
    "aliasName": "Rrturo",                    // (string: Alias Name)
    "companyType": "SC",                      // (string: Company Type)
    "incorporationDate": "2019-02-01",       // (string: Incorporation Date (yyyy-MM-dd))
    
    "birthday": "1988-07-02",                 // (string: Birthday (yyyy-MM-dd))
    "name": "Tellez",                        // (string: Name)
    "fatherSurname": "Rrturo",                // (string: Father's Surname)
    "motherSurname": ""                        // (string: Mother's Surname)
}

For CVU Merchant (Argentina)

{
    "trench": "CVU",                          // (string: Channel [CVU/CLABE])
    "merchantName": "tom",                    // (string: Merchant Name (Unique))
    "email": "[e-mail]",               // (string: Email (Unique))
    "merchantType": "PERSONAL",               // (string: Merchant Type [PERSONAL, COMPANY])
    "remark": "",                             // (string: Remark)
    
    "cuit": "20315085801",                    // (string: CUIT)
    "name": "tom"                             // (string: Full Name)
}

Response Structure

The response will include the following fields:

{
    "code": 200,
    "msg": "SUCCESS",
    "data": {    
        "merchantId": 1,                       // (number: id of the merchant)
        "country": "Mexico",                   // (string: name of the country)
        "merchantName": "Rrturo Tellez",      // (string: name of the merchant)
        "status": 1,                           // (enum: status of the merchant [1: authenticating, 2: normal, 3: authentication failed])
        "merchantType": 1                      // (number: merchant type [1: PERSONAL, 2: COMPANY])
        
    }
}

Example Response

{
    "code": 200,
    "msg": "SUCCESS",
    "data": {
        "merchantId": 1,
        "country": "Mexico",
        "merchantName": "Rrturo Tellez",
        "status": 1,
        "merchantType": 2
    }
}

Notes

• Ensure that either CURP or RFC is filled for CLABE merchants, and CUIT is filled for CVU merchants.

• The merchantType field indicates whether the merchant is a personal or company account.

• The status field reflects the current state of the merchant's application.