> For the complete documentation index, see [llms.txt](https://timechain.gitbook.io/neucron/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://timechain.gitbook.io/neucron/core-concepts/apps-and-whitelabel.md).

# Apps & Whitelabel

**Only businesses can create and publish apps.** An app is how a business brings Neucron's wallet infrastructure into its own product, and it is the foundation of every whitelabelled integration.

## Two integration paths

### Path 1: Sign in with Neucron

Your app uses Neucron as the identity and wallet provider. Users authenticate with their Neucron account (OAuth 2.0), grant your app scoped access, and their existing Neucron wallets become available inside your product.

```mermaid
sequenceDiagram
    participant U as End user
    participant Y as Your app
    participant N as Neucron
    U->>Y: Click "Sign in with Neucron"
    Y->>N: OAuth authorize (scopes)
    N->>U: Authenticate + consent
    N-->>Y: Access token (scoped)
    Y->>N: Wallet / payment API calls
```

Best when: your users already have (or will happily create) Neucron accounts, and you want zero key-management surface in your own stack.

### Path 2: Embedded whitelabel wallets

Your app keeps **its own authentication layer**. Your users never see Neucron. Your backend creates and manages wallets for your users through the Neucron API or the TypeScript SDK, choosing the [custody model](https://timechain.gitbook.io/neucron/core-concepts/custody-models) per wallet:

* **Embedded MPC wallets:** each of your users gets a non-custodial wallet (device shard + cloud backup shard + Neucron co-signer).
* **Embedded custodial wallets:** your app operates wallets on behalf of users for instant, silent transaction UX.

```mermaid
sequenceDiagram
    participant U as Your user
    participant B as Your backend (your auth)
    participant N as Neucron API / TS SDK
    U->>B: Sign in (your auth, your brand)
    B->>N: createWallet (embedded, per user)
    N-->>B: wallet_id + addresses
    B->>N: transfers, balances, invoices
    B-->>U: Your UI, entirely your brand
```

Best when: you are a fintech building a whitelabelled product and Neucron must be invisible infrastructure. If your backend is TypeScript, the [`@timechainlabs/neucron-ts-sdk`](https://timechain.gitbook.io/neucron-javascript-sdk) gives you typed access to everything; every other stack integrates the REST API directly.

## Apps are governed team members

An app is not just an API key. **An app behaves like another member of the business's team**, with its own role and granular permissions over business resources:

* You decide which resources the app can touch: specific wallets, invoicing, bills, payouts, customer records.
* Least privilege is the default posture: a storefront app can receive payments into its wallet without any ability to release payouts from treasury.
* App activity is auditable like any member's activity.

## App wallets

An app can have a **wallet associated with it**: a business resource the app controls to receive and send assets for its own operations. Typical patterns:

| Pattern                   | App wallet role                                                                                                                             |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Storefront / checkout app | Collection wallet for incoming customer payments                                                                                            |
| Payout automation app     | Operational float wallet for vendor payments                                                                                                |
| Agentic app               | Dedicated budget wallet governed by permissions (see [Agentic Wallets](https://timechain.gitbook.io/neucron/core-concepts/agentic-wallets)) |
| Multi-entity fintech      | One app + wallet per business line, brand, or region                                                                                        |

Because the app wallet is just a business resource under permission control, finance teams keep treasury oversight while product teams ship fast.

{% hint style="info" %}
**Individuals cannot create or publish apps.** Apps are a business capability, gated by KYB. Individuals can still hold, transfer, receive, make payouts, and share collection links from their personal wallets.
{% endhint %}