Basic Entities

You can implement your use case by creating and managing Unit's basic entities. They are the building blocks of the platform, and they include:

Applications

Your customers must be identified before you store or move money for them. To identify a customer, create an Application with their details — individual or business. Once the application is approved, a Customer entity is created.

Customers

A single Customer on Unit represents a single customer of your platform. Customers are important top-level entities. All the activity that belongs to a specific customer (accounts, payments, cards) will live under them.

Accounts

Accounts track the storage and movement of money. Every account includes Transactions and a current balance. You may create any number of Accounts under a Customer. To support the full range of use cases, Unit supports three account primitives: Deposit Accounts, Wallet Accounts (FBO), and Credit Accounts.

Payments

Payments are an instruction to move money in or out of an account. Unit supports a variety of payment types: ACH, wires, check deposits, check payments (print & mail), book transfers (internal payments), and real-time payments. Payment objects expose network-level detail, for example trace numbers, settlement timestamps, and return codes.

Cards

Cards are issued under an Account and draw from its balance. You can issue physical or virtual cards across all types: debit, credit, and prepaid. You may choose to be in the authorization flow for card use, to implement card controls like merchant or amount restriction.

Transactions

Every money movement within an account happens through a Transaction. Transactions are immutable, timestamped, and available in real time. They're the source of truth for account balances and the basis for any reconciliation or reporting your platform needs.