MPP

Create a dedicated 'Rate Limits' or 'API Limits' documentation page that specifies default charge request rate limits (e.g., requests per second per API key, per account, per IP) and explains how high-frequency trading users can request limit increases (contact form, support email, or self-serve upgrade path).

Add documentation explaining Lightning Network routing fee handling, specifically whether fees are deducted from the payment amount or added as an extra charge to the payer, and how this affects the 'charge' and 'session' intents.

Add a pricing or fees page that explains MPP's business model, including any platform fees, revenue share percentages, and how fees compare across payment methods.

Add documentation covering error handling and payment state management for edge cases like upstream timeouts, network failures between payment authorization and response, and whether payments are captured immediately or held pending successful upstream response.

Create a dedicated security/compliance page that lists specific certifications held (SOC 2, PCI DSS, ISO 27001) with status (e.g., 'SOC 2 Type II certified'), audit dates, and instructions for requesting reports under NDA.

Add a dedicated schema reference page documenting the `x-payment-info` extension structure with required fields, field types, and a downloadable JSON Schema or link to the OpenAPI specification fragment for validation.

Add a dedicated 'Custom Payment Method Specification' page with complete interface definitions, schema requirements, and type signatures. Expand the existing Custom section with a formal specification rather than just high-level descriptions and SDK references.

Add explicit documentation about CGO requirements for the Go SDK, particularly whether go-ethereum's crypto operations require CGO or if pure-Go alternatives are used.

Add explicit documentation on the signature format: specify whether the proof uses EIP-712 typed data, SIWE (EIP-4361), or raw message signing. Include the exact message structure or domain separator that clients must sign.

Add explicit card settlement timing (e.g., "T+2 business days per Stripe's standard terms") to the Accept card payments guide, or link to Stripe's settlement documentation.

Add a dedicated pricing page that explicitly states: (1) whether MPP charges any protocol fees, (2) exact fee structures for each payment rail (Stripe, Tempo, Lightning, etc.), (3) volume-based pricing tiers if any, and (4) comparison with Stripe's standard rates for buyer evaluation.

Add explicit documentation on whether partial refunds are supported for charge intents, and how to implement them for streamed payment disputes when using charge-based payment methods like cards or Stripe.

Add explicit documentation clarifying whether the 10-split limit is enforced at the protocol level (e.g., in the IETF spec or on-chain) or is merely a current SDK implementation constraint that could vary by client library.

Add explicit documentation on whether per-chunk voucher frequency is configurable by merchants, or if it's always fixed to one voucher per content chunk. If configurable, document the configuration mechanism and available options (e.g., time-based batches, chunk-count batches, or cost-threshold triggers).