Problem or use case
An incoming payment request opens in the send sheet with the amount, the coin illustration, Show Details and Swipe to Pay. The sheet shows who sent the request and what it is for only after the payer taps Show Details. Feedback on the Paykit demo asked for the request itself to show who it is from and what it is for.
Proposed solution
On the Payment Request sheet for an incoming one-off request, match the updated design:
- From: user icon and the requester's contact name under the amount. The avatar stays only in the header.
- For: note icon and the request note next to From. The column is left out when the request has no note.
- Details: the requester is labeled Contact, and the request note shows as Invoice Note, so it stays visible once the details are open.
LNURL pay, subscription payments and regular sends keep their current confirmation screens.
Alternatives considered
Keeping sender and purpose behind Show Details, which is how the demo presented the request.
Additional context
Problem or use case
An incoming payment request opens in the send sheet with the amount, the coin illustration, Show Details and Swipe to Pay. The sheet shows who sent the request and what it is for only after the payer taps Show Details. Feedback on the Paykit demo asked for the request itself to show who it is from and what it is for.
Proposed solution
On the Payment Request sheet for an incoming one-off request, match the updated design:
LNURL pay, subscription payments and regular sends keep their current confirmation screens.
Alternatives considered
Keeping sender and purpose behind Show Details, which is how the demo presented the request.
Additional context
Bitkit - Refactor v63page, with the Payment Request and Confirm Details frames.