Blend is designed to be white-labeled into your existing product. Your users interact with your brand, while Blend operates as invisible infrastructure behind the scenes.
Integrator ID
Every integration is identified by a unique integratorId string. This ID is used in:
- SDK initialization: Passed when creating the Blend client
- API calls: Identifies which integration traffic comes from
- Analytics: Track TVL and usage per integration
- Fee attribution: Associate deployment and revenue with your organization
const client = new BlendClientWithActions({
baseUrl: "https://api.blend.money",
userAddress: userWalletAddress,
integratorId: "your-neobank-v1.0", // Your unique integrator ID
}, {});
Branding Configuration
Through the admin portal, you can configure:
| Setting | Description |
|---|
| Logo | Your organization’s logo, displayed in the admin portal alongside your Account Types |
| Primary color | Brand color used in admin portal interfaces |
| Display name | Human-readable name for your organization |
Branding configuration is set in the admin portal. These settings affect how your organization appears to Risk Architects and in internal analytics. They do not affect your consumer-facing app, which you fully control.
Authentication
Blend supports two authentication flows depending on the audience:
| Audience | Auth Provider | Use Case |
|---|
| End users | Privy | Wallet connection in consumer apps |
| Admin portal | Auth0 | Organization member authentication |
Building Your UI
Blend provides APIs and SDKs, not a pre-built UI. You have full control over:
- How deposit and withdrawal flows look in your app
- How performance information is displayed (APY, charts, breakdowns)
- How users select products (Account Types)
- How transaction status is communicated
For reference, the Blend consumer app (app.blend.money) is built with Next.js 15, React 19, and Tailwind CSS 4. You can use any frontend framework and design system. 