Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

store network_transaction_id for off_session payments irrespective of the is_connector_agnostic_mit_enabled config #7084

Open
ShankarSinghC opened this issue Jan 22, 2025 · 0 comments · May be fixed by #7083
Assignees
Labels
A-core Area: Core flows A-payments Area: payments C-refactor Category: Refactor

Comments

@ShankarSinghC
Copy link
Contributor

Currently, we store the network_transaction_id for the setup_mandate/off_session payments only if the is_connector_agnostic_mit_enabled config is enabled. During the MITs, we refer to this flag to decide whether to use the connector_mandate_id or the network_transaction_id for the MIT.

Instead of using the flag for multiple purposes, it should be used solely to determine whether to use the connector_mandate_id or the network_transaction_id for the MIT. Therefore, this change will ensure that the network_transaction_id is always stored for off-session payments if it is present in the connector response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-core Area: Core flows A-payments Area: payments C-refactor Category: Refactor
Projects
None yet
1 participant