Skip to main content
Xcelet

Product

Connect once. Integrate with many.

One boundary between your lending applications and the lenders and services behind them, with a normalised request, response and status model.

Lender routing
Customer application
Xcelet Integration Gateway
Lender A
Lender B
Lender C

status updates return through the same mapping

Problem

Every new lender becomes another integration project.

Lender APIs differ in fields, status vocabulary and error behaviour. Handling that inside the borrower journey means the front end changes each time the lender panel does.

Lifecycle

Where the gateway sits in the lending lifecycle.

Acquire, verify, assess, decide, disburse, service and collect run against one application record. The highlighted stages are the ones this product operates in.

Where the gateway sits in the lending lifecyclein scope
  1. 01

    Acquire

    Capture enquiry

  2. 02

    Verify

  3. 03

    Assess

    Statement parsing

  4. 04

    Decide

    Eligibility rules

  5. 05

    Disburse

    Document completion

  6. 06

    Service

  7. 07

    Collect

Capabilities

What the gateway handles.

01

Normalised requests

Send one application structure regardless of the destination lender.

02

Data mapping

Translate fields into each lender's expected format.

03

Status mapping

Bring lender-specific statuses into one consistent progression.

04

Routing rules

Select destinations based on configured criteria and priorities.

05

Response model

Return outcomes to the journey in a single, predictable shape.

06

Service connectivity

Reach verification, bureau, mandate and payment services through the same boundary.

Workflow

How an application reaches a lender.

  1. Step 01

    Application

    The journey submits a completed case to the gateway.

  2. Step 02

    Routing

    Configured criteria select the matching lender workflow.

  3. Step 03

    Mapping

    Fields are translated into the lender's expected structure.

  4. Step 04

    Submission

    The case is sent to the lender's interface.

  5. Step 05

    Status

    Lender responses are normalised into a shared progression.

  6. Step 06

    Visibility

    Teams and borrowers see one consistent application status.

Ecosystem

One connection point for the services lending depends on.

Xcelet maps external services into a consistent request and response model, so lending workflows do not carry provider-specific logic.

  • Identity

    KYC, KYB and verification services.

  • Bureau

    Credit bureau data and risk signals.

  • Account Aggregator

    Consent-based financial data connectivity.

  • Mandates

    Repayment mandate setup and status flows.

  • Payments

    Disbursement and repayment payment rails.

  • Banking

    Bank account and transaction infrastructure.

  • Communication

    Customer messaging and notification services.

  • Lenders

    Lender application and status connectivity.

Categories shown. Specific provider availability depends on the agreed implementation scope.

Next step

Add lenders without rebuilding the front end.

Tell us which lenders and services you connect to today and we will map them behind one interface.

Not ready for a conversation? Try the free Bank Statement Analyser.