Eventing Reference - Hellgate Cloud Platform

Commerce V1 uses the CloudEvents 1.0 specification for asynchronous service-to-service communication. Events flow between Commerce and your extension services and processor integrations via the mTLS-secured event bridge.

Event Envelope

All events follow the CloudEvents HTTP binding with these required attributes:

Attribute	Description
`ce-specversion`	Always `1.0`
`ce-type`	Identifies the event (e.g., `CardSessionCreated`)
`ce-source`	Event source URI
`ce-id`	Unique event identifier (UUID)
`ce-time`	RFC 3339 timestamp
`Content-Type`	`application/json`

Events sent to Commerce by your integration services.

Event	Description
`CardSessionCreated`	Successful card session result
`CardSessionFailed`	Card session could not be completed
`TDSResult`	Outcome of a 3-D Secure challenge
`Finish`	Transaction result from an integration service

Events sent by Commerce to your integration services.

Event	Description
`CompleteTDSSession`	Outcome of a 3-D Secure session
`SessionVoided`	A payment session was voided
`StateChanged`	Payment state changed
Custom Transaction Event	Flow reached a transaction node
`UbersichtEvent`	Payment lifecycle notification
`CustomerCreated`	A new customer was created
`PaymentMethodSetupChanged`	Payment method setup status changed
`SettlementEvent`	Settlement activity on a payment