Overview
Your program represents your product offering. To support it, Lead needs compliance and financial information to provide bank oversight, reconcile financial activity, and effectively monitor the program and its end customers.Diagram
Object Definitions
| Object | Definition |
|---|---|
| Entities | Represent legal persons or organizations with specific rights and roles related to Lead’s products. Entities may be individuals, businesses, or sole proprietors. Each end user must be represented as an Entity on the Lead platform. Most Entities maintain a single Account, which stores risk, compliance, and regulatory details tied to their financial activity (balances, cards, etc.). Entities may have multiple Accounts when the underlying financial relationships are independent—for example, an individual account plus a joint account with a spouse. More details: Entity API |
| Applications | Contains metadata about applications within Lead. Applications are not applicable for deposit products. Approved applications can create accounts. More details: Applications API |
| Accounts | Holds information about financial products provided to end users. In Lead, accounts act as containers and may include one or more credit balances, deposit balances, or collateral sources. Active accounts can create balances. More details: Accounts API |
| Cards | Hold information about cards Lead issues. Cards transition through active, inactive, and closed states reported to Lead. Cards reported to Lead are referenced in the Transactions file for transactions of type card. |
| Balances | Represent financial products with credit or deposit balances. Balances are always positive, whether they reflect credit or deposit accounts. More details: Balances |
| Transactions | Record activity affecting balances. Transactions reconcile the current day’s ending balance against the prior day’s ending balance. More details: Transactions Note For Deposit Programs Transactions Update and Non-Posted Transactions may be used for settlement date adjustment or for cases where funds have been posted to the but not to customer accounts. |
| Funding Request & Response | Are the actions required to fund the Funding Account at Lead. This applies only to clients using incoming transfers, such as incoming ACH or wire transfers, where the Funding Account needs to be funded beforehand. |
| Sales Request & Response | Covers the sale of receivables back to the client. Receivables are sold at the balance level. Lead holds loans for “N” business days and sells the receivables back to the client on the “N”th business day. More details: Sales Request and Sales Response |
| Authorized Users | Defines the relationship between customers (specifically authorized users) and accounts. Authorized users are individuals who have restricted access to an account without owning it. If the list of authorized users exceeds 10, it is recommended to use the Authorized Users file to associate these relationships. More details: Authorized Users |
| Collaterals | Defines the relationship between a collateral asset and the secured account it supports. Supported collateral types include deposit balances (deposit_balance) and real estate (real_estate). Each collateral maps to an account and, for deposit-based collateral, to a specific deposit balance within that account. More details: Collaterals |
| Documents | Are supporting documents uploaded for Customer, Applications, Accounts, Balances. Documents referenced in respective files must be uploaded to the Documents folder prior to being associated. |