Skip to main content
A brand is OwnPay’s unit of multi-tenant isolation. When you create a brand, you get a fully independent merchant entity - its own payment gateways, checkout domain, visual branding, staff team, API keys, customer database, and double-entry ledger - all walled off from every other brand on the same OwnPay instance.

​
Brand isolation model

Every database query is scoped to the active brand’s merchant_id. Staff in Brand A cannot see Brand B’s transactions, customers, or settings. No cross-brand data leakage is possible.

​
Brand vs platform

Platform (OwnPay instance)
  • Master administrator account
  • System-wide settings and plugins
  • DNS and SSL management
  • Database server and Redis
  • The single codebase running everything
Brand (merchant tenant)
  • Isolated customers and transactions
  • Independent gateway credentials
  • Separate API keys and webhooks
  • Custom domain and branding
  • Its own ledger and balance reports
The platform is the infrastructure. Brands are the merchants running on that infrastructure.

​
Per-brand configuration

Each brand independently controls:
Ledger accounts are also strictly scoped to a brand. A balance in Brand A’s cash account never appears in Brand B’s reports.

​
Common use cases

Last modified on August 25, 2026

Related topics

OwnPay Architecture: PHP Core, Middleware, and PluginsRoadmap - OwnPay Release Milestones and Upcoming FeaturesList TransactionsGlossaryQuickstart - Accept Your First Payment in 5 Minutes