DOCS

v1.3.28
 // Pro v1.2.20

 · Latest

Docs/Integrations/Payment Gateway Compatibility

Payment Gateway Compatibility

Overview

Order Daemon includes built-in adapters for Stripe and PayPal. These adapters handle signature verification, event type normalization, and idempotency key computation. A Generic adapter is also available for any service that can send an HTTP POST.

Built-in gateways

Stripe

Webhook URL: https://yoursite.com/wp-json/odcm/v1/webhooks/stripe

Authentication: HMAC via stripe-signature header. Configure your webhook signing secret in Stripe’s dashboard and enter the same value in Order Daemon’s webhook settings.

Supported events: All standard Stripe payment intent and charge events are accepted and normalized into Order Daemon’s Universal Event model. The adapter maps payment confirmation events to the relevant rule triggers.

Setup:

  1. In Stripe Dashboard → Developers → Webhooks, create a new endpoint pointing to the URL above
  2. Copy the signing secret Stripe generates
  3. In WordPress, enter the signing secret in Order Daemon’s webhook configuration

PayPal

Webhook URL: https://yoursite.com/wp-json/odcm/v1/webhooks/paypal

Authentication: PayPal webhook signature verification. Configure using your PayPal app’s webhook ID and credentials.

Supported events: PayPal payment completion and capture events are normalized into the Universal Event model.

Generic

Webhook URL: https://yoursite.com/wp-json/odcm/v1/webhooks/generic/{connection-name}

The Generic adapter accepts webhooks from any service. It does not enforce a specific payload schema.

Authentication: Optional HMAC signing. If no signing secret is configured on the connection, the endpoint operates in permissive mode and accepts all requests.

When to use: Any external service that can send HTTP POST requests – automation platforms (Zapier, Make), custom APIs, scheduled pings (see Scheduled Automations).

WooCommerce payment method compatibility

Order Daemon’s rule triggers fire on WooCommerce order lifecycle events (woocommerce_order_status_changed, woocommerce_payment_complete), not directly on gateway callbacks. This means rules work with any WooCommerce-compatible payment gateway – if WooCommerce can process the payment and update the order status, Order Daemon’s triggers will fire.

Known edge cases:

ScenarioNotes
Block CheckoutFull compatibility. Order Daemon includes explicit Block Checkout support in the core plugin.
Buy Now Pay LaterRules fire when the payment is eventually completed, not when the order is created
Cash on DeliveryPayment complete trigger will not fire – use the Order Processing trigger instead
Stripe Radar holdsOrders blocked by Radar are placed on-hold. Use the Order On-Hold trigger Pro to handle these.

Adding support for a custom gateway

If your payment gateway sends webhooks that don’t fit the Stripe or PayPal schema, you can write a custom gateway adapter. See Architecture and the AbstractGatewayAdapter class at src/Core/Events/Adapters/AbstractGatewayAdapter.php.

Custom adapters are registered via the odcm_register_gateway_adapters action hook. See Hooks & Filters Reference.