# Add Information about Purchase Merchant POST /v2/shops/:shop_uuid/purchases/:purchase_uuid/merchant The request adds information about a merchant who provides purchase items within a shop. The request is applicable to shops which act as aggregators. Note, that even though the parameters in the request body are optional, at least any one of the following parameters is required for successful request processing: merchant_name, merchant_registry_code, merchant_order_reference, merchant_domain_name. Endpoint: POST /partner/v2/shops/{shop_uuid}/purchases/{purchase_uuid}/merchant Security: bearerAuth ## Path parameters: - `shop_uuid` (string, required) The unique identifier of the shop. Example: "38571c75-2590-4c81-8252-531613c96363" - `purchase_uuid` (string, required) The unique identifier of a specific purchase. Example: 1234 ## Request fields (application/json): - `merchant_name` (string) Name of the merchant who is connected to Inbank via an aggregator. - `merchant_registry_code` (string) Merchant's registry code, consisting of eight to eleven digits. - `merchant_order_reference` (string) Order reference of the merchant. - `merchant_domain_name` (string) URL of the merchant. - `merchant_mcc_code` (string) 4-digit merchant category code listed in ISO 18245 for retail financial services. This code is used to classify a business by the type of goods or services it provides. ## Response 401 fields (application/json): - `message` (string) Unauthorized Example: "unauthorized" ## Response 403 fields (application/json): - `message` (string) Unauthorized access Example: "User is not authorized to access this resource with an explicit deny" ## Response 404 fields (application/json): - `message` (string) Not Found Example: "purchase_not_found" ## Response 422 fields (application/json): - `message` (string) Unprocessable Entity ## Response 500 fields (application/json): - `message` (string) Internal server error Example: "internal_server_error" ## Response 204 fields