Open A3.MFO

Implementation scenarios

Four typical platform configurations. Each changes the product set, the composition of checks and the disbursement method, while the pipeline and the ledger stay the same.

Online microfinance

Short-term loans and instalments online

An application arrives from the website or an app, the decision is automated, and money reaches the card within minutes.

  • Rule and model based scoring, manual review only on borderline applications
  • Bureau and state registry checks before the decision
  • Disbursement to a card, by instant payment or to a wallet
  • Autopay and reminders before delinquency starts

An application reaches disbursement without operator involvement, while borderline cases arrive at manual review with the evidence already collected.

Scenario details
Retail and partner network

Instalments at points of sale

A merchant creates the application in store, the platform checks the client and the eligibility of the goods category, and money goes directly to the merchant.

  • Directory of merchants and permitted goods categories
  • Separate products and rates for each partner network
  • Settlement with the merchant and reconciliation against the register
  • Insurance cancellation during cooling-off through the borrower portal

A partner network is onboarded by configuring products and reference data, without a separate code branch per merchant.

Scenario details
Secured lending

Loans against pledged property

A pledged item is described by its own type, receives an appraisal with history and is linked to the contract. Encumbrance and its release are recorded as events.

  • Real estate, vehicles, equipment and jewellery
  • Appraisal history with date, appraiser and reason for revaluation
  • Loan to value computed on the current appraisal
  • Foreclosure and tax reporting on disposal

Collateral value never diverges from the books, and foreclosure follows a fixed procedure.

Scenario details
Entering a new market

A second country on the same platform

An organization is created with its own data storage region. Bureau and state registry providers of that country are connected, reference data and document templates are translated.

  • Separate database and storage region per organization
  • Own currency, time zone and business calendar
  • Checks against the sources of the identifier country, not the organization country
  • Six interface languages and multilingual document templates

A new market opens by configuring providers and reference data, because the data region is part of the model from the start.

Scenario details

How implementation runs

The order is the same for every scenario. Only the scope of the second and third steps differs.

  1. 01

    Process walkthrough

    We review products, mandatory checks, disbursement channels and existing integrations.

  2. 02

    Environment setup

    Organization, data region, reference data, products, roles and document templates.

  3. 03

    Provider connection

    Bureaus, compliance, acquiring, messaging and accounting under your own contracts and keys.

  4. 04

    Pilot operation

    Part of the flow runs through the platform, results are reconciled, then the rest is migrated.

Your scenario is different?

It almost always is. Tell us about your products and mandatory checks, and we will work out what configuration covers and what needs development.

Request a demoPricing