Reference · built on requestConnectorPayments, billing & fraud

Signifyd

Checkout and sale decisions, reroutes, returns, and chargebacks from Signifyd through the v3 API and webhooks.

Request accessPricing ↗

About

Signifyd is an ecommerce fraud protection service. Its v3 API at api.signifyd.com takes an order at one of three checkpoints (CHECKOUT, SALE, RETURN) and returns a decision of ACCEPT, REJECT, or HOLD. Later events update the same order: transactions after authorization, reprices, reroutes, fulfillments, returns, chargebacks, and representment outcomes. Webhooks notify your endpoint when something changes.

An operator reads decisions and chargeback events and proposes a hold, a release, or a chargeback record for your approval, with a receipt of who decided what.

This is a reference listing. It documents what Fibric would read from Signifyd and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • The latest decision for an order through GET /orders/{orderId}/decision, and batches through Get Decisions
  • Checkout and Sale events as they are recorded, keyed by a consistent orderId
  • Chargeback, claim, and representment summaries returned when a chargeback is created
  • Post-sale actions and their feedback through the PostSale Action endpoints
  • Webhook deliveries for the topics you register, one URL per webhook

Proposed actions

  • Target capability: propose recording a Sale event through POST /orders/events/sales, or a Checkout then Transaction pair
  • Target capability: propose a Reroute or Reprice event when the ship-to or the amount changes
  • Target capability: propose recording a chargeback through POST /orders/events/chargebacks
  • Target capability: propose a Fulfillments update or a Record Return event

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Hold a risky order before it ships

    HOLD and REJECT decisions are read as they arrive. The operator proposes a hold in the order system and records the decision alongside it.

    With Order Risk

  • Assemble chargeback evidence

    When a chargeback is recorded, the operator gathers fulfillment and transaction detail from the order and drafts the representment packet for review.

    With Chargeback Evidence

  • Re-check after a ship-to change

    An address change triggers a proposed Reroute event so Signifyd can return a fresh decision before the label prints.

    With Ship-To Change

  • Route returns by decision

    Record Return events and post-sale actions are read with the original decision. Returns on held orders are flagged for a person.

    With Returns Triage

Requirements

  • A Signifyd team with test and production credentials
  • An orderId that stays the same across all purchase attempts for one order
  • A webhook endpoint on TLS 1.2 or 1.3 with one of the cipher suites Signifyd lists
  • Device profiling data collected on your storefront, as the Getting Started guide describes
Authentication
An API key from the Signifyd console (Settings > Team > API keys), sent as the HTTP Basic username; a SIGNIFYD-TEAM-ID header selects the team when one key covers several.

Limits

  • An order can be updated up to 100 times to generate a new decision; further updates return REJECT
  • purchase.createdAt is set once per order and cannot be changed by later events
  • A chargeback that already exists returns 409 and is not created or updated
  • A 429 response signals rate limiting; the reference publishes no thresholds

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Signifyd ↗

Questions and answers

What are the checkpoints and decisions?
Checkpoints are CHECKOUT (before payment authorization), SALE (after), and RETURN. Signifyd returns ACCEPT, REJECT, or HOLD. In a pre-auth flow you call Checkout, then Transaction after the gateway responds. In a post-auth flow you call Sale alone.
How are webhooks set up?
Through POST /teams/{teamId}/webhooks with the URL to notify. More than one webhook per topic is allowed. The endpoint must use TLS 1.2 or 1.3 with a listed cipher suite. Webhooks can be listed, updated, deleted, and tested through the API.
What happens if the same order is sent twice?
A Checkout or Sale with an existing orderId updates the order and produces a new decision. purchase.createdAt is kept from the first event. After 100 updates, further updates return REJECT.
Ask about Signifyd

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Signifyd through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy