---
title: Partner
slug: get-started/core-elements/partner
description: Cross River partners are top-level entities that manage products, customers, accounts, branding, and settings with secure data isolation.
createdAt: 2026-10-05T06:49:53.951Z
---

## What is a partner

A *partner&#x20;*&#x69;s your organization's identity in the Cross River banking system. You are the partner. When you onboard with Cross River, you're created as a partner in the system. The partner is the container that holds all your products, configuration settings, and customer relationships. Cross River creates each unique partner with its own set of products tailored to its specific business model and customer needs.

During onboarding, you receive a unique Partner ID (a GUID) that identifies all your operations. This ID appears in API responses for tracking and audit purposes.

## Role of the partner

As a Partner, you are the customer-facing brand and business owner of the banking relationship. You control the customer experience: your branding, your application or platform, your customer support, your pricing, and your go-to-market strategy. Cross River offers the regulated banking  infrastructure underneath: the actual banking accounts, payment processing rails (such as Instant payments, Wires, and ACH), compliance tools and systems, ledger systems, and access to FDIC insurance where applicable.&#x20;

A partner is the highest-level entity in the COS hierarchy. It serves as your security boundary, ensuring complete data isolation from other organizations on the platform.

## What belongs to a partner?

Everything you create within COS is associated to your partner:

- **Products**: Your account types (checking, savings, lending products)
- **Customers**: Individuals and businesses you onboard
- **Accounts**: Bank accounts opened under your products
- **Users**: Your staff who access the platform


![](https://api.archbee.com/api/optimize/4hvUOg5mU1sCngl0n0Has/z1_9SAAmJrruknYHuctPw_diagram-4-acme-fintech-hierarchy-defines-owns.png)

## Partner hierarchy example

The banking hierarchy flows:

Partner → Product → Account

Partner → Customer

Customer + Account  &#x20;

- **Partner (you)**: Your organization in the Cross River system. For example, ACME Fintech
- **Product (configuration template)**: Banking service packages your RM creates for you. For example, Premier Checking.
- **Customer (your end user**): Individuals or businesses using your platform. For example, John Smith.
- **Account (banking account)**: Individual customer banking accounts . For example, John's checking account #1234567890 (opened under your product)

:::hint{type="info"}
The Partner controls which Product is used as the template when creating each customer's Account.
:::

## Key concepts

### 1. Partner as top-level entity

The partner is the highest level in the hierarchy. Products, customers and accounts exist under a specific partner. Partners are isolated from each other; you cannot see or access another partner's data or Accounts.

### 2. Configuration inheritance

Configuration flows down the hierarchy: Partner-level settings → Product configuration → Account defaults. Each level can add specificity. For example, your partner entity may have maximum limits, your product defines standard limits, and individual accounts can have custom limits (within product constraints).

### 3. Multi-product strategy

Most partners have multiple products to serve different customer segments or use cases. For example, you might have:

- "Consumer Checking" and "Business Checking" (different customer types)
- "Basic Account" and "Premium Account" (different tiers)

Each product is independently configured with its own features, limits, and payment services.

## Relationship to other entities

**Products**: Products define your account types (checking, savings, lending). All your products belong to your partner. A single customer within a partner can have an account across many products.

**Customers**: Customers are the individuals and businesses you onboard through KYC and compliance processes. All customers belong to your partner and cannot be transferred to another partner.

**Accounts**: Accounts require both a product and a customer from the same partner. This requirement enforces data isolation at every level of the hierarchy.

## Related concepts

- [Core Elements](docId:95jDawKDKJAEdtTfVnlfs)&#x20;
- [Product](docId\:wtIt_7nG1lB4OfNDWW6Yo)&#x20;
- [Customer](docId:-tWHm_NOajm8-JqxK8BYr)&#x20;
- [Account](docId\:CAfUrHQC9JleBZgedlU1N)&#x20;

