Skip to main content
PATCH
Update Merchant

Overview

The Update Merchant endpoint allows Payment Aggregators (PSPs) to update an existing sub-merchant’s company details, settlement information, contact details, and business information. This is a partial update (PATCH) — only include the fields you want to change. Fields not included in the request will remain unchanged. Important: Updates are only allowed when the sub-merchant is in PENDING or CHANGES_REQUESTED status. Merchants in other statuses (APPROVED, IN_REVIEW, REJECTED) cannot be edited.

Request Parameters

The request structure mirrors the Create Merchant endpoint. All fields are optional for partial updates.

Parameter Definitions

Top-level

Company Details

All fields from the Create Merchant are accepted, but none are required. Only include fields you want to change. Key fields: For the complete field reference, see Create Merchant — Company Details.

Settlement Details

All fields from the Create Merchant are accepted. Only include fields you want to change.

Examples

Response Examples

Error Codes

Implementation Notes

Editable Statuses

Only sub-merchants in these statuses can be updated:
  • PENDING — Initial state after creation
  • CHANGES_REQUESTED — After review, when additional information is needed
Sub-merchants in APPROVED, IN_REVIEW, or REJECTED status will return a validation error.

Partial Updates

This endpoint supports partial updates — only send the fields you want to change. Omitted fields retain their current values.

Address Handling

When same_as_registered_address is set to true, communication address fields are automatically copied from registered address fields. If you update registered address fields and want communication to match, include same_as_registered_address: true.

Validation

All the same validations from the Create Merchant endpoint apply:
  • website must include https:// prefix
  • phone_number must be E.164 format
  • business_category, business_mode, international_org_type, monthly_avg_transaction_volume must use valid enum values
  • mcc must be comma-separated 4-digit codes
  • business_category_other is required when category includes “Other”

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.

Path Parameters

merchant_id
string
required

The ID of the merchant to update.

Body

application/json

Merchant update request - only include fields to update

Request body for updating merchant - only include fields to update

company_details
object

Company details to update

settlement_details
object

Settlement details to update

Response

Merchant updated successfully.

success
boolean
required

Indicates if the request was successful

message
string
required

Response message

data
object
required

Contains the updated merchant fields