-
Notifications
You must be signed in to change notification settings - Fork 6
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
[BUG] Misleading successful payment msg even when wallet payment fails #592
Comments
@tselit Can you share the wallet address of:
|
Sure @sidvishnoi . The website was the WM playground, and the connected wallet was: |
So me and Radu couldn't both reproduce with non-WM payment pointers. |
Related: #445 |
Steps to reproduce
Tester feedback
Used
rafiki.money
to setup 2 different wallets, to easily track my WM sending wallet (starting balance of $50) and receiving wallet (starting balance of $0).Both wallets are in USD, they're configured to have WM-enabled payment pointers.
Observation: The extension shows a "Payment successful" message
Results: Waited 5 minutes...30 minutes...about 20 hrs but there were no successful, or even rejected transactions, and the balances remained unchanged, for each wallet.
Expected result
None of the payments from the WM extension actually succeeded, and so the extension should not show a message indicating successful payment.
Actual result
When making a one-time payment, the extension showed a "Payment successful" message even though the transaction didn't actually succeed.
Screenshots or videos
No response
Additional context
I was concerned that maybe the WM playground or extension may be doing something unexpected.
When I repeat the scenario using a Fynbos wallet, the payments go through.
Erica didn't use the WM playground, instead she added the receiving payment pointers onto a website, but unfortunately she made similar observations.
Operating system
Windows
Operating system version
10
Browsers
Chrome
Browser version
Version 128.0.6613.115 (Official Build) (64-bit)
Extension version
private beta release
The text was updated successfully, but these errors were encountered: