Skip to main content
This is the high‑level entry point to your Finhost documentation. It orients product teams, developers, and back‑office admins, then points you to the right deep‑dives.

​
What is Finhost?

Finhost is a white‑label digital banking platform that ships:
  • Customizable front‑end apps (web & mobile) that connect to your Core via APIs
  • A secure Auth layer (Cognito) and app‑side session management
  • KYC/KYB flows integrated with providers (e.g., Sumsub)
  • An Admin Back‑Office for operations, compliance, and support
  • Integrations with EMIs/PSPs/Custodians (e.g., OpenPayd, BCB, Fireblocks, Intercash, Kraken) to issue accounts, move money, and manage crypto rails
Use this page to understand the parts and jump to the section you need.

System config

Global settings & branding hooks that shape your white‑label instance.

Branding

Colors, logos, and UI tokens to match your brand.

Custom front‑end app

Local env, dependencies, and how the front‑end talks to Core.

API

API documentation, Auth & Authorization

Backoffice

How admins sign in (2FA), navigate, and what they can see.

​
Provider integrations

Sumsub

KYC/KYB & Transaction Monitoring.

OpenPayd

IBANs & fiat rails.

Fuse

Payments connectivity.

IFX Payments

Payments & FX.

BCB Group

Banking for crypto businesses.

Fireblocks

Crypto custody & transfers.

Intercash

Card issuing.

Kraken

Crypto liquidity & accounts.

Fiat Republic (In progress)

Coming soon.

BVNK (In progress)

Coming soon.

ClearBank (In progress)

Coming soon.

​
How the pieces fit together

  1. Auth & Sessions → The app authenticates users against Cognito and stores tokens client‑side for secure API calls.
  2. Signup flow → Users register, confirm, and initialize their profile in Core. Contracts (fees/limits) are accepted as part of onboarding.
  3. KYC/KYB → The app requests a provider access token and opens the Sumsub Web SDK with your theme configuration. On result callbacks, the app updates user state.
  4. Backoffice → Admins sign in with 2FA and manage users, accounts, transactions, and cards; compliance can monitor AML and manual review queues.
  5. Reports → Daily‑computed KPIs with on‑demand refresh for balances, plus onboarding and reconciliation views.
  6. Providers → Operational calls (IBAN issuing, payments, custody, cards) are routed via configured providers per currency/rail.
Building a custom app? Start with Before start, then Auth, then Sign Up/Sign In, and finally KYC. Operators should begin with Backoffice › Introduction, then Reports and Bank management.

​
Support & feedback

If anything is unclear or missing, leave a note in your docs repo or contact the Finhost team. The docs are evolving—your feedback helps us prioritize the next updates.