Update Sub-merchant
PATCH/api/v1/aggregator/merchants
Updates an existing sub-merchant identified by id or aggregator_mid. Changed data is propagated to the payment facilitator registration - keep sub-merchant data current, this is a scheme compliance obligation.
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
- 400
- 401
Updated sub-merchant
Propagation of the update failed - local record kept, retry after fixing the data.
Unauthorized - invalid checksum, stale timestamp or service without aggregation enabled.