ADR-007: Maximum native Hyperswitch bias
ADR-007: Maximum native Hyperswitch bias
Status
Accepted (2026-05-28)
Context
mvs-pay could rebuild many Hyperswitch features MVS-side: routing rule editor, dunning logic, cost analytics, etc. Each rebuild is a maintenance burden and competes with upstream.
Decision
Default: surface every Hyperswitch feature through the SDK or UI. Override only via a counter-ADR explaining why MVS-side rebuild is justified.
Consequences
- Smaller MVS-side surface to maintain.
- Native features (Smart Retries, decision-engine, Cost Observability, Revenue Recovery) are first-class consumers.
- MVS-side rebuilds (custom IIAS substantiation, custom HSA receipts, custom Plaid Link UX) require explicit ADR justifying why Hyperswitch can’t handle it.
Alternatives considered
- MVS-first: rebuild what we can MVS-side for stronger control. Rejected because we picked Hyperswitch specifically for these features.