User experience

The user should be able to scan or enter an identifier, review a safe destination, and pay in the wallet they already use.

Recommended payment flow

1. Scan a QR code or enter an identifier.
2. Resolve the typed value through the wallet’s configured resolver.
3. Display the profile, identifier, status, and payment options.
4. Warn when the mapping is pending, recently changed, or unavailable.
5. Let the user select an option and confirm the transaction.
6. Build, sign, broadcast, and show the wallet’s transaction result.

Confirmation screen

Pay 10.00 USDC
Network: Base mainnet
Recipient: 0x…
Token contract: 0x…

[Cancel] [Confirm payment]

Populate the confirmation screen from the selected resolver option, not from user-provided or cached address data. If the option has amount limits, a fixed amount, memo, reference, or expiration, enforce and display those constraints.

Safety presentation

• Require both status and payment_ready.
• Show chain, asset, token contract, and destination before confirmation.
• Do not present suspended, removed, or pending mappings as payable.
• Keep the resolver’s trust timestamps visible in detail views.