You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be very useful to somehow track payment requests.
Keeping in with the simplistic design philosophy, a full request management system (as implemented in Electrum for Android) may be too complex for BRD. But I'd like to propose a simplified one:
Receiver creates an "request": presses Receive and specifies the requested amount (so nothing new this far).
We presume the receiver keeps the Receive window open until the payment is made, and doesn't change the amount. Any changes would mean going back to point 1.
The sender scans the QR code and sends the transaction.
When the receiver receives a transaction that matches the receiving address and the amount in the open Receive window, a confirmation message message (green, tick symbol, etc.) appears for 3-5 seconds, and then the whole Receive window is closed and the user is back to the respective wallet.
What do you think?
The text was updated successfully, but these errors were encountered:
Thank you immensely for your answers and consideration! I forgot to explain what made me request it -- let me give a bit of a context.
Imagine a receiver requests a payment. After entering the requested amount, she waits for the sender to scan the QR code and finish the send flow. The receiver finds herself in an uncomfortable position:
she wants to know whether the payment has been successfully sent to the network, so she wants to press Back to see the transaction list;
simultaneously, she doesn't know whether the sender has finished the send flow successfully or needs to restart it (if the latter, she doesn't want to risk having to prepare the request again), so she also wants to stay in the Receive window.
It would be very useful to somehow track payment requests.
Keeping in with the simplistic design philosophy, a full request management system (as implemented in Electrum for Android) may be too complex for BRD. But I'd like to propose a simplified one:
What do you think?
The text was updated successfully, but these errors were encountered: