feat: Add FRM connector list config

[muditbhutani]

Type of Change

• New feature

Description

Adds FRM (Fraud & Risk Management) connectors to the live-mode connector_list_for_live config pipeline, bringing FRM in line with how paymentProcessors, payoutProcessors, threedsAuthProcessors and vaultProcessors are already configured.

Previously the FRM processor selection screen always rendered the hardcoded FRMInfo.frmList, with no way to control which FRM connectors are surfaced in live mode via config. This wires FRM through the same config.toml → getConnectorListForLive → Recoil atom flow as the other connector categories.

Changes

• config/config.toml — add frmProcessors key under [default.connector_list_for_live].
• ConnectorListForLiveFromConfigTypes.res — add frmProcessorsLiveList to the connectorListForLive record.
• ConnectorListForLiveFromConfigUtils.res — extract frmProcessors from config (typed via FRMPlayer) with a frmConnectorListForLive fallback when config is empty.
• ConnectorUtils.res — add the frmConnectorListForLive default list.
• FRMSelect.res — use frmProcessorsLiveList when isLiveMode is enabled, otherwise the existing frmList.

Motivation and Context

Closes #4946

How did you test it?

• npm run re:build compiles cleanly with no type errors.
• Verified generated output: FRMSelect.res.js resolves featureFlagDetails.isLiveMode ? frmProcessorsLiveList : FRMInfo.frmList.
• The config strings (signifyd, riskified, cybersourcedecisionmanager) match the FRMPlayer branch of getConnectorNameTypeFromString, so they resolve to the correct FRM(...) variants.

Checklist

• I formatted the code npm run re:format
• My changes generate no new warnings

[semanticdiff-com]

Review changes with  

[XyneSpaces]

Automated Review Summary

PR: feat: Add FRM connector list config
Reviewer: XyneSpaces Automation

Findings

Found 1 critical issue that will break compilation:

---

🚨 Critical: Typo in FRM connector variant name

File: src/screens/Connectors/ConnectorUtils.res

The added frmConnectorListForLive uses FRM(Riskifyed) but the correct variant name in the codebase is RISKIFIED (spelled with "-ied", not "-yed").

Current (incorrect):

let frmConnectorListForLive: array<connectorTypes> = [
  FRM(CybersourceDecisionManager),
  FRM(Signifyd),
  FRM(Riskifyed),  // ❌ Wrong spelling
]

Should be:

let frmConnectorListForLive: array<connectorTypes> = [
  FRM(CybersourceDecisionManager),
  FRM(Signifyd),
  FRM(Riskified),  // ✅ Correct spelling
]

This typo will cause a compilation error since the variant Riskifyed does not exist in the FRMPlayer type definition.

---

Positive Notes

• Clean implementation following the existing pattern for paymentProcessorsLiveList, payoutProcessorsLiveList, etc.
• Proper fallback to default list when config is empty
• Good use of FRMPlayer connector type for typed extraction
• Consistent with the existing config → atom → component consumption flow

---

Verdict: 🔴 Changes Requested — Fix the variant typo before merge.

[XyneSpaces]

Code Review: FRM Connector List Config

Following the control-center review checklist:

Tier 1 — High Signal Issues

✅ Naming Consistency — Pattern follows existing paymentProcessors, payoutProcessors convention. Field name frmProcessorsLiveList is consistent with siblings.

⚠️ Naming Inconsistency Found: In ConnectorUtils.res, line adds FRM(Riskifyed) but the variant name should be Riskified (typo: "Riskifyed" vs "Riskified"). Please verify this matches the actual variant definition in the codebase.

Other Findings

✅ Feature Flag Gating — Correctly uses featureFlagDetails.isLiveMode to toggle between config-driven and hardcoded lists.

✅ Blast Radius — New field frmProcessorsLiveList added to record type; fallback pattern mirrors other processor types.

Minor Suggestion

In config/config.toml, the config uses lowercase strings: ["signifyd","riskified","cybersourcedecisionmanager"]. Consider adding a comment noting these must match the string representations expected by getConnectorNameTypeFromString for the FRMPlayer branch.

[XyneSpaces]

📋 Review Summary

Overall Assessment: ✅ Looks good with minor note

Key Findings

Severity	Finding
⚠️ Minor	Possible typo: Riskifyed → should verify this matches the actual variant name (likely Riskified)

What was reviewed

• ✅ Naming consistency with existing connector list patterns
• ✅ Feature flag gating implementation
• ✅ Blast radius analysis for new record field
• ✅ Config → type resolution flow

Action Items

• Verify Riskifyed variant name is correct (or fix to Riskified)

---

Reviewed by: Hyperswitch Reviewer Agent

[Muditbhatia12]

Should cybersourcedecisionmanager be added to prod? It was just added for a demo.