Vehicle leasing integrations use DecisioQ when an application needs to compare lease alternatives, explain recommendations, and preserve a clear decision audit trail across origination, pricing, renewal, portfolio management, damage review, and end-of-lease disposition workflows.

The current public automotive catalog does not expose Vehicle Leasing as a separate top-level sector. Leasing-related decisions are currently represented through active catalog sectors such as Fleet Vehicle Management and New Car Dealership, and through reusable Decision Preparation Model assets for lease portfolio workflows.

Because of that, client applications should always load the Decision Catalog and use the returned Sector, Category, Decision, Decision Preparation Model, and Scenario metadata. Do not invent a Vehicle Leasing sector code or hard-code old decision identifiers unless they are returned by the active catalog endpoint.

Leasing applications should use the same discovery flow as the Business Decision Studio:

1. Load GET /decisioncatalog through the approved server-side Decision Catalog gateway.
2. Populate Sector from catalog.sectors[]. For leasing workflows, common current sectors include AUTO-FLEET for fleet lease portfolio decisions and AUTO-NCD for dealership lease offers, finance, incentives, and customer lifecycle decisions.
3. Populate Category from selectedSector.categories[].
4. Populate Decision from selectedCategory.decisions[] when available, or call /decisioncatalog/sectors/{sectorCode}/categories/{categoryCode}/decisions.
5. Display Decision Name only in the dropdown while keeping decisionId as the option value.
6. Load full decision detail from /decisioncatalog/decisions/{decisionId} before rendering Guided Data Collection.

For regional deployments, keep DecisioQ technical identifiers stable and localize only user-facing labels and guidance. Unless the selected endpoint and decision schema explicitly support unit-qualified input, convert mileage, distance, pressure, temperature, mass, volume, speed, fuel consumption, and other measurements to the required canonical units before submission. Do not infer units or currency from locale.

Vehicle leasing integrations should map lease application, customer, vehicle, pricing, contract, inspection, residual, remarketing, and portfolio data into decision-specific Business Data. The selected decision detail defines which criteria are required and how each value should be measured.

Do not invent criterion IDs. Use the canonical criteria returned by /decisioncatalog/decisions/{decisionId}, including criterion overview metadata, unit, direction, scale, and data guidance.

1. Authenticate through the approved server-side identity flow. Browser pages should not directly handle credentials.
2. Load the Decision Catalog and let the user choose Sector, Category, Decision, Decision Preparation Model, and Scenario.
3. Load decision detail and render Guided Data Collection from returned criteria.
4. User or system prepares Business Data for candidate lease offers, vehicles, contracts, customers, renewal actions, damage cases, or disposition actions.
5. Call POST /api/v1/validate to validate and prepare the decision input before execution.
6. Call POST /api/v1/decide to return the authoritative Decision Result.
7. Display recommendation, ranked alternatives, warnings, assumptions, and Explanation of Decision Result.
8. Keep execution trace and diagnostics collapsed by default for developer and integrator review.

The exact fields depend on the selected catalog decision. The example below shows the integration style for a leasing workflow rather than a guaranteed schema for every decision.

{
  "decisionId": "AUTO-FLEET-014",
  "decisionPreparationModelId": "AUTO-FLEET-PROFILE-STANDARD",
  "scenarioId": "AUTO-FLEET-SCENARIO-LEASE-RENEWAL",
  "businessData": {
    "correlationId": "lease-renewal-20260717-1042",
    "workflow": "Lease Renewal Review",
    "portfolioId": "LEASE-PORTFOLIO-NE",
    "options": [
      {
        "optionId": "RENEWAL-OFFER-36M-LOW-PAYMENT",
        "label": "36 Month Low Payment Renewal",
        "values": {
          "customerFitScore": 88,
          "residualRiskScore": 32,
          "profitabilityScore": 74,
          "retentionValueScore": 90,
          "operationalReadinessScore": 81
        }
      },
      {
        "optionId": "UPGRADE-OFFER-NEW-MODEL",
        "label": "Upgrade to Newer Model",
        "values": {
          "customerFitScore": 82,
          "residualRiskScore": 45,
          "profitabilityScore": 86,
          "retentionValueScore": 84,
          "operationalReadinessScore": 70
        }
      }
    ]
  }
}

Call DecisioQ from a trusted backend service. Keep identity credentials, account verification, and service configuration outside public browser code.

async function executeVehicleLeasingDecision(jwtToken, preparedDecisionInput) {
  const response = await fetch(`${process.env.DECISIOQ_BASE_URL}/api/v1/decide`, {
    method: "POST",
    headers: {
      "Authorization": `Bearer ${jwtToken}`,
      "Content-Type": "application/json"
    },
    body: JSON.stringify(preparedDecisionInput)
  });

  const payload = await response.json();

  if (!response.ok) {
    throw new Error(payload.message || "Decision execution failed.");
  }

  return payload;
}

• Use a guided decision selector: Sector, Category, Decision, Decision Preparation Model, and Scenario.
• Show Selection Overview for sector, category, and decision metadata so business users understand the decision before entering data.
• Render Guided Data Collection from criterion definitions and show criterion overview summaries where available.
• Display Decision Name in selectors and show the selected decisionId separately for developers and integrators.
• For leasing staff, keep screens focused on recommendation, reason, required action, warnings, and next step.
• Keep execution trace and diagnostics available to integrators but collapsed by default.
• Never expose internal proxy URLs, service credentials, signing keys, or account verification details in browser code.

• Confirm each leasing workflow maps to a decision actually returned by the active Decision Catalog.
• Validate Business Data before execution and show user-friendly validation messages.
• Persist correlation ID, customer ID, application ID, contract ID, VIN, stock number, portfolio ID, decision ID, profile ID, scenario ID, selected option, score, and explanation for audit.
• Retain the successful decision response requestId with the host business transaction, then call POST /api/v1/decision-outcomes when the action and realized result are known.
• Require an overrideReason for overridden recommendations; never infer acceptance merely because a result was displayed.
• Monitor GET /api/v1/decision-outcomes/summary for acceptance rate, override rate, and realized-value aggregates. Treat outcome feedback as reporting evidence, not automatic model training.
• Keep finance, compliance, and contract eligibility rules deterministic where required; use DecisioQ for multi-factor ranking, prioritization, and recommendation decisions.
• Monitor preview failures, execution failures, account verification errors, timeout rates, and unexpected warning counts.
• Review Decision Preparation Models and scenario assumptions with leasing, finance, remarketing, compliance, and portfolio owners when policies or market conditions change.