Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

This pull request refactors how the default fallback routing configuration is updated when a merchant connector account is modified. Instead of calling the old helper function, the logic is now handled through a new MerchantDefaultConfigUpdate struct with methods that more explicitly update or remove the connector from the routing algorithm, depending on whether the connector is disabled. The changes also ensure that the connector update uses a clone of the merchant connector account object.

Routing configuration update refactor:

• Replaces the old update_default_fallback_on_mca_update helper with explicit logic using the MerchantDefaultConfigUpdate struct, which updates or deletes the connector from the default fallback routing algorithm based on the connector's status. This makes the update process more modular and easier to maintain. [1] [2]
• Removes the now-unused update_default_fallback_on_mca_update function from routing/helpers.rs.

Code quality and correctness:

• Ensures the update_merchant_connector_account call receives a clone of the mca object, preventing potential issues with ownership or mutation.
• Cleans up imports by removing the now-unused update_default_fallback_on_mca_update import.

Additional Changes

• This PR modifies the API contract
• This PR modifies the database schema
• This PR modifies application configuration/environment variables

Motivation and Context

How did you test it?

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed the submitted code
• I added unit tests for my changes where possible