Signifyd¶

Signifyd provides guaranteed fraud protection with chargeback reimbursement. After a payment is authorized, the extension submits the order to Signifyd's Orders API for a guarantee decision — orders Signifyd approves are covered by its chargeback reimbursement guarantee. Use it when you want a post-authorization approve/decline/pending decision backed by a financial guarantee rather than pre-payment screening.

What It Provides¶

• A FraudScoringStrategy implementation registered under the provider name signifyd (per-provider registration). The core fraud engine resolves it with channel-enablement awareness — see Fraud Scoring Extensions.
• Post-payment scoring (score_post_payment) — the primary method. Submits the order to POST https://api.signifyd.com/v3/orders after payment authorization and maps the response:
  • guaranteeDisposition: DECLINED → block
  • guaranteeDisposition: PENDING, or signifydScore below block_threshold → review
  • guaranteeDisposition: APPROVED → allow
  • otherwise, signifydScore below review_threshold → review, else allow
• Guarantee tracking — the returned score carries guarantee_status (approved / declined / pending), Signifyd's recommendedAction, the Signifyd order ID as the provider transaction ID, and signals (signifyd_score, guarantee_disposition, order_outcome).
• Order submission payload — purchase total and currency, confirmation email, shipment destination, product line items, billing address, card BIN / last four / AVS and CVV response codes, browser IP, device fingerprint and session ID, and the user account (email, phone, name, created date, account ID).
• Decision feedback (report_decision) — sends the merchant's review disposition back to Signifyd via PUT /v3/orders/{order_id} for model training.
• Checkout and login scoring return allow with score 0 by design — Signifyd scoring happens post-authorization only. For pre-payment screening, see IPQualityScore or MaxMind minFraud.

Setup¶

1. Enable Signifyd for the channel under Settings > Extensions (extension enablement is per-channel).
2. Provide the API key from your Signifyd dashboard. api_key is a secret config field (encrypted at rest and masked in the admin); the strategy factory also falls back to the SIGNIFYD_API_KEY and SIGNIFYD_TEAM_ID environment variables — see the credential-resolution note under Operational Notes.
3. Tune review_threshold and block_threshold if you want score-based holds in addition to the guarantee disposition.

Configuration Reference¶

Permissions¶

This extension declares no permissions in its manifest.

Operational Notes¶

• Inverted score scale — Signifyd scores run 0–1000 where higher is safer. The thresholds are lower bounds (an order scoring below block_threshold is worse than one below review_threshold), and the raw score is inverted (1 - score/1000) onto the platform's 0–1 risk scale.
• Post-authorization means no charge abort — because scoring runs after payment authorization, a block decision does not stop the charge; the order's fraud status is set to pending_review and the order moves to HeldForReview. A review decision sets pending_review without changing order status.
• Fail-open — with no API key configured, or on any API failure (logged as a warning), the strategy returns allow with score 0. Order submission uses a 15-second timeout; decision feedback uses 10 seconds.
• Authentication — requests use HTTP Basic auth with the base64-encoded API key.
• One provider per channel — if more than one fraud extension is enabled on a channel, checkout logs a warning and uses the alphabetically-first provider name.