Event Types
This section provides an overview of all webhook event types related to merchant management in the Straumur payment system. These events notify your system about changes to merchant account configurations, such as terminal management activities and merchant or contract status changes.
Terminal added event
This webhook event is triggered when a new terminal has been added to a merchant account, indicating that a new payment terminal is now available for processing transactions. The event provides terminal identification details, merchant information, and contract references for proper terminal management and integration.
Terminal removed event
This webhook event is triggered when a terminal has been removed or deactivated from a merchant account, indicating that the terminal is no longer available for processing new transactions. The event provides terminal identification details, merchant information, and contract references for proper terminal cleanup and system updates.
Contract linked event
This webhook event is triggered when a merchant contract has been linked to a partner contract, indicating that the merchant is now associated with the partner agreement for billing and reporting purposes. Unlike the terminal events, a single contract may have multiple terminals attached at the time of linking, so the payload includes a terminals array describing every terminal currently active on the contract.
Contract unlinked event
This webhook event is triggered when a merchant contract has been unlinked from a partner contract, indicating that the merchant is no longer associated with the partner agreement for billing and reporting purposes. Unlike the contract linked event, no terminal list is included — the payload only contains the identifiers of the parties involved in the separation.
Merchant status changed event
This webhook event is triggered when a merchant's status changes between enabled and disabled — for example when a merchant is enabled after completing onboarding, or disabled by an administrator. A merchant can have several contracts linked to the same partner contract, so this event is raised once per partner contract, listing every one of the merchant's contracts that is linked to it in additionalData.contractNumbers. Unlike ContractStatusChanged, there is no single contractNumber field at the root of the payload.
Contract status changed event
This webhook event is triggered when a single merchant contract's status changes between enabled and disabled — for example when a contract is enabled after onboarding is complete, or disabled by an administrator. Unlike MerchantStatusChanged, this event is only raised for the specific contract whose status changed.
HMAC Signature
By validating the HMAC signature, your system can verify that messages are genuinely from the Straumur and have not been altered in transit.