Features

Eighteen modules of one core: from the client and the account to treasury and partner financing.

Operational core

Customers, accounts, payments, general ledger and day close: the base of every bank operation.

Banking products

Loans, deposits, cards, cash, FX and partnership products on shared accounts and postings.

Channels and catalog

How products reach the customer: personal cabinets, an open API and one catalog of products and plans.

Control and treasury

Treasury, reporting, limits, AML/CFT and roles: control of risks and regulator requirements.

Platform capabilities

Beyond the eighteen modules, the core has built-in tools for integration, security, operations and customer service. All of it is already in the product code.

Integration and events

  • Accounting system linkBank events are mapped to documents of an external accounting system, with a controlled transfer queue.
  • Event bus consoleEvent queue statistics, manual batch dispatch, retries and triage of failed messages.
  • Template notificationsTemplates in the customer language, event rules and an SMS provider chosen by recipient country.
  • Reference data in six languagesEvery entry of the bank reference books is translated into all six product languages.
  • Business calendarWeekends, holidays and the bank time zone drive value dates and deadlines.
  • Dated pack updatesA new regulatory version of a country pack is staged ahead, switched on the right day and rolled back if needed.

Security and access

  • Request rate limitingProtects the API from overload and brute force, limits are set in security settings.
  • Security headers and CORSHSTS, CSP and an allowed domain list are on in both the core and the personal cabinets.
  • Encrypted audit and secretsAudit log fields and partner secrets are stored encrypted in the database.
  • Trusted devicesA customer device is bound, trusted or revoked, risky sessions require confirmation.
  • Channel policies for businessesStrong authentication and device requirements are set for each corporate customer.
  • Standard partner registrationOpen Banking partners register themselves under RFC 7591, authorization requests go through PAR.

Operations and reliability

  • Backups per bankA backup catalog is kept for each bank separately, restore is started through the API.
  • Restore drillsRestores are tested on schedule, with a step-by-step log and a migration rollback check.
  • Bank onboarding wizardA new bank is set up in one call: registry, country pack and a launch readiness check.
  • Release gatesA release is blocked when core latency, queues or volumes go beyond thresholds.
  • Background processesAccruals, standing orders, reconciliations, rates and KYC reviews run on schedule with no double runs.
  • Alerts and monitoring includedReady Prometheus alert rules and a Grafana board for the core API.
  • Recovery runbooksInstructions for failures of day close, payments and the database, target availability 99.9%.

Data and reports

  • Customer on one screenAccounts, deposits, loans and cards of a customer with totals per currency in one API response.
  • Customer event feedA timeline of customer operations and actions for the clerk and in the personal cabinet.
  • Customer tagsFree-form tags to segment the base and run product campaigns.
  • Balance on any dateHistorical account balance and account reconciliation with the general ledger on request.
  • Exports in the right formatStatements in DOCX and for 1C, business reports in PDF, XLSX, CSV and JSON.
  • Liquidity ratiosLCR, NSFR, gap analysis and a matrix of historical stress scenarios.
  • Campaign analyticsTracking of product campaign events and summary figures for each.

Customer service

  • Back office task queueExceptions and manual actions become tasks with an assignee and a lifecycle.
  • Bank-branded certificatesBalance, details, debt and deposit certificates and payment schedules in PDF in six languages.
  • Loan self-serviceEarly repayment, restructuring requests and documents in the personal cabinet.
  • Deposit self-serviceEarly closure with an amount preview, rollover and a change of payout account.
  • Card in customer handsFreeze, limits, channels, reissue, PIN and disputes right from the personal cabinet.
  • Self-registrationThe customer signs up in the personal cabinet and binds their own device.

Product tools

  • Credit linesLimit, available amount, suspension and limit changes approved by a second employee.
  • Scoring builderRules, logistic regression, ONNX and hybrid models with a preview before activation.
  • Risk-based rateThe loan rate is picked by the band of the borrower scoring result.
  • Partner-subsidized installmentsA partner or merchant covers the interest, the subsidy is reflected in accounting.
  • Credit bureau exchangeRegular reporting to bureaus, import of responses and dispute handling.
  • Collateral valuation before payoutRequests to appraisers with result intake and a loan payout readiness checklist.
  • Payment queue and cut-offA payment waits for funds or its value date and leaves after the cut-off time.
  • Cash shifts and limitsTeller shifts with a count by banknotes, minimum and maximum cash per branch.

For developers

  • Compatibility CLIPayment channels and processing are checked against reference messages of five countries.
  • SDK for your adaptersA sample package to connect your own payment channel or processor.
  • Test interbank environmentSandbox profiles and an end-to-end check from payment to posting.
  • Load scenariosReady load, benchmark and long chaos test scenarios in the sandbox.
  • Country pack self-checkRegression on identifiers, account numbers, payment templates and report forms.
  • Open architecture decisionsKey core decisions are described in ADR with the reasons and consequences.

Shall we show the modules on your configuration?

We can show the module in action, walk through integrating it with your current core system, and estimate what a launch in your jurisdiction would take.