Create Sub-merchant

PUT 
/api/v1/aggregator/merchants

Registers a new sub-merchant under the aggregator payment service.

In the payment facilitator model every sub-merchant must be registered before its first transaction. Sub-merchants with transfer-type products are active immediately after a successful call. Card products additionally go through card onboarding - the sub-merchant becomes eligible for card payments after verification completes.

When onboarding with any downstream acquirer fails, the sub-merchant record is not persisted and the call returns HTTP 400 with the failure reason.

Checksum

The server verifies the checksum by concatenating the values of all fields sent in the request body, in the order they appear in the JSON (excluding checksum), joined with |, with your Secret Hash appended at the end:

sha256({field1}|{field2}|...|{SecretHash})

Array values are flattened element by element in place of the field. The timestamp must be current - requests older than 60 seconds are rejected with HTTP 401.

This API is available only for services with the aggregation model enabled.

Request

Responses

200

Created sub-merchant

400

Sub-merchant onboarding failed - record rolled back.

401

Unauthorized - invalid checksum, stale timestamp or service without aggregation enabled.

422

Validation error - missing required fields (e.g. address for transfer-type products).