> ## Documentation Index
> Fetch the complete documentation index at: https://yn-c9bb3266.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Banking as a Service quickstart

> How Yuno BaaS works, what you provision before any API call, and where to go for the full reference.

Yuno BaaS lets you create bank accounts, run transfers, and onboard end entities (individuals or businesses) through one API. It uses the same authentication as the payments API, so the integration footprint is small once your account is provisioned.

This page is conceptual. It shows the resource model, the onboarding gate, and where to go next. Production access requires entity provisioning that cannot be done from sandbox alone, so this is the right place to start before you write code.

## Resource model

BaaS has four resources, in order:

<Steps>
  <Step title="Entity">
    The end party (individual or business) that will hold an account. Created with [Create entity](/api-reference/baas/create-entity).
  </Step>

  <Step title="Onboarding">
    KYC for individuals or KYB for businesses. The entity cannot transact until onboarding succeeds. Submit with [Create onboarding](/api-reference/baas/create-onboarding) and watch progress with [Get onboarding](/api-reference/baas/get-onboarding) or webhook events.
  </Step>

  <Step title="Account">
    The bank account itself. Open with [Create account](/api-reference/baas/create-account) only after onboarding is approved.
  </Step>

  <Step title="Transfer">
    Move funds between BaaS accounts or out to external rails with [Create transfer](/api-reference/baas/create-transfer). Track with [Get transfer](/api-reference/baas/get-transfer).
  </Step>
</Steps>

For the full lifecycle and how BaaS connects to payouts and split marketplace, see [BaaS overview](/features/baas/overview).

## Entity types

| Type         | Who                        | What you submit                                 |
| ------------ | -------------------------- | ----------------------------------------------- |
| `INDIVIDUAL` | A natural person           | Name, date of birth, tax ID, identity documents |
| `ENTITY`     | A business or organization | Business name, type, tax ID, beneficial owners  |

## What is different from payments

BaaS shares authentication and webhook infrastructure with payments, but the rest is its own surface:

* **Separate endpoints.** All BaaS lives under `/v1/baas/`. Resource models, statuses, and webhook events are distinct from `/v1/payments/`.
* **Onboarding gate.** Every entity must clear KYC/KYB before any account or transfer can succeed. Build for the async wait.
* **Regional availability.** BaaS is currently live in select markets. Check the [BaaS overview](/features/baas/overview) for the current list before scoping a launch.
* **Payout integration.** BaaS accounts can receive funds from [payment splits](/features/split-marketplace) and [payouts](/features/payouts) using the same recipient model.

## What to do first

<Steps>
  <Step title="Confirm BaaS is enabled for your account">
    BaaS access is provisioned per merchant. If [Create entity](/api-reference/baas/create-entity) returns an authorization error, contact support to enable it for your account.
  </Step>

  <Step title="Read the BaaS overview">
    The [BaaS overview](/features/baas/overview) covers the integration flow end to end with the sequence diagram. Read it before designing your data model.
  </Step>

  <Step title="Plan for async onboarding">
    Onboarding can take from minutes to days depending on entity type and region. Subscribe to the [BaaS webhook notifications](/api-reference/baas/webhook-notifications) and design your UX around the wait, not around polling.
  </Step>

  <Step title="Sandbox the four-step flow">
    Once enabled, exercise create entity, create onboarding, create account, create transfer in order. Each step in the [API reference](/api-reference/baas/create-entity) has the request shape.
  </Step>
</Steps>

## Where to go next

<CardGroup cols={2}>
  <Card title="BaaS overview" icon="landmark" href="/features/baas/overview">
    The product page with the full integration sequence diagram.
  </Card>

  <Card title="Create entity" icon="user-plus" href="/api-reference/baas/create-entity">
    First call in any BaaS flow.
  </Card>

  <Card title="Create onboarding" icon="file-signature" href="/api-reference/baas/create-onboarding">
    KYC/KYB submission. Required before any account or transfer.
  </Card>

  <Card title="Create account" icon="building-columns" href="/api-reference/baas/create-account">
    Open the bank account once onboarding is approved.
  </Card>

  <Card title="Create transfer" icon="arrow-right-arrow-left" href="/api-reference/baas/create-transfer">
    Move funds between accounts or out to external rails.
  </Card>

  <Card title="Webhook notifications" icon="bell" href="/api-reference/baas/webhook-notifications">
    Lifecycle events for entities, onboardings, accounts, and transfers.
  </Card>
</CardGroup>