Expand description
Payment data types. Lexe SDK payment types.
Structs§
- Client
Payment Id - A unique, client-generated id for payment types (onchain send, ln spontaneous send) that need an extra id for idempotency.
- LnClaim
Id - Newtype for LDK’s
lightning::ln::channelmanager::PaymentIdbut used specifically for inbound lightning payment idempotency. - Payment
- Information about a payment.
- Payment
Created Index - A unique, ordered payment identifier:
(created_at, payment_id). - Payment
Hash - The payment hash of a Lightning payment. Serialized as a 64-character hex string.
- Payment
Secret - The payment secret of a Lightning invoice, used to authenticate the payer. Serialized as a 64-character hex string.
- Payment
Updated Index - A unique, ordered payment identifier:
(updated_at, payment_id).
Enums§
- Order
- Sort order for listing results.
- Payment
Direction - The direction of a payment:
"inbound","outbound", or"info". - Payment
Filter - Filter for listing payments.
- Payment
Id - A globally unique identifier for any payment (Lightning or on-chain).
Serialized as
"<prefix>_<hex>", e.g."ln_3ddc..."or"os_0a19...". - Payment
Kind - A fine-grained category for a payment. Useful for filtering payment history and analytics (e.g. regular Lightning payments vs. waived channel fees).
- Payment
Rail - The protocol used to fulfill a payment:
"onchain","invoice","offer","spontaneous", etc. - Payment
Status - The status of a payment:
"pending","completed", or"failed".