CA update #13
Merged
CA update #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
CA Update for M2 Telesales
Currently, once telesales checkout is completed by the end customer, the confirmation redirect url is reached to initiate the auth request from the merchant's Magento server.
To support CA, Telesales need to include country code and currency information in the authorization request to POST /transactions endpoint. However, since the confirm redirect parameter only includes checkout token (and no other information is passed to look up the currency or country code attributes of an order), this requirement poses a challenge.
The proposed solution is to move the auth flow away from end customer reaching the confirm endpoint synchronously, and instead allowing admin user (in-store) to initiate the auth flow async once customer completes telesales checkout flow. As a result, one additional UI (refresh button) will be introduced to initiate the auth flow.