feat(router): add retry support for debit routing #8220
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of Change
Description
In the case of debit routing flow, the routing output (
CallConnectorType
) will include both the connector and its associated card network. In our current implementation, we simply iterate over the connector list and pass the connector. With the updated requirement, we will also need to pass the corresponding card network for each connector in the case of debit routing.Additional Changes
Motivation and Context
How did you test it?
Create a business profile and enable debit routing for it
-> Create a adyen connector
-> I have created a db entry that contains the wrong card network so that the payment can be retried
-> the payment response contains two attempts
-> List all the attempts for a payments
-> The payment was first tried with


star
card network and then with thevisa
Checklist
cargo +nightly fmt --all
cargo clippy