L402 Hash Verifier

Catch payment_hash mismatches before paid retry — 8 sats

About

Compare hash values from challenge headers/payloads, BOLT11 invoice tag p, and the hash used on retry. Use this before burning more sats on failing paid retries.

Try It

8 sats via L402.

API Usage

curl -X POST https://maximumsats.com/api/l402-hash-verify \
  -H "Content-Type: application/json" \
  -d '{"endpoint_payment_hash":"<target_hash>","invoice":"lnbc...","retry_payment_hash":"<hash_you_sent>"}'

Sample Response

{
  "ok": true,
  "verification": {
    "normalized_hashes": {
      "challenge_payment_hash": "<target_hash>",
      "invoice_payment_hash": "<invoice_hash>",
      "retry_payment_hash": "<hash_you_sent>"
    },
    "checks": {
      "challenge_vs_invoice": true,
      "retry_vs_challenge": true,
      "retry_vs_invoice": true
    }
  }
}
Also available via MCP as l402_hash_verify at maximumsats.com/mcp