Organization and merchant

Onboarding begins by creating an organization and, under it, a merchant. The merchant is the entity that owns settlement destinations, configuration, and keys; merchant_id is the reference that every later surface carries.

Step 1 — Create an organization

The organization is the top-level account. Create it first; the merchant cannot be created without one. The principal that creates the merchant must be an owner of the organization.

An organization must be in a state that permits administrative operations for merchant creation to succeed. A suspended organization cannot create merchants — resolve the suspension first.

Step 2 — Create a merchant

Create a merchant under the organization. Supply:

• the organization it belongs to;
• a non-empty merchant name.

On success you receive a new merchant_id. The merchant starts in an initial created state and proceeds through the remaining onboarding steps before it can take live payments.

The organization a merchant belongs to is fixed for the lifetime of that merchant. It cannot be reassigned later.

What merchant_id is

merchant_id is your stable correlation key across the platform. It identifies the merchant on every downstream surface:

• payments you create are scoped to it;
• KYT requests Tekmerion sends you carry it;
• notifications and the Proof of Payment carry it.

Creating a merchant establishes identity only. It does not create payment, notification, or settlement configuration, and it is not proof that the merchant is ready to receive payments. The remaining onboarding steps establish that:

1. Receiving profile and whitelist — where funds may settle.
2. Factory authorisation — the signature that authorises settlement on-chain.
3. KYT endpoint setup — your compliance-decision endpoint.
4. Notification endpoints and API keys — delivery destinations and credentials.
5. Go-live checklist — everything that must be true before the first live payment.