Update sessionData after /setup call #2504
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.
Summary
We weren't updating our internal
sessionData
after a newsessionData
blob is returned from the/setup
call.Although the original blob remains valid, best practice says that we should always use the latest
sessionData
returned by the backendTested scenarios
A
/payments
call made using thesessionData
returned from the/setup
call, instead of the one from the original/session
call, succeeds in making a payment.