Points the Plugin URI at choice.marketing and adds listing screenshots. No functional change; no reconfiguration needed.<\/p>","1.2.2":"
Renames the plugin. Hooks, options, settings, and the webhook URL are unchanged; no reconfiguration needed.<\/p>","1.2.1":"
Corrects the plugin name shown in two admin notices. No functional change; no reconfiguration needed.<\/p>","1.2.0":"
Fixes a duplicate-case bug affecting sites with a persistent object cache, and stops error-response bodies reaching the log. Hooks and webhook URL are unchanged; no reconfiguration needed.<\/p>"},"ratings":[],"assets_icons":{"icon-256x256.png":{"filename":"icon-256x256.png","revision":3669681,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon-512x512.png":{"filename":"icon-512x512.png","revision":3669681,"resolution":"512x512","location":"assets","locale":"","width":512,"height":512}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3669681,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3669681,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.2.2","1.2.3"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3671133,"resolution":"1","location":"assets","locale":"","width":1280,"height":873},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3671133,"resolution":"2","location":"assets","locale":"","width":1280,"height":1687},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3671133,"resolution":"3","location":"assets","locale":"","width":1280,"height":800},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3671133,"resolution":"4","location":"assets","locale":"","width":1280,"height":873}},"screenshots":{"1":"Signifyd settings tab under WooCommerce > Settings, with API key and screening options.","2":"Signifyd Score metabox on the WooCommerce order screen, showing case score and disposition.","3":"The plugin listed on the WordPress Plugins screen.","4":"Signifyd log entries on the WooCommerce Status > Logs screen."}},"plugin_section":[],"plugin_tags":[129025,12891,132861,277981,286],"plugin_category":[45],"plugin_contributors":[277982],"plugin_business_model":[],"class_list":["post-352313","plugin","type-plugin","status-publish","hentry","plugin_tags-chargebacks","plugin_tags-fraud","plugin_tags-fraud-prevention","plugin_tags-signifyd","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_contributors-jaffray","plugin_committers-jaffray"],"banners":{"banner":"https:\/\/ps.w.org\/riskloom-fraud-screening-for-signifyd\/assets\/banner-772x250.png?rev=3669681","banner_2x":"https:\/\/ps.w.org\/riskloom-fraud-screening-for-signifyd\/assets\/banner-1544x500.png?rev=3669681","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/riskloom-fraud-screening-for-signifyd\/assets\/icon-256x256.png?rev=3669681","icon_2x":"https:\/\/ps.w.org\/riskloom-fraud-screening-for-signifyd\/assets\/icon-256x256.png?rev=3669681","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/riskloom-fraud-screening-for-signifyd\/assets\/screenshot-1.png?rev=3671133","caption":"Signifyd settings tab under WooCommerce > Settings, with API key and screening options."},{"src":"https:\/\/ps.w.org\/riskloom-fraud-screening-for-signifyd\/assets\/screenshot-2.png?rev=3671133","caption":"Signifyd Score metabox on the WooCommerce order screen, showing case score and disposition."},{"src":"https:\/\/ps.w.org\/riskloom-fraud-screening-for-signifyd\/assets\/screenshot-3.png?rev=3671133","caption":"The plugin listed on the WordPress Plugins screen."},{"src":"https:\/\/ps.w.org\/riskloom-fraud-screening-for-signifyd\/assets\/screenshot-4.png?rev=3671133","caption":"Signifyd log entries on the WooCommerce Status > Logs screen."}],"raw_content":"\n
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.<\/p>\n\n
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.<\/p>\n\n
wp-config.php<\/code> instead of the database<\/li>\n<\/ul>\n\nChoosing which orders get screened<\/h4>\n\n
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<\/code>) lets you refine that per order.<\/p>\n\nWhat it deliberately does not do<\/h4>\n\n\n- 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.<\/li>\n
- 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.<\/li>\n
- It never changes order status on its own. A
DECLINED<\/code> guarantee stores the disposition and fires the wc_signifyd_case_updated<\/code> action so each store can apply its own policy, rather than cancelling orders behind your back.<\/li>\n<\/ul>\n\nWhich Signifyd API this uses<\/h4>\n\n
This plugin calls the Signifyd V2 Cases API<\/strong>. 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.<\/p>\n\nExtending it<\/h4>\n\n
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<\/code> in the source repository.<\/p>\n\nWho maintains this<\/h4>\n\n
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.<\/p>\n\n
Setup notes and gateway mapping guidance live at Choice OMG<\/a>.<\/p>\n\nExternal services<\/h3>\n\n
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.<\/p>\n\n
When the plugin contacts Signifyd<\/strong><\/p>\n\n\n- When an eligible order is paid, to create a fraud case.<\/li>\n
- When a staff member clicks Refresh, Close Case, or Purchase Guarantee on the order screen.<\/li>\n<\/ul>\n\n
Signifyd also sends data to<\/em> your site, over a signed webhook, when a case is created, rescored, reviewed, or a guarantee completes.<\/p>\n\nWhat is sent<\/strong><\/p>\n\nCreating a case transmits the information Signifyd needs to assess risk:<\/p>\n\n
\n- Order details: order ID, order key, total, currency, creation time, payment gateway, and transaction ID<\/li>\n
- Line items: product IDs, names, URLs, images, quantities, and prices<\/li>\n
- Customer details: name, email address, phone number, billing address, shipping address, and the IP address recorded on the order<\/li>\n
- Account details, for registered customers: username, email, account ID, and registration date<\/li>\n
- Payment risk signals: the gateway's AVS and CVV match results, plus the card BIN, last four digits, and expiry month and year<\/li>\n<\/ul>\n\n
Full card numbers and CVV values are never transmitted; the plugin does not have access to them.<\/p>\n\n
Other calls (refresh, close, guarantee) transmit only the Signifyd case ID.<\/p>\n\n
Service, terms, and privacy policy<\/strong><\/p>\n\n\n- Service: Signifyd<\/a><\/li>\n
- Terms of service: https:\/\/www.signifyd.com\/terms\/<\/a><\/li>\n
- Privacy policy: https:\/\/www.signifyd.com\/privacy\/<\/a><\/li>\n<\/ul>\n\n
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.<\/p>\n\n\n
\n- Upload the plugin to
wp-content\/plugins\/riskloom-fraud-screening-for-signifyd\/<\/code>, or install it from the Plugins screen.<\/li>\n- Activate it through the Plugins screen. WooCommerce must be active.<\/li>\n
- Go to WooCommerce > Settings > Signifyd<\/strong> and enter your Signifyd team API key.<\/li>\n
- On the same screen, choose which payment gateways are screened and which order event creates the case.<\/li>\n
- Copy the webhook URL shown on that screen into the Signifyd console under Settings > Webhooks, subscribed to at least Case Creation, Case Rescore, Case Review, and Guarantee Completion.<\/li>\n<\/ol>\n\n
Keeping the API key out of the database<\/h4>\n\n
Define it in wp-config.php<\/code> instead of using the settings field:<\/p>\n\ndefine( 'WC_SIGNIFYD_API_KEY', 'your-team-api-key' );\n<\/code><\/pre>\n\nThe constant overrides the stored option, and the settings field is shown disabled with a note explaining why.<\/p>\n\n\n
\nDo I need a Signifyd account?<\/h3><\/dt>\nYes. Signifyd performs the screening, so the plugin cannot function without an account and an API key. See the External services section for what is sent.<\/p><\/dd>\n
Does this support the Signifyd V3 Decisions API?<\/h3><\/dt>\nNot currently. It targets the V2 Cases API, which remains available to existing Signifyd teams. Porting to V3 would mainly affect the API client.<\/p><\/dd>\n
Does this store or transmit credit card numbers?<\/h3><\/dt>\nNo. It reads only the risk-signal fields your payment gateway has already stored on the order: AVS and CVV match results, card BIN, last four digits, and expiry. The full card number and the CVV value never pass through the plugin.<\/p><\/dd>\n
Will it cancel orders that Signifyd declines?<\/h3><\/dt>\nNo. The plugin stores the score and disposition and fires the wc_signifyd_case_updated<\/code> action. Acting on a declined guarantee is left to your own code or workflow, so the plugin never cancels or holds an order on its own.<\/p><\/dd>\nMy payment gateway is not Moneris. Will this work?<\/h3><\/dt>\nYes, with a small amount of configuration. The order meta keys the plugin reads card risk signals from are filterable through wc_signifyd_gateway_meta_map<\/code>, and AVS code translation through wc_signifyd_avs_map<\/code>. The defaults target the WooCommerce Moneris gateway because that is the gateway the plugin has run against in production.<\/p><\/dd>\nIs it compatible with High-Performance Order Storage?<\/h3><\/dt>\nYes. All order access goes through the WooCommerce CRUD API, and the plugin declares HPOS compatibility. It works with both legacy post storage and HPOS.<\/p><\/dd>\n
Does purchasing a guarantee cost money?<\/h3><\/dt>\nPurchasing a guarantee is billable on your Signifyd account, so the button asks for confirmation before submitting.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.2.3<\/h4>\n\n\n- Pointed the Plugin URI at the plugin's page on choice.marketing instead of the GitHub repository.<\/li>\n
- Added listing screenshots.<\/li>\n<\/ul>\n\n
1.2.2<\/h4>\n\n\n- Renamed the plugin to \"Riskloom Fraud Screening for Signifyd\" so the name leads with a distinctive term rather than a generic description.<\/li>\n
- Removed the
load_plugin_textdomain()<\/code> call, which WordPress has not needed since 4.6 and this plugin's minimum of 6.0 can never reach.<\/li>\n- Added the plugin owner to the contributor list.<\/li>\n<\/ul>\n\n
1.2.1<\/h4>\n\n\n- Renamed the plugin in both admin notices, which still used the pre-1.2.0 name.<\/li>\n
- Corrected the Plugin URI capitalisation to match the canonical repository path.<\/li>\n
- Regenerated the translation template against the corrected strings.<\/li>\n<\/ul>\n\n
1.2.0<\/h4>\n\n\n- Fixed the AVS mapping comment never being saved, which left that line blank in the order panel on every order.<\/li>\n
- Fixed the duplicate-case guard being ineffective on sites with a persistent object cache, where it could allow two Signifyd cases to be created for one order.<\/li>\n
- Stopped writing Signifyd error-response bodies into the WooCommerce log; only the HTTP status code is recorded now.<\/li>\n
- Renamed the plugin for WordPress.org directory compliance. Internal hooks, options, and the webhook URL are unchanged.<\/li>\n
- Added a translation template, documented every function and class, and added architecture and contributor documentation.<\/li>\n
- Refreshed compatibility: tested against WordPress 7.0 and WooCommerce 11.0.<\/li>\n<\/ul>\n\n
1.1.0<\/h4>\n\n\n- Removed the bundled SDK in favor of the WordPress HTTP API<\/li>\n
- HPOS compatibility<\/li>\n
- Filterable gateway meta map and AVS map<\/li>\n
- Added WooCommerce settings tab and Purchase Guarantee button<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- Initial internal version<\/li>\n<\/ul>","raw_excerpt":"Fraud screening for WooCommerce with Signifyd. Creates cases automatically, receives signed webhook decisions, and adds order-screen controls.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/es.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/352313","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/es.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/es.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/es.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=352313"}],"author":[{"embeddable":true,"href":"https:\/\/es.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/jaffray"}],"wp:attachment":[{"href":"https:\/\/es.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=352313"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/es.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=352313"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/es.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=352313"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/es.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=352313"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/es.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=352313"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/es.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=352313"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}