Sample L402 Launch Checker Report

This is an example of the detailed report you receive after running a full L402 Launch Checker scan.

Report Summary

Endpoint: https://api.example.com/v1/content

Method: POST

Status: warning

Confidence: 0.72

The endpoint responds with L402-style challenges but the invoice parsing detected inconsistencies in the payment hash field naming convention.

Checks

Check Status Detail
endpoint_reachable pass Endpoint responded with HTTP 402
www_authenticate_header pass WWW-Authenticate header present
invoice_format warning Non-standard payment hash field name
content_type pass Response content-type is application/json
challenge_timeout pass Challenge received within 500ms

Recommended Fixes

High Priority

Non-standard payment hash field name

Your endpoint returns payment_request where the L402 spec expects payment_hash. Update your server to use the standard field name, or use a compatibility layer that normalizes both field names.

Medium Priority

Missing grace period handling

Your endpoint does not appear to honor the invoice TTL grace period. Users may experience premature failures if their payment is delayed. Consider adding a 30-second grace period before rejecting expired invoices.

Low Priority

WWW-Authenticate header format

The L402 spec recommends a structured WWW-Authenticate header. Your current header format may not be parsed correctly by all L402 clients.

Next Steps

  1. Review the fixes above and prioritize based on your deployment timeline
  2. Re-run a full scan after making changes to verify fixes
  3. Contact support@maximumsats.com if you have questions about the report

Report generated by L402 Launch Checker v0.1.0

← Back to L402 Launch Checker