UPI Setu - Merchant on-boarding - Setup merchant

Reading time — 2 minutes

#Setting up a merchant (Aggregator)

The merchant on-boarding APIs are only relevant for an aggregator. If you are an individual merchant, you can proceed to the merchant quickstart and either of our product pages UPI payments or UPI mandates.

You can use the following API, to on-board merchants in UPI Setu, by providing required business details for merchants and your aggregatorAccountId. The aggregatorAccountId will be shared with you as part of the aggregator on-boarding process.

Host	`https://umap.setu.co/api`
Method	`POST`
Path	`/v1/aggregators/merchants`
Header	`Authorization`: Bearer <insert_token_here> Generate an access token ↗ `Content-Type`—will be `application/json`
API reference	Setup a merchant ↗

The request payload shown below is the bare minimum that needs to be passed inorder to create a merchant on our platform

{
    "aggregatorAccountId": "328a928f-e277-4798-8e28-4b19a61a8a23",
    "businessName": "Setu",
    "franchiseName": "Setu",
    "legalName": "BrokenTusk Technologies Pvt Ltd",
    "businessType": "PUBLIC",
    "genre": "ONLINE",
    "mcc": "5432"
}

The standardAccountId parameter is optional and it is used to group merchants under a single organisation, when standardAccountId is not passed, the merchant is created under a new organisation.

These are some optional parameters that you can pass along in the request payload, which will overrides the default behavior

{
    "standardAccountId": "328a928f-e277-4798-8e28-4b19a61a8a22"
    
    "merchantType": "small", // default is large
    "onboardingType": "bank", // default is aggregator
    "acceptDeemedTxns": true, // default is false
    "paymentModes": [
        "savings"
    ], // defaults to aggregator.paymentModes
    "products": [
      "autopay"
    ], // defaults to aggregator.products
    "vpaHandles": [
        "pineaxis"
    ] // defaults to aggregator.vpaHandles
}

—

–

#Setting up a merchant (Aggregator)