Skip to main content
guarantee.settled Sent when an accepted guarantee reaches settled state through the clearing process. Use it to mark payment obligations complete and reconcile delivery records.

​
Event fields

​
id
string
required
​
type
string
required
guarantee.settled
​
created_at
string
required
ISO 8601 datetime
​
api_version
string
required
​
data
object
required
​
data.guarantee_id
string
required
​
data.req_id
string
required
​
data.cycle_id
string
required
​
data.version
number
required
1|2
​
data.user_address
string
required
​
data.recipient_address
string
required
​
data.asset_address
string
required
​
data.amount
string
required
Amount in token base units.
​
data.network
string
required
​
data.status
string
required
SETTLED
​
data.settled_at
string
required
ISO 8601 datetime

​
Event examples

Payload
{
  "id": "evt_01JY3M1X7Z4V8Q2H5B6C9N0KRP",
  "type": "guarantee.settled",
  "created_at": "2026-06-22T15:00:00.000Z",
  "api_version": "2026-06-01",
  "data": {
    "guarantee_id": "0xGuaranteeId",
    "req_id": "0x1",
    "cycle_id": "42",
    "version": 1,
    "user_address": "0x1111111111111111111111111111111111111111",
    "recipient_address": "0x2222222222222222222222222222222222222222",
    "asset_address": "0x3333333333333333333333333333333333333333",
    "amount": "100000",
    "network": "eip155:84532",
    "status": "SETTLED",
    "settled_at": "2026-06-22T14:59:58.000Z"
  }
}
  • Match guarantee_id and req_id to the original paid request.
  • Reconcile the amount, asset, payer, recipient, and network before changing entitlement or accounting state.
  • Keep the delivered response hash or artifact reference beside the payment.
  • Treat duplicate or out-of-order deliveries as normal.
See transaction lifecycle and payment proof and audit.