feat: Add Nextiva Connector in Dashboard#4923
Conversation
Registers the Nextiva connector (PayConex by Bluefin) in the Control Center: adds the NEXTIVA processor variant, connector list entry, name/display-name/info mappings, and a placeholder gateway icon. Auth is BodyKey (api_key = API access key, key1 = Account ID), supplied to the config form via the euclid wasm. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Changed Files
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 53c55a1c3b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Processors(TOKENIO), | ||
| Processors(PAYLOAD), | ||
| Processors(PAYTM), | ||
| Processors(NEXTIVA), |
There was a problem hiding this comment.
Gate Nextiva until its WASM config is bundled
When a merchant selects this newly listed card, the onboarding page calls Window.getConnectorConfig(connector) in ConnectorAccountDetails.res; the bundled public/hyperswitch/wasm/euclid currently has no nextiva entry (getConnectorConfig("nextiva") throws), so the page falls into the error state before any auth fields can render. Please include the regenerated WASM config in this change or keep Nextiva out of connectorList until that artifact is available.
Useful? React with 👍 / 👎.
XyneSpaces
left a comment
There was a problem hiding this comment.
Review Summary
Classification: New Connector Registration — Nextiva (PayConex/Bluefin)
Risk Level: Low
Files Changed: 3 files (ConnectorTypes.res, ConnectorUtils.res, placeholder SVG)
Verification Against Control Center Checklist
Tier 1 — Naming Consistency:
✅ Connector variant naming — NEXTIVA follows uppercase convention
✅ String mapping — "nextiva" lowercase matches existing pattern
✅ Display name — "Nextiva" matches branding
✅ Description info — nextivaInfo follows existing pattern
Registration Completeness:
✅ processorTypes variant added
✅ connectorList entry added
✅ getConnectorNameString mapping added
✅ getConnectorNameTypeFromString reverse mapping added
✅ getProcessorInfo mapping added
✅ getDisplayNameForProcessor mapping added
Findings
🔍 Placeholder icon acknowledged
The PR body notes the SVG is a placeholder. Ensure the official Nextiva/PayConex logo replaces this before merge.
💡 Merge coordination required
This PR depends on the WASM PR (#4922) for the auth form fields to render correctly. The PR body correctly notes this dependency — ensure both merge together.
Verdict: ✅ Clean connector registration following established patterns. Replace placeholder icon before merge.
XyneSpaces
left a comment
There was a problem hiding this comment.
Review Summary
Classification: Connector Registration — Nextiva Dashboard Integration
Scenario: connector-new-integration
Risk Level: Low
Files Changed: 3 files (1 SVG, 2 ReScript source files)
Verification Against Control Center Checklist
Tier 1 — Naming Consistency:
✅ Variant name NEXTIVA follows UPPER_CASE convention matching sibling connectors
✅ String mapping "nextiva" matches lowercase kebab-case pattern
✅ Display name "Nextiva" uses Title Case
✅ Info variable nextivaInfo follows camelCase pattern
Tier 2 — Pattern Alignment:
✅ Connector added to connectorList array in alphabetical position (after PAYTM, before PHONEPE)
✅ All 5 required mappings present: type variant, list entry, name string, reverse mapping, processor info, display name
✅ Description follows existing format — provider name, service category, region
Findings
🔍 Placeholder SVG icon
The NEXTIVA.svg is a placeholder with a simple "N" text. Per PR body, this should be replaced with the official Nextiva/PayConex logo before merge.
Fix: Replace placeholder with official logo SVG or add a TODO comment in the PR description tracking the logo acquisition.
💡 Connector description could include UCS indicator
The description states "secure payment services" but doesn't indicate this is a UCS-only connector. Meritors may expect direct connector behavior.
Suggestion: Consider appending "(UCS)" to the description or display name to set correct expectations, matching patterns used for other UCS-only connectors if any exist.
Dependency Verification
| Dependency | Status | Notes |
|---|---|---|
| Backend connector support (hyperswitch#12608) | ✅ Linked | UCS-only connector registration |
| WASM config regeneration | ⏳ Pending | PR body notes separate WASM PR needed |
| Official logo SVG | ⏳ Pending | Placeholder currently in place |
Verdict:
Summary
Registers the Nextiva connector (PayConex by Bluefin) in the Control Center dashboard so merchants can configure it. Backend support: hyperswitch PR #12608.
Nextiva is a UCS-only connector. Auth is
BodyKey:api_key— PayConex API access keykey1— PayConex Account IDChanges
src/screens/Connectors/ConnectorTypes.res— addNEXTIVAtoprocessorTypessrc/screens/Connectors/ConnectorUtils.res—connectorListentry,nextivaInfo,getConnectorNameString("nextiva"), reverse mapping,getProcessorInfo,getDisplayNameForProcessor("Nextiva")public/hyperswitch/assets/Gateway/NEXTIVA.svg— gateway icon (placeholder — replace with the official Nextiva/PayConex logo before merge)The auth fields (API access key + Account ID) are rendered from the euclid wasm config, regenerated in the companion WASM PR.
🤖 Generated with Claude Code