Summary
Add automated test coverage for the Fraud Risk Management (FRM) feature using Signifyd as the FRM connector alongside Stripe as the payment processor.
Motivation
The FRM feature allows merchants to evaluate payment fraud risk using external connectors. Automated Cypress tests are needed to verify the FRM flow works correctly end-to-end.
What needs to be added
- New Cypress spec:
cypress-tests/cypress/e2e/spec/Payment/52-FRM.cy.js
- Connector config for Signifyd:
cypress-tests/cypress/e2e/configs/Payment/Signifyd.js
- Register FRM connectors in
Utils.js
- Fix
createNamedConnectorCallTest to handle payment_vas connector type with frm_configs array
Test scenarios
Tests run with CYPRESS_CONNECTOR=stripe; Signifyd handles FRM evaluation via email triggers:
- APPROVE:
testapproved@signifyd.com → expects status: succeeded
- DECLINE:
testdeclined@signifyd.com → expects status: failed
- HOLD:
testpending@signifyd.com → expects status: requires_customer_action
Paperclip Reference
Paperclip issue: B-61
Summary
Add automated test coverage for the Fraud Risk Management (FRM) feature using Signifyd as the FRM connector alongside Stripe as the payment processor.
Motivation
The FRM feature allows merchants to evaluate payment fraud risk using external connectors. Automated Cypress tests are needed to verify the FRM flow works correctly end-to-end.
What needs to be added
cypress-tests/cypress/e2e/spec/Payment/52-FRM.cy.jscypress-tests/cypress/e2e/configs/Payment/Signifyd.jsUtils.jscreateNamedConnectorCallTestto handlepayment_vasconnector type withfrm_configsarrayTest scenarios
Tests run with
CYPRESS_CONNECTOR=stripe; Signifyd handles FRM evaluation via email triggers:testapproved@signifyd.com→ expectsstatus: succeededtestdeclined@signifyd.com→ expectsstatus: failedtestpending@signifyd.com→ expectsstatus: requires_customer_actionPaperclip Reference
Paperclip issue: B-61