Marketplace
Update Marketplace Settings
Update marketplace profile details, default commission rate, and marketplace notification settings.
PATCH
Intro
Updates your own marketplace’s public business details, default commission rate, and payment-notification preferences — as opposed to any one sub-merchant’s data.Context
This is the operator-level counterpart to Update Merchant: that endpoint changes a specific sub-merchant’s profile and commission override, this one changes your business profile and the default commission rate every merchant without an override inherits (see the inheritance behavior described in Link Merchant). Per-merchant overrides on top of this default are set via Update Commission.Hows
Request Body
At least one field is required.string
Marketplace business name.
string
Marketplace public email address. Must be unique across Khaime accounts.
string
Marketplace public phone number.
string
Marketplace country name.
string
2-letter ISO country code, for example
NG, US, or GB.string
Marketplace website URL. Must be a full absolute URL.
string
Public marketplace description.
number
Default commission rate for the marketplace, expressed as a decimal between
0 and 1. For example, send 0.08 for 8%.object
Marketplace payment notification settings. When provided, include at least one setting.
Response
Behavior
Profile and commission fields are partial updates — omitted fields are left unchanged.notification_config is merged with the existing config, so you can update one notification setting without affecting the other. Unset notification keys default to true at send time.
commission_rate here updates the marketplace default commission rate. To override commission for one specific sub-merchant, use Update Merchant or Update Commission.
Notification settings apply only to marketplace charges and affect all payment gateway webhook processing from the next successful payment event onward.
Error Codes
Requests that fail Khaime’s schema validation (no fields provided, invalid email format,commission_rate out of range, empty notification_config) return 422. business_email already in use is caught at the application level and returns 400.
Whys
Bundling profile, default commission, and notification preferences into one endpoint reflects that these are all “how my marketplace presents and behaves by default” settings, distinct from anything about a specific merchant. Mergingnotification_config instead of requiring both keys every time means you can flip one notification toggle without having to know or resend the current value of the other.
