Struct PayLnurlRequest 

pub struct PayLnurlRequest {
    pub lnurl: Option<String>,
    pub pay_request: Option<LnurlPayRequest>,
    pub amount: Amount,
    pub message: Option<String>,
    pub personal_note: Option<String>,
    pub partner_pk: Option<UserPk>,
    pub partner_prop_fee: Option<Ppm>,
    pub partner_base_fee: Option<Amount>,
}

A request to pay to an LNURL-pay endpoint.

Use analyze to get the associated LnurlPayRequest, which contains information on amount constraints, message limits, and more.

Fields

lnurl: Option<String>

The LNURL or Lightning Address to pay to.

Exactly one of lnurl or pay_request should be provided.

pay_request: Option<LnurlPayRequest>

The LNURL pay request to use.

Exactly one of lnurl or pay_request should be provided.

amount: Amount

The amount to pay. This value must satisfy the minimum and maximum limits set by the LNURL endpoint.

message: Option<String>

An optional message to include in the payment, visible to the recipient.

Will only be sent if the LNURL endpoint supports it, and will be truncated to the LNURL endpoint’s specified length limits if needed.

personal_note: Option<String>

An optional personal note for this payment. The receiver will not see this note.

If provided, it must be non-empty and no longer than 200 chars / 512 UTF-8 bytes.

partner_pk: Option<UserPk>

The partner’s user_pk, if the partner is setting the fee for this payment instead of using Lexe’s default fees.

This must be set in order for partner_prop_fee and partner_base_fee to take effect.

The total fee (partner_base_fee + partner_prop_fee * amount) must be at least 0.5% (5000 ppm) and less than 50% (500,000 ppm) of the payment amount.

partner_prop_fee: Option<Ppm>

The partner-chosen proportional fee to charge on this payment, paid on top of the routing fees.

partner_base_fee: Option<Amount>

The partner-chosen base fee to charge on this payment, paid on top of the routing fees.