For the complete documentation index, see llms.txt. This page is also available as Markdown.

Submerchant Update

This service allows you to update submerchant accounts by providing their necessary details.

In the process of updating submerchants, it's important to note that you cannot change the submerchant type. Once a submerchant is created with a specific type, it cannot be modified to a different type. Therefore, it's crucial to ensure that the correct submerchant type is selected during the initial setup.

All of the submerchant types are capable of update operations;

  • PERSONAL

  • PRIVATE COMPANY

  • LIMITED OR JOINT STOCK COMPANY

Update Submerchant

put

Updates an existing submerchant. The request body shape varies by submerchant type; one of three variants must be sent. The subMerchantType field is not included in the update body.

Header parameters
AuthorizationstringRequired

Authorization header; a signed hash value that starts with IYZWSv2 and is generated in Base64 format.

Example: IYZWSv2 YXBpS2V5OnNhbmRib....E0OGI1MTE=
Content-TypestringRequired

Request body content type.

Example: application/json
Body

Update fields vary by submerchant type. Do not send subMerchantType in update.

or
or
Responses
200

Successful response

application/json
statusstring · enumOptional

Result.

Example: successPossible values:
localestring · enumOptional

Response language.

Example: enPossible values:
systemTimeintegerOptional

Operation time (epoch ms).

Example: 1755857408023
conversationIdstringOptional

ID sent in the request.

Example: 123456789
put/onboarding/submerchant

Sample Codes

Last updated