Transaction webhooks (available soon) - Byzantine Finance

Transaction events track the lifecycle of a deposit or withdrawal. Subscribe to them to reconcile funding and settlement in your own system.

Populated fields

Each transaction event sets transactionId and accountId in the envelope’s related block. The other related keys are null.

Event types

Event	Fires when
`transaction.withdrawal_initiated`	A withdrawal has been signed and placed in the vault’s withdrawal queue.
`transaction.waiting_for_funds`	Byzantine is waiting for incoming funds.
`transaction.payment_in_review`	The payment is under review.
`transaction.funds_in_transfer`	Funds are being transferred.
`transaction.funds_received`	Funds have been received.
`transaction.processing`	The transaction is being processed on-chain.
`transaction.completed`	The transaction completed successfully.
`transaction.simulation_failed`	The transaction simulation failed.
`transaction.reverted`	The transaction was reverted.

For status meanings and polling as an alternative to webhooks, see Tracking Transactions.

Example payload

{
  "id": "00000000-0000-4000-8000-000000000001",
  "type": "transaction.completed",
  "occurredAt": "2026-06-03T15:00:00Z",
  "livemode": true,
  "payloadVersion": 1,
  "related": {
    "accountId": "b3f2d2dc-6abc-40fa-b2d2-d6d76b839c09",
    "userId": null,
    "entityId": null,
    "beneficiaryId": null,
    "transactionId": "53f2d2dc-6abc-40fa-b2d2-d6d76b839c09"
  },
  "data": {
    "status": "completed"
  }
}