> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vence.one/llms.txt
> Use this file to discover all available pages before exploring further.

# How vence works

# How Vence works

Vence does one core job: turn fragmented financial reality into **explainable trust**, then use that trust to authorize access, credit, cards, and capital.

```
Identity + cashflow + behaviour + network
        ↓
   Trust Graph
        ↓
 Feature / risk context
        ↓
   Policy Engine
        ↓
  Decision Engine (API)
        ↓
 Monitoring + Controls
        ↓
 House of finance surfaces
```

## Decision Platform

1. **Ingest** — Entities, identity links, consents, transactions, and feature snapshots.
2. **Graph** — People, businesses, institutions, accounts, wallets, and relationships with evidence.
3. **Decide** — Underwrite and access decisions with verdict, limits, reasons, and versions.
4. **Monitor** — Material changes re-enter policy (payroll stops, velocity spikes, revenue decline).
5. **Control** — Pause draws, reduce limits, restrict spend — within Vence’s contractual scope.

## House of finance

Surfaces do not invent their own risk brain. They call the same platform. Today these products are **founder-beta / design partner** — they demonstrate the platform; they are not general production banking:

* Business banking and bill pay
* Vence Card (planned 3% business cashback) and Elite (planned 6% for founders)
* Net-60, Capital, Bill Pay Later, Pay Over Time, Liquidity
* Stablecoin payments and cross-border AR with expanding corridor coverage (roadmap)

## For developers

The public path is intentionally short (when API access is provisioned):

1. Create an API key in Console.
2. Create or retrieve an entity.
3. Attach identity / cashflow signals.
4. Call underwrite.
5. Fulfill on webhooks and audit the decision record.

See [Quickstart](/developers/quickstart).