---
title: COS terms
slug: ops-and-admin/cos-terms
description: Discover the COS (Cross River Operating System), an API framework that streamlines fintech operations with unique identifiers for secure partner interactions and efficient banking tasks.
docTags: 
createdAt: 2026-02-09T13:22:01.672Z
---

## What is COS

COS  is a proprietary core banking platform comprising several different modules which work together to power our fintech platform. At the head of COS sits the banking Core API that manages fundamental banking functions such as customer onboarding, account management, and transaction activity.   

## Resource

A resource refers to constructs such as a* partner*, *customer*, *product*, *account*, or a *payment*. The unique identifier (id) for a resource can help locate specific information within COS, such as an ACH debit payment or an inbound wire transfer.

## Account

This is a bank account which has a routing number and account number. The type of account will vary based on your funds flow. Refer to [Accounts](docId\:ZQyAf4oeI1rEzpBOI78MJ) for more details.

## Unique identifiers

COS uses GUIDs to identify different resource types throughout the system. The unique identifier for a resource can help locate specific information within COS, such as an ACH debit payment or an inbound wire transfer.

## Payment ID

All rail payments have their own GUID referred to as a *Payment ID*. This can be found in the response payload of a new payment request. It can also be used in the endpoint URL to view payment details.

## Transaction ID

When a core posting event occurs, a *Transaction ID* will generate. This can be found on the transaction details page as well as at the end of the page URL.

## Request ID

The *Request ID* is within the response header. *Request IDs* are more relevant to API users and will not be visible to COS Explorer users who lack admin permissions which allow them to view API logs. A successful `POST` request will provide a *Request.Id**  ***in the response header. 

## Partner ID

This identifies the Partner within COS. External users only have access to a single Partner.  Partners are provided with their *Partner ID* during onboarding. Many API operations provide the *Partner ID* value within the response body. 

The *Partner ID* is not visible to COS Explorer users that lack admin permissions which allow them to view API logs or Partner page within the Admin module.

Data in the Core is segmented by Partner. This prevents any information belonging to one Partner, such as a Customer or Transaction record, from being visible to another Partner.

## Product ID

Products are unique resources that define how an account functions. All accounts, such as DDA and time deposit account products, belong to a product which can be configured as needed. A Partner may have more than one product within their partner resource. For example, a BaaS Partner may have both a checking and savings product as part of their program offering. Most operations will trigger a response which contains the *Product ID*. For additional information, see [COS product types and IDs](docId\:A4xk-yBQUtIA6tNQ5oJKf). 

## Customer ID

Customers are uniquely identified either by their *Customer ID* or their CIF number. CIF is used internally by Cross River for compliance purposes. Customer refers to the end customer, the Partner’s (who has a Cross River account) customer. There is a customer record in COS that goes through KYC and KYB. For more information about customer records, see  [Customer record](docId\:EDJywbh2OgbvTQleF_QZZ).

## Event ID

This ID refers to webhook events. When a Partner is registered for a particular webhook event and that event is triggered, it will include the *Event ID* as well as additional resources tied to that event. Partners can then query those specific resources for additional details related to the event.