Skip to content

01The engine

What the engine does, and what it never does. Reading, checking and assessing. Never deciding.

The engine never decides a loan. Your bank keeps its own KYC, AML checks, credit policy and approval. Stedlan shortens the work; it never replaces the bank’s decision.

  1. 01

    Reads documents in Arabic and English

    Salary certificates, bank statements, social security statements, IDs and credit bureau reports become structured data.

  2. 02

    Checks and cross-checks

    Type, legibility, expiry, name and ID match, consistency across documents, such as salary against bank credits, and tamper signals. Doubtful documents go to a person.

  3. 03

    A deterministic, explainable assessment

    Ratios, capacity and a loan-readiness score from a versioned rule set. The same file always gets the same result, and every run records the documents used, the rules version and the reasons.

  4. 04

    An expert on every package

    Credit experts on the Stedlan review desk will check the data, correct it where needed and approve every package. Each expert action will be logged with its reason.

  5. 05

    Back-testing on your own history

    Before relying on it, a bank can back-test the engine on its own historical, anonymised data, to a standard its risk team accepts.

  6. 06

    An engine API, later

    An API to run the engine inside a bank’s own systems is planned for a later phase.

02Why it helps

Less chasing. More deciding. What a bank gains from a prepared file.

  • Complete files

    Applications are designed to arrive with the documents a credit officer needs, already checked, with an index of every document and a plain statement of what was checked and by whom.

  • Less time chasing documents

    The aim: relationship managers and analysts spend less time asking for missing papers and rebuilding files by hand. A pilot will measure it.

  • Consistent, explained results

    Written, versioned rules give the same result for the same file, and every number comes with its reason.

03How data works

Clients own their files. Banks will see them only with consent.

  • No client data inside the engine

    The engine a bank licenses contains rules, models and code. It never contains client data.

  • Consent, per bank and purpose

    A bank sees a file only with the client’s consent, for that bank and that purpose. Withdrawn, access ends.

  • Sending follows the Central Bank

    Stedlan will send files only once the Central Bank of Jordan confirms the route. Until then, clients bring their signed package.

  • Packages you can verify

    Each package is signed and carries a verification code. The check shows who issued it, when, whether it is still valid, and the SHA-256 of each PDF to compare. Never personal data.

    Check a package

  • Methodology from public practice

    Written from standard, public credit practice, calibrated with pilot data. Never any bank’s confidential policy.

  • Free for clients

    Clients never pay. Banks will pay for the engine.

04Pilot

Talk to us about a pilot.

We are looking for a first bank to back-test the engine on its own anonymised history, or to pilot it with consenting clients.

Pilots

We discuss pilots directly with banks. Write to us with the subject “Pilot” and tell us what you would like to test.

hello@stedlan.com