Why this exists
Signifyd leaves WooCommerce out. It supports Magento 2, Salesforce Commerce Cloud, and BigCommerce. Stores on WooCommerce with a Signifyd contract have to write their own REST API client or screen orders by hand. We hit that gap while running a WooCommerce store that was taking chargebacks, so we wrote the integration ourselves. It ran in production. Then we released it under GPL rather than leave it in one client's site.
What it does
- Creates a Signifyd case automatically when an eligible order is paid, building it from the order server-side.
- Verifies each inbound webhook with HMAC-SHA256 before trusting it, then stores the risk score and guarantee disposition with the order.
- Adds an order-screen panel for staff. From there, they can view the case, refresh it, close it, or purchase Signifyd's financial guarantee.
- Maps payment-gateway meta through a filter, so it isn't locked to one gateway.
- Works with High-Performance Order Storage and legacy post storage.
- Ships no vendor SDK. Its API client is a few hundred lines built on the WordPress HTTP API.
- Reads the API key from
wp-config.phpwhen you'd rather it never touch the database.
What it deliberately does not do
It never handles card numbers or CVV values. The only payment fields it reads are risk signals your gateway already stored. Those are the AVS and CVV match results, the card BIN, the last four digits, and the expiry.
It never logs request or response bodies. Logging goes through the WooCommerce logger. It records order IDs, case IDs, and status codes.
It never changes order status itself. No store should inherit a default that cancels orders behind an operator's back. On a declined guarantee, it stores the disposition and fires an action hook so each store applies its own policy.
What gets sent to Signifyd
Screening happens on Signifyd's servers. So each case sends them customer data: the order, its line items, and the gateway's risk signals. It also carries the customer's name, email, phone, billing and shipping addresses, and the IP recorded on the order. Sending customer personal data to a third party is a privacy decision, not just a technical one. Before the plugin goes live, review your privacy policy and your obligations under GDPR, CCPA, PIPEDA, or whichever regime applies.
Requirements
You need WordPress 6.0 or newer, PHP 7.4 or newer, WooCommerce 6.0 or newer, and a Signifyd account. It needs a team API key. The plugin targets Signifyd's V2 Cases API, though Signifyd promotes its V3 Decisions API for new integrations. Existing teams keep V2 access. Confirm with your Signifyd account team which version your credentials are provisioned for.
Who maintains it
Choice OMG maintains this plugin. We're a digital marketing and web agency in Edmonton, Alberta, founded in 2010. We run Web Optimization, Google Ads, and web design for our clients on flat monthly fees. Like most of our tooling, it came out of client work.
Talk to us if you run WooCommerce and are fighting chargebacks. The same goes if you want your store's tracking and attribution to be as solid as its fraud screening.