Riskloom Fraud Screening for Signifyd

Signifyd has no official WooCommerce integration. It ships supported plugins for
Magento 2, Salesforce Commerce Cloud, and BigCommerce, leaving WooCommerce stores
to build their own. This plugin is that integration, written directly against
Signifyd’s REST API using WordPress’s own HTTP client.

When an eligible order is paid, the plugin builds a case from the order and
submits it to Signifyd for screening. Signifyd returns its risk score and
guarantee decision over a signed webhook, which the plugin verifies and stores on
the order. Staff get a compact panel on the order screen showing the score and
disposition, with buttons to refresh the case, dismiss it, or purchase Signifyd’s
financial guarantee.

Features

• Creates a Signifyd case automatically when an eligible order is paid
• Verifies signed webhooks (HMAC-SHA256) and stores the resulting score and
  guarantee disposition on the order
• Order-screen panel for staff: view case, refresh, close case, purchase guarantee
• Filterable payment-gateway meta mapping, so the plugin is not tied to one gateway
• Compatible with High-Performance Order Storage (HPOS)
• No bundled SDK and no vendor dependencies; the API client is a few hundred lines
  on top of the WordPress HTTP API
• API key can live in wp-config.php instead of the database

Choosing which orders get screened

Screening is limited to the payment gateways you select on the settings screen,
so only credit-card orders are sent. You choose whether the case is created on
payment completion or when the order reaches processing status. A filter
(wc_signifyd_order_is_eligible) lets you refine that per order.

What it deliberately does not do

• It never handles card numbers or CVV values. Only risk-signal fields your
  gateway has already stored are read: AVS and CVV match results, card BIN, last
  four digits, and expiry.
• It never writes request or response bodies to logs. Logging goes through the
  WooCommerce logger and records order IDs, case IDs, and status codes only.
• It never changes order status on its own. A DECLINED guarantee stores the
  disposition and fires the wc_signifyd_case_updated action so each store can
  apply its own policy, rather than cancelling orders behind your back.

Which Signifyd API this uses

This plugin calls the Signifyd V2 Cases API. Signifyd’s current documentation
promotes the V3 Decisions API for new integrations, and V2 remains available to
existing teams. Confirm with your Signifyd account team which API version your
credentials are provisioned for before installing.

Extending it

Ten filters and actions are available, covering gateway meta mapping, AVS code
translation, order eligibility, the full case payload, request timeout, and a
post-update action for custom workflow. The full reference lives in
docs/ARCHITECTURE.md in the source repository.

Who maintains this

Choice OMG maintains this plugin. We are a digital marketing and web agency in
Edmonton, Alberta, and we wrote it because a client’s WooCommerce store needed
Signifyd screening that Signifyd does not ship for WooCommerce. It runs in
production on that store against the Moneris gateway.

Setup notes and gateway mapping guidance live at
Choice OMG.

External services

This plugin connects to Signifyd, a third-party fraud-screening service. It is
not usable without a Signifyd account, because screening happens on Signifyd’s
servers rather than in WordPress.

When the plugin contacts Signifyd

• When an eligible order is paid, to create a fraud case.
• When a staff member clicks Refresh, Close Case, or Purchase Guarantee on the
  order screen.

Signifyd also sends data to your site, over a signed webhook, when a case is
created, rescored, reviewed, or a guarantee completes.

What is sent

Creating a case transmits the information Signifyd needs to assess risk:

• Order details: order ID, order key, total, currency, creation time, payment
  gateway, and transaction ID
• Line items: product IDs, names, URLs, images, quantities, and prices
• Customer details: name, email address, phone number, billing address, shipping
  address, and the IP address recorded on the order
• Account details, for registered customers: username, email, account ID, and
  registration date
• Payment risk signals: the gateway’s AVS and CVV match results, plus the card
  BIN, last four digits, and expiry month and year

Full card numbers and CVV values are never transmitted; the plugin does not have
access to them.

Other calls (refresh, close, guarantee) transmit only the Signifyd case ID.

Service, terms, and privacy policy

• Service: Signifyd
• Terms of service: https://www.signifyd.com/terms/
• Privacy policy: https://www.signifyd.com/privacy/

Because customer personal data is transmitted to a third party, review your own
privacy policy and any applicable data-protection obligations (GDPR, CCPA, PIPEDA
and similar) before enabling this plugin on a live store.