Expand description
Payment URI resolution.
For core types and parsing, see lexe_payment_uri_core.
Modules§
- bip353
- BIP353 resolution. BIP 353 (DNS Payment Instructions) resolution.
- helpers
- Helper functions and utilities; some of these are public.
- lnurl
- LNURL-pay and Lightning Address resolution. Resolver for LNURL-Pay and Lightning Address (LUD-06, LUD-16).
Structs§
- Bip321
Uri - A BIP321 / BIP21 URI
- Email
Like Address - Email-like human-readable payment address: BIP353 or Lightning Address. String fields are guaranteed to be lowercase (normalized during parsing).
- Lightning
Uri - A “lightning:” URI, containing a BOLT11 invoice or BOLT12 offer.
- Lnurl
- A parsed LNURL.
- Offer
With Amount - An offer payment method with optional amount from a BIP321 URI.
- Onchain
- An onchain payment method, usually parsed from a standalone BTC address or BIP321 URI.
Enums§
- Error
- Payment
Method - A single “payment method” – each kind here should correspond with a single linear payment flow for a user, where there are no other alternate methods.
- Payment
Uri - A decoded “Payment URI”, usually from a scanned QR code, manually pasted
code, or handling a URI open (like tapping a
bitcoin:bc1qfjeyfl...URI in your mobile browser or in another app).
Functions§
- resolve_
best - Resolve a
PaymentUriinto a single, “best”PaymentMethod.