Finlego Support Hub

Book a demo with us and we will contact you soon to discuss all necessary details we need to start working with your company.

Onboarding includes a technical kickoff with a solutions engineer, environment provisioning, a tailored integration plan, sample API calls and test cases, and training for your ops and product teams. We’ll set milestones, acceptance criteria, and a go‑live checklist specific to the products you adopt.

Timeline depends on product scope and integrations. We’ll provide a detailed project plan during onboarding.

Developer portal with full API reference, sample mobile/web apps, Postman collections, webhooks guide, reporting templates and a sandbox environment.

Connectors are modular adapters between FinLego and external systems (bank rails, payment processors, identity/KYC providers, accounting/ERP). Enable a connector, supply credentials, configure mapping rules, and test end‑to‑end in the sandbox. If you need a new connector, we can build one as a professional service.

Start with the API smoke tests, then exercise full happy‑path flows (account creation → KYC → funding → transaction → reconciliation). Use webhooks to validate async flows and test edge cases (retries, partial failures). Log and save request/response pairs for support tickets.

Production onboarding includes security reviews, production API keys, endpoint whitelisting, compliance checks (KYC/AML rules), and a go‑live checklist. Coordinate a cut‑over window with your FinLego PM; we recommend a staged rollout (alpha → beta → full) to limit risk.

We follow industry best practices: TLS in transit, encryption at rest, role‑based access controls, audit logs and granular API key scopes. For customers who require artifacts, we share security documentation and architecture diagrams under NDA.

KYC/AML Tools are configurable: choose data points to collect, rules for automatic accept/deny/hold, and screening vendors. You can apply different KYC tiers per product/region and export regulation‑ready reports for auditors.

For card issuing we support tokenization, P2PE and scope‑reduction patterns. We work with certified processors and can advise on PCI scope reduction for your deployment. Specific documentation and responsibilities are outlined during contract and onboarding.

The ledger stores transactional entries with currency and bookkeeping metadata. We support multi‑currency balances, GL tagging, and mapping to external accounting via export tools and connectors. FX events can be modeled as separate ledger entries to preserve auditability.

Settlement schedules depend on rails and connectors. We provide daily and intraday reconciliation reports, APIs to query statement lines, and hooks for automated reconciliation workflows. You can export CSV/JSON or integrate directly with your accounting system.

Common causes: insufficient funds, connector timeouts, validation failures, or KYC holds. Include request IDs, timestamps, and any webhook payloads when you open a ticket. Support will triage, reproduce in sandbox when possible, and advise mitigation or rollback options.

Card issuing requires BIN sponsorship and KYC flows. We support virtual and physical card lifecycle: provisioning, activation, tokenization, spending controls and limits. During onboarding we coordinate BIN/issuer setup and test card distributions in sandbox.

Mobile and crypto wallets integrate via our SDKs and APIs. For crypto you can choose custodial or non‑custodial models; for mobile wallets we provide tokenization and mobile provisioning flows. We also support push notifications and in‑app transaction signing.

Chargebacks follow network rules (Visa/Mastercard/etc.). We surface dispute events in the back‑office, collect evidence, and support submission to the issuer network. Provide chargeback IDs, timestamps and relevant transaction metadata when you open a dispute ticket.

We support both on‑chain and off‑chain settlement depending on the product. Transactions are logged to the ledger and reconciled against on‑chain activity. You can configure confirmation thresholds, supported chains, and notification webhooks for block events.

Yes - through liquidity partners and integrated exchanges. Conversion workflows, settlement timing and fees are configurable. AML and KYC controls apply to conversion flows; we can map these into your risk thresholds.

We offer custody models that include hardware security modules (HSM) or multi‑party computation (MPC) for private key management. Custodial arrangements, access controls and key rotation policies are documented during integration.

The white‑label UI supports visual theming (colors, logos, fonts), configurable screens and modular components. You can enable/disable features per client or tenant and we provide guidelines to maintain UX consistency and regulatory disclosures.

Yes - we provide mobile app templates and developer support for native builds. We can assist with build configuration, provisioning profiles, and guidance on app‑store requirements. App‑store ownership and legal responsibilities remain with you unless otherwise contracted.

Standard back‑office includes user & account management, KYC review queues, transaction monitoring, manual adjustments, dispute handling, role‑based permissions and reporting dashboards. Custom workflows can be added as modules.

Yes - exports are available in common formats (CSV/JSON). We also provide connectors and APIs to push posting lines, statement exports, and reconciliation data into ERPs or accounting packages.

Use this Support Hub form (below), email your dedicated support alias, or contact your account manager. Include product name and a short reproduction of the issue.

Support is available as part of our service tiers. Basic technical support is included with platform subscriptions; advanced options are available as paid packages or professional services.

Endpoint availability, 2xx responses, TLS validity, whitelisting.

Compare ledger, statements, settlements; check for pending items.

Request/response pairs, IDs, timestamps, webhook payloads, logs.