pavlenex / bitcoin-payments

Designing a set of guidelines for those interested in building Bitcoin merchant applications 🏗️

Bitcoin Payments

Designing a set of best practices for designers and developers building effective Bitcoin merchants payment applications. These guidelines cover basic interface elements, how to use them and integrate effectively into a seamless interface.

These guidelines are based on industry standards, best-practices and user-research. However, they don't represent a rulebook. Use it as a foundation when developing/designing your applications and feel free to contribute to its expansion and improvement.

The end-goal of this project is to become a part of the payment section of the @BitcoinDesign guide. For more general overview on Bitcoin Payments, check Johns Beharry's work.

bitcoin-payments's Issues

Understand the difference between UX of paying an invoice on mobile vs desktop

Ideally, an invoice should just be a QR code. However due to different UX on mobile vs desktop wallets, when merchant software displays an invoice, there's always a "Copy" section which provides a way to copy/paste data bypassing the QR code scanning.

• Explain the difference
• Research different solution
• Propose an optimal solution

Invoice statuses

Different software use different statuses for the invoice. The goal of this issue is to research different statuses and come up with a concrete naming suggestion that's unified and contextual.

• Investigate API's of payment processors in particular and take note on every invoice status they have
• Categorize most commonly used invoice statuses and see if we can simplify some of them
• Present a clear list of invoice statuses
• Explain a difference of invoice status on and off-chain
• Illustrate statuses and common actions
• Explain how invoice statuses should be distinguished with labels
• Buyer's flow for different statuses
• Merchant's flow for different statuses (foundation for the troubleshooting section)