Merchant Lifecycle Notifications

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL


        
          
            https://docs.omni-dev.integratedcommerce.io/mcp

Standard setup for AI tools providing an mcp.json file

{
  "Omni API Dev MCP server": {
    "url": "https://docs.omni-dev.integratedcommerce.io/mcp"
  }
}

Subscribe to receive notifications for merchant onboarding lifecycle events — merchant application progress, merchant approval decisions, and pricing template review decisions.

merchant.application.started
merchant.application.submitted
merchant.application.status_changed
merchant.application.requires_action
merchant.application.info_uploaded
merchant.approved
merchant.rejected
pricing_template.approved
pricing_template.rejected

All merchant lifecycle events share one payload shape: an event envelope (id, type, timestamp, and the related merchant id once one exists) and a data section with the application, status transition, and pricing template details that apply to the event type; fields that do not apply are null. Payloads are PII-safe by design — they never carry underwriting documents, bank details, or tax identifiers.

The same rules as transaction notifications apply:

The request body will contain a JSON payload with the details of the event
Each delivery is signed with the svix-id, svix-timestamp and svix-signature headers — see Webhook Configuration for how to verify them