A merchant is the payment and legal tenant in Flint: it owns the processor account, settlement details, and business profile. The public merchant surface is merchant-scoped: you read and update the authenticated merchant, and external API keys stay bound to exactly one merchant.
A merchant may optionally belong to an organization for hierarchy and settings inheritance; a merchant without an organization_id is a valid standalone tenant. payments, payouts, and requirements report current readiness, while observed_at says when Flint evaluated it. onboarding_status, has_past_due, and current_deadline_at provide the related account state. Use the onboarding and account management surfaces to resolve outstanding requirements.
For creating and verifying merchants programmatically, see the API and agent onboarding guide.
The merchant profile and logo share version. Send the last-read value as expected_version on PATCH to reject a concurrent profile edit with MERCHANT_CHANGED. A logo change advances the same version as contact, address, metadata, and business-profile changes. Readiness changes do not advance the profile version.
