Skip to main content
Try Free AnalyserBook a Demo
Gateway architecture

One connection layer across lender and service workflows.

Keep your customer application at the top, lender-specific paths behind the gateway and supporting lending services connected as a separate integration layer.

Technical architecture showing Your Application connected to the Xcelet Gateway, which is connected to four placeholder lender workflows and separate lending-service categories.
Experience layerYour Application
Customer journey
Central orchestration layer

Xcelet Gateway

Request mappingConfigured workflowsStatus mapping

Centralized lender and service integration boundary

Configured lender workflows

Lender APlaceholder label
Lender BPlaceholder label
Lender CPlaceholder label
Lender DPlaceholder label
The integration problem

Every new lender shouldn't mean another integration project.

Move repeated lender-specific connection work behind a centralized boundary while keeping the frontend focused on one lending journey.

BeforeRepeated point-to-point integrations
Frontend

FrontendAPI A

FrontendAPI B

FrontendAPI C

Each lender path creates another interface to maintain.
With XceletA centralized gateway boundary
Frontend
Xcelet Gateway
Multiple Lenders
Configured lender workflows remain behind one shared integration layer.
Gateway capabilities

The operational layers behind every integration.

Current project material supports the represented capabilities below. Items without verified implementation detail are clearly marked for confirmation.

Represented in current material Confirm implementation scope
Represented

Integration orchestration

Coordinate configured lender workflows through a centralized gateway layer.

Represented

Data transformation

Current product material references normalized request and mapped status structures.

Represented

Application submission

Package an application for submission through the selected configured lender workflow.

Confirm scope

Status synchronization

Status mapping is represented; synchronization behaviour and cadence require confirmation.

Confirm scope

Error handling

Retry policy, exception paths and operational recovery behaviour require confirmation.

Confirm scope

Webhook/event handling

Supported event sources, delivery behaviour and webhook contracts require confirmation.

Confirm scope

Logging

Log coverage, access, retention and observability behaviour require product confirmation.

Represented

Configuration

Represent lender and product workflow mappings as configured gateway paths.

Error recovery, event delivery, logging and synchronization details are intentionally not marketed as available until verified by Xcelet product teams.

Use cases

A shared integration layer for different lending models.

Use the gateway boundary wherever customer experiences, lending operations and lender-specific workflows need to stay connected.

01

LSP multi-lender

Keep one lending journey connected to the configured workflows of multiple lender partners.

02

Loan marketplaces

Create a shared integration layer between customer applications and lender-specific paths.

03

DSA lender connectivity

Connect loan-distribution operations to configured lender application flows.

04

Embedded lending

Link an embedded customer experience to lending services through a centralized layer.

05

Enterprise lender integrations

Organize lender-specific connection paths behind a consistent integration boundary.