Credit exposure ( credit_exposure )

Role

Where the receivable receivable aggregates existing invoices to answer “how much does this buyer owe me?”, the credit_exposure exposure answers “how much credit have I granted this buyer, and how much remains open?”.

Exposure is a persisted object — unlike receivable, it is not recalculated from invoices. It is built explicitly by orchestration processes, movement by movement, through an immutable ledger. This lets it cover flows that do not yet have an issued invoice, such as credit authorization or financing an order in progress, or that involve a financing company.

There is at most one exposure per tuple (buyer_id, merchant_id, currency).

Identifier and structure

Each exposure has a stable identifier prefixed with cex_. Every ledger movement uses prefix cem_.

{
"object": "credit_exposure",
"id": "cex_2b4d1f8a9c3e7f5b",
"buyer_id": "cmp_3a8f1d9c2b4e7f6a",
"merchant_id": "mer_1a2b3c4d5e6f7a8b",
"currency": "eur",
"status": "active",
"authorized_amount_excluding_tax": 500000,
"authorized_amount_including_tax": 600000,
"consumed_amount_excluding_tax": 100000,
"consumed_amount_including_tax": 120000,
"released_amount_excluding_tax": 0,
"released_amount_including_tax": 0,
"settled_amount_excluding_tax": 83334,
"settled_amount_including_tax": 100000,
"cancelled_amount_excluding_tax": 0,
"cancelled_amount_including_tax": 0,
"expired_amount_excluding_tax": 0,
"expired_amount_including_tax": 0,
"outstanding_amount_excluding_tax": 416666,
"outstanding_amount_including_tax": 500000,
"movements": [
  {
    "id": "cem_1a2b3c4d5e6f7a8b",
    "type": "credit_granted",
    "amount_excluding_tax": 500000,
    "amount_including_tax": 600000,
    "source_type": "checkout_session",
    "source_id": "cs_5e2d8f1a9b3c4d7e",
    "created_at": "2026-06-17T10:00:00.000Z"
  },
  {
    "id": "cem_9f2e1a4b3c8d7e6f",
    "type": "credit_settled",
    "amount_excluding_tax": 83334,
    "amount_including_tax": 100000,
    "source_type": "payment",
    "source_id": "pay_4a7b2e9f1c3d8a5e",
    "created_at": "2026-06-18T09:15:00.000Z"
  }
],
"metadata": {},
"created_at": "2026-06-17T10:00:00.000Z",
"updated_at": "2026-06-18T09:15:00.000Z"
}

Fields

Amount counters

Exposure accumulates six pairs of counters (excluding tax + including tax). Each action on exposure increments one counter and may reduce active outstanding balance.

Active outstanding balance (outstanding_amount_*) is calculated in real time:

outstanding = max(0, authorized − released − settled − cancelled − expired)

Each counter and the field outstanding exist on two bases (_excluding_tax and _including_tax). At least one basis must be provided for an action.

Movement ledger

The field movements is an append-only ledger — every action on exposure creates an immutable movement. It is the complete history of credit granted to this buyer.

Status

Interaction with the credit limit

The credit limit defines the authorized ceiling; exposure tracks what is actually committed. Available credit is the difference between the two.

available = credit_limit.effective_amount − credit_exposure.outstanding_amount

The nodes credit.evaluate_credit_availability and credit.check_credit_availability automatically calculate this comparison and produce an object credit_availability_check with the following fields:

{
"object": "credit_availability_check",
"decision": "approved",
"reason": "within_limit",
"basis": "excluding_tax",
"currency": "eur",
"limit_amount": 500000,
"used_amount": 416666,
"requested_amount": 50000,
"available_amount": 83334,
"projected_used_amount": 466666,
"projected_available_amount": 33334
}

When decision is rejected, the reason is insufficient_available_credit. The process then routes to a decline path or request for additional collateral.

In processes

Exposure is entirely driven by process nodes — there is no automatic update triggered by other objects.

Typical flow: credit authorization

Here is the common shape of a credit-decision process during checkout:

credit.evaluate_credit_availability (company, requested amount)
→ approved → credit.grant_credit → create checkout session / order
→ rejected → notify buyer or request collateral

Typical flow: close after payment

payment.matched or psp_payment.succeeded
→ credit.fetch_credit_exposure (company)
→ credit.settle_credit_exposure (received amount)
→ [if outstanding = 0] credit.cancel_credit_exposure

Events

Every exposure action emits a distinct event. The payload includes the complete exposure state before and after the movement, plus the movement itself in latest_movement.

The event credit_exposure.granted is emitted both at creation (first action grant) and on every subsequent increase in authorized outstanding balance.