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:

1. Entity

   The end party (individual or business) that will hold an account. Created with Create entity.

2. Onboarding

   KYC for individuals or KYB for businesses. The entity cannot transact until onboarding succeeds. Submit with Create onboarding and watch progress with Get onboarding or webhook events.

3. Account

   The bank account itself. Open with Create account only after onboarding is approved.

4. Transfer

   Move funds between BaaS accounts or out to external rails with Create transfer. Track with Get transfer.

For the full lifecycle and how BaaS connects to payouts and split marketplace, see 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 for the current list before scoping a launch.
• Payout integration. BaaS accounts can receive funds from payment splits and payouts using the same recipient model.

What to do first

1. Confirm BaaS is enabled for your account

   BaaS access is provisioned per merchant. If Create entity returns an authorization error, contact support to enable it for your account.

2. Read the BaaS overview

   The BaaS overview covers the integration flow end to end with the sequence diagram. Read it before designing your data model.

3. Plan for async onboarding

   Onboarding can take from minutes to days depending on entity type and region. Subscribe to the BaaS webhook notifications and design your UX around the wait, not around polling.

4. Sandbox the four-step flow

   Once enabled, exercise create entity, create onboarding, create account, create transfer in order. Each step in the API reference has the request shape.

Where to go next

BaaS overview

The product page with the full integration sequence diagram.

Create entity

First call in any BaaS flow.

Create onboarding

KYC/KYB submission. Required before any account or transfer.

Create account

Open the bank account once onboarding is approved.

Create transfer

Move funds between accounts or out to external rails.

Webhook notifications

Lifecycle events for entities, onboardings, accounts, and transfers.