## Jiko Data Model

Before making your first API call, it is important to understand how data is structured within your Jiko integration.

Your entire integration exists within a securely isolated **Partner Tenant** (your overarching platform environment):

![Pockets Diagram](/assets/datamodel1.98289ad3d38d811b5e5b4ff135a1c1e1e07b99b785bb0f8023abd5205702a4aa.9c1bb791.png)

### 1. Customers (End Users)

Once an individual or business successfully completes the KYC or KYB onboarding process, they become a **Customer**.

A Customer is the verified legal entity that owns the underlying assets. Your Partner Tenant can manage many Customers.

Physical and virtual **debit cards** are also issued at this level and are directly tied to a specific customer.

### 2. Pockets (The Financial Engine)

A Customer does not have a single balance. Instead, they have one or more **Pockets**.

A Pocket is the core construct of the Jiko platform. It combines:

- A bank account for cash movement
- A brokerage account for T-Bill exposure


A single Customer can have multiple Pockets, for example:

- Operating Capital
- Payroll


### 3. Portals

To move money in and out of the Jiko ecosystem, a Pocket requires an access point.

A **Portal** generates a unique routing number and account number tied to a specific Pocket. Multiple Portals can be created per Pocket, for example:

- One for receiving wires
- One for payroll deposits


Each pocket comes with one portal already instantiated, but you can create more as required.

## Summary

- 1 Partner Tenant → Many Customers
- 1 Customer → Many Pockets and Cards
- 1 Pocket → Many Portals