Connect commercetools with Signifyd to automate fraud screening, reduce chargebacks, and keep more good orders flowing through your checkout with policy-based decisioning.
• Order data from commercetools (line items, totals, currency, customer, addresses, and delivery method) is mapped to Signifyd case fields for case creation and scoring.
• Payment-related attributes available in commercetools (method, transaction IDs, and authorization status when present) are forwarded to Signifyd as part of the case payload.
• Case creation is triggered on defined order lifecycle events, with idempotency keys used to prevent duplicate cases during retries or event replays.
• Signifyd decisions are consumed via webhook callbacks and mapped to commercetools order custom fields, state transitions, or tags for downstream handling.
• Decision updates (approve, decline, review, and subsequent changes) are processed as deltas, with timestamps and correlation IDs stored for traceability.
• Errors and webhook signature validation outcomes are logged, and failed deliveries are retried with backoff to protect both APIs under load.
.png)
We map commercetools order, customer, device, and payment signals into Signifyd, then push approve, decline, or review back as order updates or custom fields.
Typical payloads include cart and line items, billing and shipping details, IP and device context, payment method metadata, and order history when available.
Yes, we wire Signifyd outcomes to commercetools state machines so declines cancel, reviews hold fulfillment, and approvals proceed without manual steps.
Yes, we configure per-store policies, currencies, and thresholds, and route decisions based on project, channel, or store key.
We add structured logging, replayable webhooks, and alerting for decision delays or API errors, so ops can spot issues before they hit fulfillment.




