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

# Integration Models

> Iron supports B2B, B2B2B, and B2B2C setups. Integrate via API, the Partner Dashboard, or offer Iron App as a whitelabel frontend for your end customers.

Iron supports three integration models: direct use (B2B), serving business customers (B2B2B), and serving individual consumers (B2B2C).

## At a Glance

| Model     | Who uses Iron's services | Example                                                   | Integration                 |
| --------- | ------------------------ | --------------------------------------------------------- | --------------------------- |
| **B2B**   | Your company directly    | Fintech using stablecoin rails for treasury               | API or Dashboard            |
| **B2B2B** | Your business customers  | PSP offering stablecoin payouts to merchants              | API or Dashboard + Iron App |
| **B2B2C** | Your individual users    | Neobank offering EUR virtual accounts to retail customers | API or Dashboard + Iron App |

## B2B: Direct Use

Use Iron for your own operations such as treasury, payroll, and settlement.

**Examples:**

* Cross-border payroll, converting USDC to EUR and paying employees via SEPA
* Exchange settlement through stablecoin-to-fiat [Offramps](/offramp)
* Corporate treasury across fiat and stablecoins via [Virtual Accounts](/account)

Integrate through the [API](/api-access) or the [Partner Dashboard](/partner-dashboard).

<Note>
  B2B is not exclusive. The same company can use Iron directly and act as a Partner under B2B2B or B2B2C, onboarding its own customers or subsidiaries. See [Roles & Entities](/roles-entities).
</Note>

## B2B2B: Serving Business Customers

Embed Iron into your product. You act as a **Partner**. Your business customers become **Customers** of Iron.

**Examples:**

* PSP offering stablecoin money transfers to merchant clients
* Banking-as-a-service platform enabling neobank clients to issue virtual EUR accounts
* Payroll provider letting companies pay contractors in stablecoins

Each business customer completes [KYB onboarding](/kyb) and gains access to [Onramp](/onramp), [Offramp](/offramp), [Swap](/swap), [Virtual Accounts](/account), and [Stablecoin Issuance](/issuance/create-your-stablecoin).

## B2B2C: Serving Individual Users

Embed Iron into your consumer-facing product. You act as a **Partner**. Your individual users become **Customers** of Iron.

**Examples:**

* Neobank offering named EUR and USD virtual bank accounts to retail customers
* Crypto wallet enabling users to onramp fiat to stablecoins via personal vIBAN
* Remittance app letting users send stablecoins and have recipients cash out to local bank accounts

Individual customers complete KYC through one of three frameworks:

| Framework                                   | How it works                                                                                       |
| ------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| [KYC Reliance](/reliance-kyc-token-sharing) | Iron relies on your existing KYC, shared via SumSub token sharing. Requires a regulatory agreement |
| [KYC Outsourcing](/outsourcing)             | You collect KYC data on Iron's behalf and submit via API                                           |
| [Direct Onboarding](/hosted)                | Iron handles KYC through a hosted verification flow                                                |

<Note>
  Regardless of the onboarding framework, every customer is a direct customer of Iron for compliance purposes. See [Onboarding Lifecycle](/onboarding) for the full flow.
</Note>

## Iron App: Whitelabel Frontend

For B2B2B and B2B2C setups, Iron offers **Iron App**, a whitelabel frontend that your end customers (the last B or C) use directly.

Iron App gives your customers account management, transaction history, onboarding, and access to Iron's products. No custom UI needed. You manage configuration through the Partner Dashboard or API. Iron App handles the end-customer experience.

**When to use Iron App:**

* Go live without building a frontend
* End customers need direct access to onboarding, account management, and transaction history
* Keep the customer-facing experience up to date with new Iron features automatically

## How to Integrate

Two integration paths. Use both simultaneously.

<CardGroup cols={2}>
  <Card title="API" icon="code" href="/api-access">
    Create customers, onboard them, set up Autoramps, and monitor transactions programmatically.
  </Card>

  <Card title="Partner Dashboard" icon="browser" href="/partner-dashboard">
    Manage customers, Autoramps, API keys, and transactions at [app.iron.xyz](https://app.iron.xyz).
  </Card>
</CardGroup>

Most partners use the **API for programmatic workflows** (customer creation, Autoramp setup, webhook-driven monitoring) and the **Dashboard for operations** (reviewing customer status, managing API keys, inspecting transactions).