Skip to documentationDocumentation
On this page

invoice.late_payment

Late payment received on an expired invoice.

A payment was accepted after being first detected on or after the payment deadline, or while the invoice was already closed. A transfer detected before the deadline is not late solely because its blockchain confirmations take longer.

Money and processing#

late_payment_amount, gross_amount, fee_total, and net_amount describe this accepted payment. The payload does not include cumulative amount_paid; retrieve the invoice to read that total.

With automatic completion enabled, the same acceptance can also produce invoice.paid or invoice.overpaid with another event ID. The late-payment payload can retain the closed status from before that completion. Decide fulfillment from current GET state and never sum both event credits.

A rejected invoice never changes status: a late payment on it is reported only by this event, with status: rejected, even when automatic completion is enabled.

Schema version 1#

Fields are taken from the public OpenAPI contract. Required nullable fields must be present and may contain null.

  • id · string · Required

    Stable event UUID for merchant-side idempotency. · Format: uuid

  • event_seq · integer · Required

    Global event sequence. Gaps are possible; it does not establish delivery or processing order. · Format: int64

  • type · "invoice.late_payment" · Required

    —

  • schema_version · 1 · Required

    —

  • environment · "live" | "test" · Required

    —

  • merchant_id · string · Required

    Format: uuid

  • subject_type · "invoice" · Required

    —

  • subject_id · string · Required

    Format: uuid

  • occurred_at · string · Required

    Canonical business occurrence timestamp. · Format: date-time

  • data · object · Required

    All amounts, including late_payment_amount, are denominated in the invoice's currency and network. Cross-asset recovered payments use their frozen invoice-equivalent values; actual source and settlement amounts remain on the invoice payments. gross_amount − fee_total = net_amount. · Unknown properties are rejected

  • data.invoice_id · string · Required

    Format: uuid

  • data.external_id · string | null · Required

    —

  • data.currency · string · Required

    —

  • data.network · string · Required

    —

  • data.environment · "live" | "test" · Required

    —

  • data.amount_requested · string · Required

    Format: decimal · Pattern: ^\d+(.\d+)?$

  • data.late_payment_amount · string · Required

    Format: decimal · Pattern: ^\d+(.\d+)?$

  • data.status · "expired" | "underpaid" | "invalid" | "rejected" · Required

    —

  • data.gross_amount · string · Required

    Format: decimal · Pattern: ^\d+(.\d+)?$

  • data.fee_total · string · Required

    Format: decimal · Pattern: ^\d+(.\d+)?$

  • data.net_amount · string · Required

    Format: decimal · Pattern: ^\d+(.\d+)?$

Example — version 1#

json example
{
  "id": "00000000-0000-0000-0000-000000000001",
  "event_seq": 184203,
  "type": "invoice.late_payment",
  "schema_version": 1,
  "environment": "live",
  "merchant_id": "00000000-0000-0000-0000-000000000002",
  "subject_type": "invoice",
  "subject_id": "00000000-0000-0000-0000-000000000003",
  "occurred_at": "2026-09-14T10:00:00Z",
  "data": {
    "invoice_id": "00000000-0000-0000-0000-000000000003",
    "external_id": null,
    "currency": "USDC",
    "network": "ethereum",
    "environment": "live",
    "amount_requested": "25.00",
    "late_payment_amount": "10.00",
    "status": "expired",
    "gross_amount": "10.00",
    "fee_total": "0.10",
    "net_amount": "9.90"
  }
}

See delivery and envelope, signature verification, and business processes.