Description
When a user sends a zap (Lightning payment) from ZapDesk, the UI does not give clear confirmation that the payment actually succeeded. The user is left unsure whether the zap went through, whether to retry, or whether the recipient was credited.
Steps to Reproduce
- Open a ticket / view that exposes the "Send a zap" action.
- Trigger the zap flow and complete payment (sign with wallet / approve).
- Observe the UI after the payment settles.
Expected Behavior
After a successful zap:
- A clear success indicator is shown (toast, inline status, or both).
- The amount paid and recipient are visible in the confirmation.
- If applicable, the ticket / activity log records the successful payment so it's visible on the next page load too.
Actual Behavior
No (or insufficient) visual confirmation that the payment succeeded. The user cannot easily tell whether the zap landed.
Notes / Investigation Pointers
- Identify which component renders the "Send a zap" action and where the payment response is awaited.
- Check whether the success path is being swallowed (e.g. response not awaited, error path treated as success, or success toast accidentally suppressed).
- Make sure failure cases also surface a clear error so users can retry.
Environment
- Version: 0.9.0
- Browser: any
Description
When a user sends a zap (Lightning payment) from ZapDesk, the UI does not give clear confirmation that the payment actually succeeded. The user is left unsure whether the zap went through, whether to retry, or whether the recipient was credited.
Steps to Reproduce
Expected Behavior
After a successful zap:
Actual Behavior
No (or insufficient) visual confirmation that the payment succeeded. The user cannot easily tell whether the zap landed.
Notes / Investigation Pointers
Environment