fix(router): store network_transaction_id
in stripe authorize
flow
#5399
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
Now we are trying to store the
network_transaction_id
that comes in the latest_attempt of the authorize response instead we should be storing thenetwork_transaction_id
that comes in thelatest_charge
object.Additional Changes
Motivation and Context
How did you test it?
-> Create mca for stripe
-> Create a payment with
steup_future_usage: off_session
0 amount-> Create a payment with
steup_future_usage: off_session
with some amountChecklist
cargo +nightly fmt --all
cargo clippy