Loxon Solutions

The learned component sits in two of the seven modules of a twenty five year old credit management suite. The lending origination, collateral management and workflow products are parameterized deterministic software. The models live in the early warning system, where the vendor's own company timeline dates its first AI projects to a specific era of its history, and in the collection platform, where behavior analysis drives contact strategy.

Strip the models and retail lending, corporate lending, collateral management and the collection workflow all continue to run. The vendor also states plainly that an early warning prediction model may be expert based rather than statistical. That describes an optional analytical layer, not a product the models carry.

The human sits in the described path rather than beside it. The early warning system is documented as supporting the human workflow processes of monitoring, explicitly including manual decisions, customer relationship handling and root cause analysis. It has built in automatic and manual workflows, and it schedules recurring human events such as customer visits and calls.

Watch listed cases stay under manual control, qualitative information is captured manually under control, and escalation and pre workout routing are included. The system produces signals and classifications for a banker to act on rather than executing action. No thresholds, confidence bands or limits on unaided action are published, and the division between what the model decides and what the officer decides is implied by workflow rather than stated.

The validation method is documented in detail; the results are not. The early warning product page sets out the apparatus of credit model validation in the vocabulary supervisors use. It covers thorough backtesting, including root cause analysis and signal significance testing, and expert based validation covering plausibility checking and reject inference.

It also covers statistical techniques such as rating migration matrices for low default portfolios, and discusses explicitly the discriminatory power of a behavioral approach. The institution gets full parameterization to change the models and the qualitative inputs itself, which is the property that helps a supervised buyer validate what it deploys. The vendor publishes no results, no performance figures for its own models, no versioning or drift disclosure and no external assessment. The passages read as methodological guidance rather than as a claim about tested implementations.

Two named engagements and no attributed numbers. Raiffeisen Bank Hungary is identified in the company's own history as the first customer, the institution the original retail lending product was built inside. The Egyptian Collateral Registry is named as a delivered national infrastructure project with a testimonial stating the system was developed and implemented to Egyptian law and regulatory requirements, and that Loxon remains its backbone.

Alongside them sit more than eighty banking groups and over two hundred staff. No outcome figure attaches to any named institution, the testimonial carries no named individual, and the recovery and portfolio quality improvements the products are sold on are never quantified anywhere.

Silent. Nothing states whether customer credit and behavioral data is used to train or improve models, whether anything is pooled across the eighty banking groups on the platform, or how long data persists. Where models are described, the framing is that the institution supplies its own data and parameterizes its own models. That points toward per customer isolation, but it is an inference from product design rather than a published commitment.

Nothing published on data handling. No retention position, no deletion terms, no subprocessor disclosure, no statement on how borrower and delinquent account data is segregated between tenants in the multi tenant environments the company operates, and no privacy specific attestation. The collection platform reaches consumers directly through messaging, email and push notification, which raises consumer contact data questions the published material does not address.

No certification, attestation, audit report or trust page is published. For a vendor holding retail and corporate credit files and delinquency data for eighty banking groups, and running multi tenant cloud environments, the absence of any published information security certification is a notable gap rather than a neutral one. Cloud marketplace listings often show security and compliance attestations in a structured field, and any on this vendor's listings are not reflected here.

A software vendor with no license or supervised standing. It works close to the regulatory machinery: it built a Basel calculation engine early in its history, publishes commentary aimed at Gulf central bank rulebook expectations and expected credit loss reporting, and delivered a national collateral registry for a state. Every one of those is a customer relationship or a content exercise rather than a regulatory position held by the firm itself.

Nothing at product level. The company runs a blog series on the EU AI Act and on DORA, category explainer content aimed at its buyers rather than disclosure about its own systems. The blog explains what the rules mean for the category, while the product pages describe the specification. No fairness testing, treatment of protected characteristics in default prediction or governance framework appears in the product material. That matters because behavioral default models built on payment timing and spending patterns are precisely where proxy discrimination arises.

No recourse position published. The exposure is specific to this product set: an early warning classification moves a performing borrower onto a watch list and can trigger repricing, facility withdrawal or restructuring, and a collection strategy assigns contact intensity, yet nothing describes whether the borrower is told, how a wrong classification is challenged, or how responsibility divides between the vendor supplying the model framework and the bank operating it. The bank is the regulated party and carries it.

No model provider, base model or third party analytical engine is named as underpinning its own products. The one disclosed third party dependency runs the other way: the company implements Oracle's financial services analytical applications as a services line, which is somebody else's analytics delivered to a customer rather than a component inside the Loxon products. Where generative capability is discussed it appears in blog material rather than in a product specification naming a supplier.

The lending and collection products are themselves systems of record, and the early warning system is offered either integrated with the retail lending, corporate lending or collection modules or as a standalone deployment against another vendor's stack, which is a real architectural statement rather than a claim. The company joined the Amazon Web Services independent software vendor program in April 2026 and publishes products on that marketplace.

It delivers Oracle financial services analytical applications as an implementation partner, so it integrates with a named third party analytics estate. No core banking connectors are enumerated and integration is described at the level of collecting from source systems.

The deployment half is answered and the residency half is not. Both software as a service and on premises versions of the collection platform exist as separately described products, the newer collection system is cloud native, the early warning module deploys standalone or integrated, and the company runs multi tenant cloud environments on a named public cloud with published operational engineering roles supporting them. Nothing states data residency, region availability, or how data is kept inside a jurisdiction, which matters for a vendor selling across the European Union, the Gulf and Africa simultaneously.

No pricing is published on the vendor's own site. There are no rates, tiers, bands or module prices across a seven product portfolio sold in both software as a service and on premises form. The company lists at least two products on the AWS Marketplace, and marketplace listings routinely carry contract pricing that a vendor never publishes on its own site. Any price on those listings is not reflected here.

More than eighty financial brands and banking groups are reported as customers across Central and Eastern Europe, the Middle East, Africa and Asia Pacific, with offices beyond Budapest in Romania and the Gulf. Buyer types span banks and leasing companies, retail and corporate segments, and both conventional and Islamic banking operations. The Islamic support is a real capability distinction rather than a marketing line, since Islamic products require different profit and default treatment. There is no presence in the largest banking markets, no tier one global institution named, and the customer count is reported by the company without a directory.