Skip to main content
POST
Create Merchant

Overview

The Create Merchant endpoint allows Payment Aggregators (PSPs) to programmatically onboard sub-merchants. It creates a new merchant account with company details, settlement bank information, and contact details. After creation, the sub-merchant status depends on the environment:
  • Production: Status is set to PENDING (requires approval)
  • Non-production: Status is set to APPROVED (auto-approved for testing)

Request Parameters

Required Parameters

  • company_details: Company registration, business information, and contact details
  • settlement_details: Bank account details for settlements

Parameter Definitions

Top-level

Company Details

Notes:
  • When same_as_registered_address is true, communication address fields are auto-populated from registered address.
  • Multiple business categories can be comma-separated (e.g., "E-commerce (physical goods & cross-border shipping),SaaS / subscriptions / recurring billing").

Settlement Details

Examples

Response Examples

Error Codes

Implementation Notes

Merchant Status Flow

  • PENDING → Created, awaiting approval
  • IN_REVIEW → Under compliance review
  • APPROVED → Active, can process payments
  • CHANGES_REQUESTED → Additional information required
  • REJECTED → Application rejected

Country Names

Country fields (registered_country, communication_country, bank_country) must use the full country name (e.g., "India", "United States", "United Arab Emirates").

Phone Number Format

Phone numbers must include the country code in E.164 format (e.g., +919876543210, +14155551234).

Business Category

Multiple categories can be comma-separated. When "Other" is included, business_category_other must provide a description.

Authorizations

X-Client-ID
string
header
required

Client Application ID - Your unique application identifier used to authenticate API requests. You can find your Client ID in the Developer Settings section of the merchant dashboard.

X-Client-Secret
string
header
required

Client Secret Key - Your secret key used alongside the Client ID for secure authentication. Keep this confidential and never expose it in client-side code. Available in the Developer Settings section of the merchant dashboard.

X-API-Version
string
header
required

API Version - Specifies which version of the API to use (e.g., '1.X.X', '2.X.X', or '3.X.X'). This header allows you to control which API version your integration uses. Default version information is available in the Developer Settings.

Body

application/json

Merchant details to create

settlement_details
object
required
company_details
object
required

Response

Merchant created successfully.

success
boolean
required

Indicates if the request was successful

message
string
required

Response message

data
object
required