Embedded Finance
Embedded finance lets non-financial brands offer regulated financial journeys inside their own products. FinHub exposes this as an API-first platform: you own UX and branding; FinHub provides customer lifecycle, verification, wallets, and payments. This page maps a typical integration to the published Customer APIs, Verification & Compliance, and Financial Operations references. Use it as the narrative companion to those sections.Sandbox base URL (illustrative):
https://sandbox.finhub.cloud/api/v2.1 — your tenant receives the exact base URL and credentials during onboarding.Documentation map
Customer APIs
B2C and B2B registration, sessions, activation, and organization management
Verification & Compliance
Verifications, documents, approvals, and mandatory consents
Financial Operations
Wallets, beneficiaries, payment consents, prepare/execute, orders
Workflow diagrams
B2C workflow
B2B workflow
Placeholders
Replace these with values from your tenant and API responses:B2C individual — embedded journey
High-level sequence aligned with Individual customer APIs:B2B organization — embedded journey
Aligned with Organization customer APIs:Financial operations (after activation)
Financial endpoints are only valid once the customer is activated and wallets are ACTIVE. The canonical HTTP sequence is documented on the Financial Operations overview:Why API service model fits embedded finance
- Your UI, your brand — no forced FinHub screens; you build flows in your app or web.
- Composable steps — same APIs support light-touch onboarding or fully automated journeys.
- Regulatory coverage — KYC/KYB, consents, and payment consents are exposed as explicit API calls.
API Service Model
Platform overview and authentication concepts
Next steps
Individual APIs (B2C)
Registration through activation
Organization APIs (B2B)
Business onboarding and activation
Verification & Compliance
Verifications, documents, and consents
Financial Operations
Wallets, transfers, and payment operations