Skip to main content

ORBSIS Business Model

The ORBSIS model combines identity, fund accounts, Budget controls, payment instruments, and transaction records.

It can be represented as:

Entity → Primary Account → Sub Account → Budget → VCC Card → Transaction

Entity​

An Entity represents a business or customer on the platform.

It identifies who is using ORBSIS and acts as the top-level identity for accounts, verification, and related business data.

Primary Account​

A Primary Account is the top-level fund account of an Entity.

It is primarily used to:

  • Receive top-ups
  • Centrally manage business funds
  • Transfer funds to Sub Accounts
  • Record fund movements at the Primary Account level

A Primary Account can manage multiple Sub Accounts.

Sub Account​

A Sub Account is a real fund account.

Businesses can create separate Sub Accounts by department, project, brand, business line, or other operational needs to isolate funds.

A Sub Account is primarily used to:

  • Receive funds
  • Transfer funds to other accounts
  • Hold Available Balance
  • Allocate Budget Limits
  • Manage account-level Frozen Amount

The Sub Account itself is not the primary layer for detailed card spending records.

Budget​

A Budget is a logical control layer built on top of a Sub Account.

It is not an independent fund account. Instead, it helps answer questions such as:

  • How much limit is assigned to this business purpose?
  • How much has already been spent?
  • How much can still be spent?
  • How much capacity remains available for additional allocation or use?

A Sub Account can contain multiple Budgets, and a Budget can be associated with multiple VCC cards.

VCC Card​

A VCC Card is the actual payment instrument used under a Budget.

The card performs external payments, while its spending capacity is controlled by the associated Budget and card limit model.

ORBSIS primarily supports:

  • Shared Cards: No independent Card Limit; they use the Available Limit of the associated Budget
  • Limited Cards: Have an independent Card Limit that occupies part of the associated Budget's Utilized Limit

Transaction​

Transaction records represent fund or payment activity, but their meaning depends on the layer being reviewed.

For example:

  • Primary Account transactions: Primary Account fund movements
  • Sub Account fund movements: transfers, Budget Allocation, Budget Release, and other fund operations
  • VCC transactions: actual card payments, authorizations, and related transaction statuses

When investigating an issue, first identify the relevant layer and then review the appropriate records.

A Simple Example​

Suppose a company needs to manage advertising spend:

Company Entity → Primary Account → Advertising Sub Account → Meta Ads Budget → VCC Cards

The business first transfers funds from the Primary Account to the Advertising Sub Account, then allocates a Budget Limit from the Sub Account's Available Balance.

Virtual cards can then make advertising payments under the control of that Budget.

This is the basic way ORBSIS separates real funds from spending controls.