docs.vin

deceasedAccount

The deceasedAccount noun — identity, lifecycle, events, and every capability as an anchored section: 5 capabilities, 0 live, 5 sandbox, 0 declared.

deceasedAccount is one of the estate's 317 automotive nouns — a job a car needs done. It carries 5 capabilities: 0 live, 5 sandbox, 0 declared · doors aggregator.vin.

Identity

NoundeceasedAccount
PillarServices (facets: 1 data · 3 services · 1 commerce)
Capabilities5 — 0 live · 5 sandbox · 0 declared
EntitiesLoanServicing
Doorsaggregator.vin
SDKVin.deceasedAccount.* from apis.vin
Address/catalog/deceasedAccount#{action} — the anchor IS the wire name minus deceasedAccount.

Events

The vocabulary this noun can append to the record — 5 past-tense, versioned event types, each linked to the capability that emits it:

Apply & book

probateClaimFile

deceasedAccount.probateClaimFile · POST /deceased-accounts/probate-claim-file · gate key · sandbox · answers DeceasedAccountProbateClaimFile@1

No input — this capability takes no request body.

Door — aggregator.vin serves this noun on its two routes: / (the landing) · /5NMJBCDE6RH339459 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

Emits — DeceasedAccount.probateClaimFiled@1.

the SDK — deceasedAccount.probateClaimFile
import { deceasedAccount } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await deceasedAccount.probateClaimFile()
POST /deceased-accounts/probate-claim-file
curl -X POST https://apis.vin/deceased-accounts/probate-claim-file \
  -H 'content-type: application/json' \
  -d '{}'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-16T14:50:09.751Z · HTTP 200
{
  "type": "OK",
  "answers": "DeceasedAccountProbateClaimFile@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "deceasedAccount",
    "asOf": "2026-08-10",
    "servicing": {
      "status": "no-open-loan"
    },
    "probateClaim": {
      "status": "no-death-notice-on-file",
      "basis": "no-cast-identity-deceased"
    },
    "payer": {
      "name": "Ava Good",
      "castRow": "super-prime",
      "creditTier": "super-prime"
    }
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "deceasedAccount",
    "asOf": "2026-08-10",
    "servicing": {
      "status": "no-open-loan"
    },
    "probateClaim": {
      "status": "no-death-notice-on-file",
      "basis": "no-cast-identity-deceased"
    },
    "payer": {
      "name": "Ava Good",
      "castRow": "super-prime",
      "creditTier": "super-prime"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "hardship-desk-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Fulfill & operate

notify

deceasedAccount.notify · POST /deceased-accounts/notify · gate key · sandbox · answers DeceasedAccountNotify@1

No input — this capability takes no request body.

Door — aggregator.vin serves this noun on its two routes: / (the landing) · /5NMJBCDE6RH339459 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

Emits — DeceasedAccount.notified@1.

the SDK — deceasedAccount.notify
import { deceasedAccount } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await deceasedAccount.notify()
POST /deceased-accounts/notify
curl -X POST https://apis.vin/deceased-accounts/notify \
  -H 'content-type: application/json' \
  -d '{}'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-16T14:50:09.750Z · HTTP 200
{
  "type": "OK",
  "answers": "DeceasedAccountNotify@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "notificationRef": "DAN-001O",
    "accountStatus": "flagged-deceased",
    "collectionSuspended": true,
    "creditLifeReviewOpened": true,
    "probateHoldPlaced": true,
    "nextStep": "await-estate-representative",
    "asOf": "2026-08-10"
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "notificationRef": "DAN-001O",
    "accountStatus": "flagged-deceased",
    "collectionSuspended": true,
    "creditLifeReviewOpened": true,
    "probateHoldPlaced": true,
    "nextStep": "await-estate-representative",
    "asOf": "2026-08-10"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "legal-authority-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Lifecycle & state

collectionSuspend

deceasedAccount.collectionSuspend · POST /deceased-accounts/collection-suspend · gate key · sandbox · answers DeceasedAccountCollectionSuspend@1

No input — this capability takes no request body.

Door — aggregator.vin serves this noun on its two routes: / (the landing) · /5NMJBCDE6RH339459 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

Emits — DeceasedAccount.collectionSuspended@1.

the SDK — deceasedAccount.collectionSuspend
import { deceasedAccount } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await deceasedAccount.collectionSuspend()
POST /deceased-accounts/collection-suspend
curl -X POST https://apis.vin/deceased-accounts/collection-suspend \
  -H 'content-type: application/json' \
  -d '{}'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-16T14:50:09.750Z · HTTP 200
{
  "type": "OK",
  "answers": "DeceasedAccountCollectionSuspend@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "deceasedAccount",
    "asOf": "2026-08-10",
    "servicing": {
      "status": "no-open-loan"
    },
    "suspension": {
      "status": "no-death-notice-on-file",
      "basis": "no-cast-identity-deceased"
    },
    "payer": {
      "name": "Ava Good",
      "castRow": "super-prime",
      "creditTier": "super-prime"
    }
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "deceasedAccount",
    "asOf": "2026-08-10",
    "servicing": {
      "status": "no-open-loan"
    },
    "suspension": {
      "status": "no-death-notice-on-file",
      "basis": "no-cast-identity-deceased"
    },
    "payer": {
      "name": "Ava Good",
      "castRow": "super-prime",
      "creditTier": "super-prime"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "hardship-desk-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

More actions

assumption

deceasedAccount.assumption · POST /deceased-accounts/assumption · gate key · sandbox · answers DeceasedAccountAssumption@1

No input — this capability takes no request body.

Door — aggregator.vin serves this noun on its two routes: / (the landing) · /5NMJBCDE6RH339459 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

Emits — DeceasedAccount.assumed@1.

the SDK — deceasedAccount.assumption
import { deceasedAccount } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await deceasedAccount.assumption()
POST /deceased-accounts/assumption
curl -X POST https://apis.vin/deceased-accounts/assumption \
  -H 'content-type: application/json' \
  -d '{}'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-16T14:50:09.750Z · HTTP 200
{
  "type": "OK",
  "answers": "DeceasedAccountAssumption@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "assumptionRef": "DAA-001O",
    "assumingParty": "SANDBOX, PAT",
    "priorBorrower": "ESTATE OF SANDBOX, A",
    "assumptionApproved": true,
    "remainingPrincipal": {
      "amount": "9891.00",
      "currency": "USD"
    },
    "dueOnDeathWaived": true,
    "newAccountStatus": "assumed-current",
    "requiredDocuments": [
      "certified-death-certificate",
      "assumption-agreement",
      "credit-authorization"
    ],
    "asOf": "2026-08-10"
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "assumptionRef": "DAA-001O",
    "assumingParty": "SANDBOX, PAT",
    "priorBorrower": "ESTATE OF SANDBOX, A",
    "assumptionApproved": true,
    "remainingPrincipal": {
      "amount": "9891.00",
      "currency": "USD"
    },
    "dueOnDeathWaived": true,
    "newAccountStatus": "assumed-current",
    "requiredDocuments": [
      "certified-death-certificate",
      "assumption-agreement",
      "credit-authorization"
    ],
    "asOf": "2026-08-10"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "legal-authority-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

creditLifePayoff

deceasedAccount.creditLifePayoff · POST /deceased-accounts/credit-life-payoff · gate key · sandbox · answers DeceasedAccountCreditLifePayoff@1

No input — this capability takes no request body.

Door — aggregator.vin serves this noun on its two routes: / (the landing) · /5NMJBCDE6RH339459 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

Emits — DeceasedAccount.creditLifePaidOff@1.

the SDK — deceasedAccount.creditLifePayoff
import { deceasedAccount } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await deceasedAccount.creditLifePayoff()
POST /deceased-accounts/credit-life-payoff
curl -X POST https://apis.vin/deceased-accounts/credit-life-payoff \
  -H 'content-type: application/json' \
  -d '{}'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

receipt · executed 2026-08-16T14:50:09.750Z · HTTP 200
{
  "type": "OK",
  "answers": "DeceasedAccountCreditLifePayoff@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "noun": "deceasedAccount",
    "asOf": "2026-08-10",
    "servicing": {
      "status": "no-open-loan"
    },
    "claim": {
      "status": "no-death-notice-on-file",
      "basis": "no-cast-identity-deceased"
    },
    "payer": {
      "name": "Ava Good",
      "castRow": "super-prime",
      "creditTier": "super-prime"
    }
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "noun": "deceasedAccount",
    "asOf": "2026-08-10",
    "servicing": {
      "status": "no-open-loan"
    },
    "claim": {
      "status": "no-death-notice-on-file",
      "basis": "no-cast-identity-deceased"
    },
    "payer": {
      "name": "Ava Good",
      "castRow": "super-prime",
      "creditTier": "super-prime"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "hardship-desk-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Data model

The record shape behind this noun — one entity, each property an evidence field. See the whole estate model on the data model page.

LoanServicing

Modeled

The noun drawn out — its record shape, its lifecycle, and how it is exercised end to end. 2 diagrams, rendered from the estate model.

DeceasedAccount · Class model

DeceasedAccount · State machine

Generated from the catalog. Every capability, answer, gate, and entity on this page is a rendered descriptor — it cannot drift from the wire.

deal

The deal noun — identity, lifecycle, events, and every capability as an anchored section: 24 capabilities, 0 live, 24 sandbox, 0 declared.

detail

The detail noun — identity, lifecycle, events, and every capability as an anchored section: 19 capabilities, 0 live, 19 sandbox, 0 declared.

On this page

Identity
Events
Apply & book
probateClaimFile
Fulfill & operate
notify
Lifecycle & state
collectionSuspend
More actions
assumption
creditLifePayoff
Data model
LoanServicing
Modeled