Skip to main content
An organization is the top-level boundary for everything you sell on Macropay: products, customers, checkout, payouts, and webhooks all live inside one. Because Macropay is the Merchant of Record, each organization is also the unit we use to remit sales tax and VAT on your behalf — so the customer’s bank statement shows the right seller, and the right entity’s books stay clean. Most builders eventually need more than one. You can spin up as many as you like from a single login and switch between them in two clicks.

​
When to use more than one

Separate brands

Ship a SaaS product and a paid newsletter without mixing their catalogs, customers, or payout schedules.

Client work

Run a billing org per client. Each gets isolated revenue, refunds, and a clean MoR tax trail.

Per-agent billing

Give each AI agent its own org to track agentic margin — billed revenue vs. AI cost — without cross-contamination.

Sandbox vs. live

Keep experiments walled off from a production org while you validate pricing or metered events.

​
Create and switch between organizations

1

Start with your first organization

If you haven’t yet, sign up on Macropay. The org you create during onboarding becomes your default workspace.
2

Open the organization menu

From the dashboard, click the menu in the bottom-left corner and choose New Organization.
3

Name and describe the new organization

Fill in the details for the new org — its name and slug determine the public-facing identity your customers will see at checkout.
4

Add your first product

Every org starts empty. Create a product to make it sellable — one-time or subscription, both use the same API and data model.
5

Done — the organization is live

Your new organization is ready to take payments, with tax and PCI handled for you.
6

Switch between organizations

Reopen the bottom-left menu and select any organization to switch context. Products, customers, and payouts swap instantly.
Organizations are fully isolated. Products, customers, payouts, webhooks, and access tokens belong to exactly one org and never leak across the boundary.

​
Programmatic access per organization

Each organization issues its own organization access tokens (OAT). Scope a token to one org and every API call lands in that workspace — handy when you automate per-brand or per-agent billing.
Pair one OAT per agent with the Signals API to attribute activity and outcome events to the right organization, then read agentic margin per agent without any manual reconciliation.