# Multi-tenancy

> This guide shows how integrators and BPO organisations can manage payments for several clients from one Merchant Portal login, using organisations.

This guide shows how integrators and BPO organisations can manage payments for several clients from one Merchant Portal login, using organisations.

Video walkthrough: [Setting up multi-tenancy in Shuttle](https://www.youtube.com/watch?v=6xiXHmzz2b4)

## Overview

Each client gets its own organisation, with its own team, billing, accounts and payment providers. You see them all from one login and switch between them, while each client's data, configuration and reporting stay separate.

## Key benefits

- **Central management**: oversee every client's payments from one login
- **Provider independence**: the same workflows whichever payment provider each client uses
- **Client separation**: each client's data, configuration and reporting are kept apart
- **Scale**: onboard and manage hundreds of client organisations
- **One API**: integrate once and use it across every client's accounts

## Setting it up

### Step 1: Your own login

Sign up to the Merchant Portal with your own business details, not a client's. Your login can belong to any number of organisations, with a role in each. See [Organisations, accounts and users](/merchants/merchant-portal/intro/#organisations-accounts-and-users).

### Step 2: An organisation for each client

1. Open the menu under your account name and select **My Organisations**.
2. Select **Add Organisation**.
3. Enter the client's name and website, then select **Save**.

Repeat for each client. Each organisation has:

- its own team
- its own billing and reporting
- its own configuration
- its own branding and settings

### Step 3: Accounts for each client

Inside each client's organisation:

1. Open the menu under your account name and select **My Instances**.
2. Select **New Instance**, then **Create Instance**.
3. Connect the client's payment provider under **Configure** > **Payment Processing**. See [Payment processing](/merchants/merchant-portal/payment-configuration/).
4. Set up what the client needs, such as payment links, voice payments and branding, under **Configure**.

## Advanced use cases

### Geographic separation

For organisations managed by region, create a separate organisation for each region, for example:

- **Client-US**: North American operations and compliance
- **Client-EMEA**: European operations with local payment methods
- **Client-APAC**: Asia-Pacific configurations

This lets you manage each region's:

- compliance
- local payment methods
- currencies
- team

### Department separation

Large businesses may want to keep departments apart:

- **Client-Sales**: customer-facing payments
- **Client-Operations**: internal billing and reconciliation
- **Client-Support**: refunds and disputes

## Billing

By default, each organisation is billed separately, so each client receives its own invoices. This works well when clients pay their own payment processing costs.

If you'd rather pay for all your client organisations centrally, consolidated billing is available. Contact our support team to discuss it.