Ingest lifecycle event
Report a payment lifecycle event for a prior decision so Specter can keep the case and your fraud backends up to date.
Reference the decision via decision_id. Specter advances the decision’s payment state, forwards the event to the
backends that participated in that decision, and stores a log entry with each backend’s delivery status. A backend
that does not support the event type is reported as skipped rather than failing the request.
Authorizations
HS256-signed JWT bearer token, obtained via the OAuth2 client-credentials grant (see Authentication).
Body
Event request
Lifecycle event ingestion request.
Event-type-specific payload. The fields depend on the event type — see Lifecycle events.
The Specter decision this event is linked to.
"1e7b9c0a-2d43-4f6a-8d29-c4a1f2d05b3e"
When the payment event occurred (ISO 8601).
"2026-06-01T10:04:00Z"
The type of payment lifecycle event.
authorization, capture, refund, void, chargeback, fraud_report, failed Response
Event entry
Persisted lifecycle event log entry.
"4a8c2e6d-7f1b-4d9a-b3e5-9c6f2a8d4e1b"
Event-type-specific payload. The fields depend on the event type — see Lifecycle events.
"1e7b9c0a-2d43-4f6a-8d29-c4a1f2d05b3e"
"2026-06-01T10:04:00Z"
"2026-06-01T10:04:02Z"
authorization, capture, refund, void, chargeback, fraud_report, failed "authorization"