> ## 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.

# Integrations

> Vence is built to integrate with Visa, Mastercard, Plaid, Stripe, bank rails, payroll, and institution stacks — while remaining the trust and decision layer.

# Integrations

Vence is **integration-first infrastructure**. The Decision Platform is designed to sit beside the rails and processors institutions already trust — not to replace every logo in a pitch deck.

## Designed to compose with

| Category                    | Examples                                |
| --------------------------- | --------------------------------------- |
| Card networks               | **Visa**, **Mastercard**                |
| Bank data                   | **Plaid** and equivalent aggregators    |
| Payments & billing          | **Stripe** and complementary processors |
| Banking / ledger / treasury | Modern financial execution partners     |
| Auth for Console            | WorkOS (institutional identity)         |
| Payroll, KYB, chain RPC     | Adapter ports as programs require       |

Public product language names **Vence**. Partner systems execute behind adapters. Your object model, decisions, and audit trail stay on Vence.

## Why this matters

* Platforms keep their existing checkout, cards, and bank connections.
* Vence supplies **who should get access**, **how much**, **why**, and **what changed**.
* Surfaces (banking, card, credit) inherit the same policy versions as API customers.

## Developer surface

When API access is provisioned, connect sandbox, create keys, and call the Decision API. Partner logos above are **built-to-integrate** targets — not a claim that every adapter is live today. See [Authentication](/developers/authentication) and [API overview](/developers/api-overview).