DecisioQ Vehicle Leasing Developer Integration Manual

How software developers should incorporate DecisioQ into vehicle leasing platforms, customer portals, pricing engines, fleet leasing systems, and end-of-lease workflows

Vehicle Leasing Industry Edition

Contents

1. Purpose and Scope

2. Recommended Integration Architecture

3. Core System Components

4. Leasing Data to Send to DecisioQ

5. Decision Templates for Vehicle Leasing

6. End-to-End Workflows

7. API Implementation Patterns

8. Security, Privacy, and Compliance

9. Integration with Common Leasing Systems

10. Performance and Scalability

11. User Interface Guidance

12. Testing Strategy

13. Developer Best Practices

14. Implementation Checklist

1. Purpose and Scope

This manual explains how to embed DecisioQ into Vehicle Leasing software systems. It focuses on practical implementation patterns for consumer leasing, commercial fleet leasing, captive finance companies, independent leasing platforms, dealership lease portals, and lease lifecycle management applications.

DecisioQ should be used where the application must evaluate multiple alternatives against configurable weighted criteria, produce an explainable recommendation, and preserve a clear audit trail. In vehicle leasing, that includes approval routing, vehicle matching, lease pricing, renewal offers, end-of-lease disposition, remarketing, inspection outcomes, and fleet allocation decisions.

2. Recommended Integration Architecture

DecisioQ should sit beside the leasing platform as a decision service. The host system remains the system of record for customers, contracts, payments, vehicles, inspections, and accounting. DecisioQ receives structured decision inputs, evaluates templates, returns ranked recommendations, and stores decision history for review.

Customer Portal / Dealer Portal / Leasing CSR UI

|

Leasing Management System (LMS)

|

+---------------- Source Systems ----------------+

| CRM | Credit Bureau | Identity | Inventory | ERP |

| Telematics | Valuation | Insurance | Payments |

+------------------------------------------------+

|

Decision Orchestration Layer

|

DecisioQ API: templates, criteria, alternatives, evaluations, history

|

Recommendation + score + rationale + audit identifier

|

LMS updates quote, application, contract, renewal, or disposition workflow

3. Core System Components

4. Leasing Data to Send to DecisioQ

Send only the data required for the decision. Avoid sending unnecessary personal data. Use normalized numeric values, controlled vocabularies, and stable IDs so decisions can be reproduced later.

5. Decision Templates for Vehicle Leasing

5.1 Lease Application Approval Template

Use this template when a customer submits a lease application and the platform must recommend approve, decline, refer to underwriter, request co-signer, or request additional verification.

POST /api/decisions/evaluate
{
  "templateCode": "LEASE_APPLICATION_APPROVAL_V1",
  "correlationId": "lease-app-983744",
  "subject": { "type": "LeaseApplication", "id": "APP-983744" },
  "alternatives": [
    { "id": "APPROVE", "name": "Approve" },
    { "id": "REFER", "name": "Refer to underwriter" },
    { "id": "REQUEST_DOCS", "name": "Request additional documents" },
    { "id": "DECLINE", "name": "Decline" }
  ],
  "criteria": {
    "creditQuality": 78,
    "affordability": 64,
    "identityAndFraudRisk": 92,
    "customerRelationship": 70,
    "vehicleTermRisk": 61,
    "policyExceptions": 85
  },
  "context": {
    "correlationId": "optional",
    "attributes": {}
  }
}

5.2 Vehicle Recommendation Template

Use this template in customer portals and dealer sales tools to rank vehicles and lease packages. Alternatives can be specific VINs, vehicle trims, or configured lease offers.

// C# example: evaluating vehicle lease offers
var request = new DecisionEvaluationRequest
{
    TemplateCode = "LEASE_VEHICLE_RECOMMENDATION_V1",
    CorrelationId = quote.Id,
    Alternatives = availableOffers.Select(o => new DecisionAlternative
    {

Id = o.OfferId,

Name = $"{o.Year} {o.Make} {o.Model} {o.Trim} - {o.TermMonths} months"

    }).ToList(),
    Criteria = new Dictionary<string, decimal>
    {
        ["budgetFit"] = budgetFitScore,
        ["mileageFit"] = mileageFitScore,
        ["availability"] = availabilityScore,
        ["residualStrength"] = residualScore,
        ["incentiveValue"] = incentiveScore,
        ["customerPreference"] = preferenceScore
    }
};

var result = await decisioQClient.EvaluateAsync(request);
var recommendedOffer = result.RankedAlternatives.First();

6. End-to-End Workflows

6.1 New Lease Origination

1. Customer starts an application through a portal, dealer system, or call center.
2. The LMS validates required fields and retrieves identity, credit, inventory, and pricing data.
3. The orchestration service maps the data into DecisioQ criteria.
4. DecisioQ evaluates approval alternatives and returns a recommendation with score and rationale.
5. The LMS displays the decision to the sales or underwriting user.
6. If accepted, the selected offer is attached to the quote or contract.
7. The system stores the DecisioQ audit ID, template version, inputs, selected outcome, and override reason if applicable.

6.2 Lease Renewal and Upgrade

1. Identify customers within the renewal window.
2. Retrieve payment history, vehicle condition, mileage usage, current incentives, and available inventory.
3. Use DecisioQ to rank renewal, upgrade, extension, buyout, or return options.
4. Present the top recommendations to the customer or account manager.
5. Capture acceptance, rejection, or manual override for continuous improvement.

6.3 End-of-Lease Disposition

7. API Implementation Patterns

7.1 Template Versioning

Every evaluation should reference a template code and version. Never overwrite a template in a way that changes historical meaning. Create a new version when weights, criteria, alternatives, or threshold policy changes.

Recommended template naming:

LEASE_APPLICATION_APPROVAL_V1

LEASE_APPLICATION_APPROVAL_V2

LEASE_VEHICLE_RECOMMENDATION_V1

LEASE_PRICING_OPTIMIZATION_V1

LEASE_RENEWAL_OFFER_V1

LEASE_END_OF_LEASE_DISPOSITION_V1

FLEET_LEASE_ALLOCATION_V1

7.2 Result Handling

{
  "auditId": "DQ-AUD-2026-00044127",
  "templateCode": "LEASE_END_OF_LEASE_DISPOSITION_V1",
  "templateVersion": "1.0",
  "rankedAlternatives": [
    {
      "id": "REFURBISH_RETAIL",
      "name": "Refurbish then retail",
      "overallScore": 86.4,
      "rationale": "Strong market value, manageable repair cost, and high local demand."
    },
    {
      "id": "AUCTION",
      "name": "Send to auction",
      "overallScore": 72.8,
      "rationale": "Fast liquidation but lower expected recovery."
    }
  ],
  "context": {
    "correlationId": "optional",
    "attributes": {}
  }
}

8. Security, Privacy, and Compliance

• Use OAuth2, JWT, or API key authentication based on the deployment model.
• Authorize by role: sales user, underwriter, leasing manager, fleet manager, admin, and auditor.
• Minimize personally identifiable information sent to DecisioQ. Prefer IDs, bands, flags, and normalized scores where possible.
• Encrypt data in transit and at rest. Use tenant isolation for multi-tenant leasing platforms.
• Log every decision with correlation ID, template version, input snapshot, result, selected outcome, user, and timestamp.
• Require override reasons when users choose an outcome different from the recommendation.

9. Integration with Common Leasing Systems

10. Performance and Scalability

• Use synchronous API calls for interactive quote, recommendation, and underwriting screens where users need immediate feedback.
• Use asynchronous batch processing for renewal campaigns, fleet allocation runs, portfolio reviews, and end-of-lease remarketing decisions.
• Cache static reference data such as vehicle classes, branch locations, product rules, and incentive mappings.
• Do not cache live risk, credit, inventory, or inspection results unless your compliance policy allows it.
• Use idempotency keys for retry-safe evaluations in reservation, quote, and contract workflows.
• Record latency, error rate, template usage, and override rate for operational monitoring.

11. User Interface Guidance

Do not show DecisioQ output as a black box. Display the recommendation, rank, score, and main rationale in the leasing workflow. Allow authorized users to inspect criterion contributions when making underwriting, pricing, or end-of-lease decisions.

12. Testing Strategy

13. Developer Best Practices

• Keep DecisioQ integration behind an internal orchestration service instead of calling it directly from browser or mobile clients.
• Use separate templates for approval, pricing, renewal, end-of-lease, fleet allocation, and remarketing.
• Normalize criteria into consistent scales, for example 0 to 100, before evaluation.
• Store template code, version, inputs, outputs, and selected outcome for every decision.
• Treat DecisioQ recommendations as decision support unless your business policy explicitly allows straight-through automation.
• Provide manual override capability with reason codes and role-based approval.
• Review override rates and outcome performance to refine criteria weights over time.

14. Implementation Checklist