Skip to main content

Payment Event Types

This section provides an overview of all webhook event types related to payment processing in the Straumur payment system. These events notify your system about the various stages of payment transactions, allowing you to track and respond to payment lifecycle changes.

Available Event Types​

The payment webhook system supports the following event types:

Authorization​

Event: Authorization

This event is triggered when a payment authorization has been processed and informs you of the outcome of a payment request.

Auto-capture is the default

Unless a payment is configured for manual or delayed capture, it is captured immediately. In that case, a successful Authorization event (success: "true") is your fulfilment signal — the funds have already been captured, and no separate Capture event is sent. See the Capture event below.

One checkout can send several Authorization events

A shopper who is declined can retry in the same session, and each attempt sends its own Authorization event. Expect one or more success: "false" events before a success: "true" — or before the session expires with no further event. See One checkout, several Authorization events.

Capture​

Event: Capture

When we have processed your capture request, we send you a webhook event with the outcome.

Only sent for manual or delayed capture

You will only receive a Capture event for payments created with isManualCapture or captureHoursDelay. Payments captured immediately (the default) never get a separate Capture event — the Authorization event above already confirms the funds were captured.

Adjustment​

Event: Adjustment

This event is triggered when the new amount has been authorized.

Refund​

Event: Refund

This event is triggered when a refund has been processed for a payment.

Tokenization​

Event: Tokenization

This event is triggered when a tokenization request has been successfully completed. It indicates that a new payment token has been created and is ready for use in future transactions.

Token Disabled​

Event: TokenDisabled

This event is triggered when a payment token has been deactivated or disabled in the system. Once disabled, the token can no longer be used for future transactions.

Token Updated​

Event: TokenUpdated

This event is triggered when a payment token has been updated.

Offer Closed​

Event: OfferClosed

This event is triggered when a payment offer has expired — for example, because the shopper abandoned the session. For cards, offers expire after 12 hours by default. The payload carries the transaction references along with the outcome of the event.