Skip to documentationDocumentation
On this page

invoice.rejected

The invoice closed with a payment that cannot be accepted and nothing accepted.

A timely payment arrived for this invoice but cannot be accepted, and nothing was accepted on the invoice. The invoice is closed with the final status rejected. This event does not credit or debit funds, and no reason is published.

Money and processing#

Do not fulfill the order from this invoice. amount_paid is 0: nothing was accepted on the invoice. If an earlier payment had already been accepted, the invoice closes as underpaid with invoice.underpaid instead, and this event is not sent. While other timely payments for the invoice are still in progress, the invoice waits for them before it closes.

rejected never changes, but it does not promise that no money will ever be accepted. Money accepted on this invoice later arrives as invoice.late_payment, and the invoice stays rejected even when automatic completion of late payments is enabled. Retrieve the invoice to read amount_paid after such an event.

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.rejected" · 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

    The invoice closed because a timely payment cannot be accepted and nothing was accepted (an invoice with an accepted part closes underpaid instead). The status stays rejected even if money is accepted later. No reason is published. · 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.amount_paid · "0" · Required

    —

  • data.status · "rejected" · Required

    —

Example — version 1#

json example
{
  "id": "00000000-0000-0000-0000-000000000001",
  "event_seq": 184203,
  "type": "invoice.rejected",
  "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",
    "amount_paid": "0",
    "status": "rejected"
  }
}

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