Closes #149(Add mobile failed payment recovery guidance)#286
Merged
El-swaggerito merged 2 commits intoJul 23, 2026
Merged
Conversation
Contributor
|
This PR cannot be merged automatically because it has merge conflicts. Please update the branch with the latest base branch and resolve the conflicts. After the conflicts are resolved and checks pass, the automation can review it again. |
4 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #149 (Add mobile failed payment recovery guidance)
closes #149
The failed payment recovery guidance transforms a confusing raw error experience into a supportive user journey. Instead of cryptic Stellar codes, users now see clear titles and plain language explanations tailored to each failure category. The inline banner provides scannable messaging with specific next steps and context aware action buttons like try again or go back. Network issues, insufficient balance, bad sequences, and more each receive custom guidance. This thoughtful error handling builds user trust, reduces support burden, and makes the payment flow feel polished and professional.