Store and payment webhooks
Configure Shopify, WooCommerce or Stripe webhooks where the connection requires them.
Updated 9 August 2026Why use webhooks
Webhooks send order or payment events from the originating system to Incendium server to server. They complement browser tracking by capturing confirmed business events even when a purchaser closes the page quickly, a browser request is interrupted or the payment completes outside the original session.
The result is a stronger revenue record for reporting and attribution. Browser activity still matters because it supplies the journey; the webhook supplies an authoritative outcome.
Available webhook routes
Use the Incendium instructions and authentication details shown in the WooCommerce webhook card.
Configure the required Shopify webhook topics and use the project-specific destination supplied in Incendium.
Use payment_intent.succeeded for one-time payments or invoice.paid for subscriptions, unless the project has an agreed alternative.
Configure safely
Open the correct webhook card
Go to Settings → Connections → Integrations and find the relevant provider under Webhooks.
Copy the project-specific values
Use the exact endpoint, key or secret shown for this project. Do not reuse values from another site.
Select the minimum required events
Subscribe only to the order or payment states Incendium needs. This reduces noise and lowers the risk of duplicate outcomes.
Send a controlled test
Complete a test order or use the provider’s test facility, then confirm delivery and the resulting Incendium event.
Avoid duplicate revenue
- Use a stable order, payment or invoice identifier.
- Do not treat both an authorisation and a captured payment as separate sales.
- Define how refunds, cancellations and failed payments should be handled.
- Check for retries: webhook providers may send the same event more than once.
- Verify that browser and webhook routes reconcile to one business outcome.