COS terms

what is 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 s 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 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 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 and 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