How organizations work
The parts of an organization, who can reach each one, how money moves and which credential each API takes.
An organization lets you sell Coritan products as your own. You decide what to sell and at what price, your customers sign in on your storefront, and your team looks after them. Coritan runs the resources, takes the payments as merchant of record and pays you out.
The parts of an organization
Section titled The parts of an organization- Owner
- The Coritan account that created the organization. The owner has every permission, is the only person who can delete the organization or switch its billing basis, and cannot be removed or demoted. The resources behind linked products run on the owner's Coritan account.
- Members
- Other Coritan accounts you add, each with a role. Members work in the organization's pages in the Coritan dashboard and in the staff console. Organization roles and permissions lists what each role can do.
- Customers
- The people who buy from you. A customer account belongs to your organization only: it is not a Coritan account, and a customer never sees coritan.com. Customers sign in on your storefront with an email or a username and a password.
- Products and pricing
- What your customers can buy. A linked product is backed by a Coritan product, such as a server plan of App Deployment, and ordering it creates the real resource. A standalone product is something you deliver yourself, and nothing is created on Coritan. Each product has one price per billing cycle. See Set up products and pricing.
- Customer services
- What a customer holds after an order: one product at one price, renewed each billing cycle until it is cancelled. See Manage customer services.
- Storefront
- The site where customers browse, order, pay and manage what they bought. You build it on the storefront APIs, and set its logo, colours and legal links in Settings.
How money moves
Section titled How money movesYour organization's billing mode decides who takes your customers' payments.
| Billing mode | Who takes payment | Invoices and payouts |
|---|---|---|
platform_mor (Platform merchant of record) |
Coritan's payment gateways, with Coritan as merchant of record. | Coritan invoices your customers when their services come due and pays you each month. |
own_gateway (Own gateway) |
Your own PayNow store. Checkout fails until it is connected. | Coritan raises no renewal invoices and makes no payouts. The money reaches you through PayNow, and what you owe Coritan for it is invoiced to your account. |
hybrid (Hybrid) |
Your PayNow store when it is connected, otherwise Coritan's gateways. | Coritan invoices and pays you out for the money its gateways took. |
Whatever the billing mode, Coritan earns two things from your organization:
- The platform cut, a share of the money your customers actually pay you each calendar month, store and hosting alike. The share is the tier of that month's whole volume, and it applies to all of it: with the defaults, 3.5% under $2,000, 2% under $10,000 and 1% from $10,000. Tax, refunds, chargebacks, discounts, customer credit and invoices you mark paid are not money in, so they count for nothing.
- The cost of the hosting you resell, below Coritan's list price by the wholesale discount, which is a setting (The reseller program's terms shows it). On the Usage billing basis, which a new organization starts on, you pay the wholesale rate for what each customer's server uses, charged as it runs. On the Plans basis you pay the wholesale price of each service period your customer's invoice pays for. Your price for a linked plan can be no lower than the plan costs you. Your margin is your price, less what the hosting costs you, less the cut. See what your customers' use costs you shows it customer by customer.
A payout is what Coritan's gateways collected for you, less the cut on all your money, the wholesale charges and your usage at wholesale. When that does not cover what you owe, because your own PayNow store took the payments, the rest is invoiced to your account. Invoices you mark paid and invoices paid from customer credit are not part of a payout. Track your payouts explains the monthly cycle, and The reseller program's terms has the current tiers.
Coritan's own organizations, the ones it runs its own brands from, pay no cut, no wholesale charges and no usage charge.
Credentials for each API
Section titled Credentials for each APIEvery Organization API path starts with https://api.coritan.com/api/v1/orgs/{org_slug}, where {org_slug} is your organization's slug. Which credential a call takes depends on who is calling.
| Caller | Paths | Credential |
|---|---|---|
| A member, from your own tools | The organization itself, members, customers, products, services, billing, DNS, mail, webhooks | Authorization: Bearer with the member's Coritan access token, or a staff console session |
| Staff, in the staff console | /staff/... and /chat/... |
Authorization: Bearer with a staff session from staff sign-in |
| A signed-in customer | /portal/... and the customer's own /auth/... calls |
Authorization: Bearer with a customer token from customer sign-in |
| Anyone | /storefront/... |
None |
| Your servers | /commerce/... |
X-API-Key with an organization API key and the scopes it needs, or a member's token |
| Your checkout page | /store/... |
x-publishable-api-key with a publishable key, plus the shopper's token for their own orders |
An organization API key works on the Commerce API only. Every other member call needs a person's token, so an automation that manages customers or products signs in as a member.
Limits
Section titled LimitsCoritan sets each organization's tier and its limits on customers, customer services and products. The dashboard shows the tier in the list of organizations. When a limit is reached, the API refuses the next customer, service or product with 403 and names the count, for example Service limit reached (500/500).