-
Notifications
You must be signed in to change notification settings - Fork 109
feat: [IOBP-1578] Payment webview flow #6899
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
Merged
Merged
Conversation
This file contains hidden or 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
Co-Authored-By: Alessandro <[email protected]>
Co-Authored-By: Alessandro <[email protected]>
Co-Authored-By: Alessandro <[email protected]>
Jira Pull Request LinkThis Pull Request refers to Jira issues: |
PR Title Validation for conventional commit type✅ All good! PR title follows the conventional commit type. |
github-merge-queue bot
pushed a commit
that referenced
this pull request
Apr 18, 2025
##⚠️ This PR depends on #6899 ## Short description This PR adds the header with the close action button to the new payment webview flow. ## List of changes proposed in this pull request - Added a custom `HeaderSecondLevel` to the payment webview screen (the `useHeaderSecondLevel` wasn't used because it doesn't allow having only one action); - Added a prompt to confirm if the user really wants to exit the flow when tapping the close button or repeatedly pressing the hardware back button on Android. ## How to test - Start a payment flow with the dev server started and check that the `webViewPaymentFlow` is enabled; - At the final payment step, ensure that a header with a close action button is visible. - Verify that tapping the close action button triggers an alert asking the user to confirm whether they want to exit the flow. - On Android devices, ensure that pressing the hardware back button triggers the same confirmation alert as the close action button. ## Preview https://github.com/user-attachments/assets/f67ee073-ae7d-455d-9188-fddf1f0791f2 --------- Co-authored-by: Emanuele Dall'Ara <[email protected]>
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.
Short description
This pull request introduces significant changes to the payment authorization workflow by adding support for a web view payment flow
List of changes proposed in this pull request
walletPaymentWebViewPayloadSelector
to retrieve the web viewpayload
from the statepaymentStartWebViewFlow
action to handle the start of the web view payment flowstartWebviewPaymentSession
to handle webview flowHow to test
webViewPaymentFlow
remote feature flag enabled