4 docs tagged with "webhooks"

The DSM includes an event system that records every significant action, an inbound webhook framework for receiving data from external systems, and supporting structures for public-facing identity and trust credentials.

The XRM data model is built around merchants - business entities that extend the platform's party model - with supporting records for classification, geographic presence, product catalogues, and external system integration. Understanding how these relate is the key to understanding how Raytio's merchant management works.

The inbound webhook processor is a generic, multi-tenant system for receiving and acting on HTTP webhook events from external providers. A single receiver endpoint handles all providers and tenants. Each registered webhook carries its own signature validation rules and processing logic, eliminating the need for provider-specific code or configuration files.

The State Transitions and Actions table allows definition of the actions that will be taken when the state of application instance changes. For example it is possible to send an email when the state of an instance changes to "Received" (which means that the data receiver has viewed the shared data).