Understand validation

Step 01

What the report checks

• Format: Can the BOLT11 encoding be parsed?
• Signature: Does the invoice signature verify?
• Requirements: Does the invoice meet the parser’s required-field and semantic checks?
• Expiry: Has the invoice expired at the time of inspection?
• Network: Which network is encoded, and does it match your optional expectation?
• Amount: Is an amount specified, or does the payer choose it?

Step 02

Read the status labels

• Passed: The check succeeded.
• Warning: Review a condition such as expiry or a network mismatch.
• Failed: A validation check failed.
• Info: Context, such as an unspecified amount or detected network.
• Not checked: A preceding failure prevented this check.

Step 03

Understand the limits

Expired invoices and network mismatches remain inspectable. Expiry is a snapshot at the report’s checked time and depends on the clock of the machine doing the validation.

A valid signature does not establish a recipient’s real-world identity. Decoding cannot establish whether an invoice has already been paid, whether a route is available, or whether your wallet supports every invoice feature. The report does not make an overall “safe to pay” claim.