Problem

Payment Detection use case page contains AI warning, speculative content, unverified chain counts (claims 10+ but actual is 9), placeholder links, and marketing language that needs cleanup.

Key issues:

• AI-generated warning box at top
• Claims "10+ EVM chains" but should be 9 (Fantom deprecated)
• Marketing copy vs factual benefits-focused language
• Multiple placeholder # links
• References to 553+ tokens needs verification
• No tooltips for technical terms (blockchain, confirmations, webhooks, etc.)

Proposed Solution

Apply Invoicing page cleanup template to Payment Detection page:

• Remove AI warning box
• Verify and update chain count to 9
• Replace marketing language with factual, benefits-focused copy
• Fix or remove placeholder links (add notes for future pages)
• Verify token count claim against codebase
• Add tooltips for technical terms (blockchain, smart contract, webhook, confirmation, etc.)
• Consider adding Check callout after key sections
• Review code examples for accuracy
• Verify detection speeds against actual performance
• Update "Detection-Only vs Full Workflows" section for clarity

Considerations

• Marketing page at https://request.network/payment-detection claims "25+ blockchains" but docs should reflect API reality (9 EVM chains)
• Payment Detection is core functionality - accuracy is critical
• Page is already comprehensive with good structure - focus on accuracy and removing slop
• Code examples should be tested and realistic
• Detection speeds should be verified (currently claims ~15s Ethereum, ~2s Polygon)

References

• Parent issue: Docs - Remove AI slop from Use Case pages #18
• Template: Issue Docs - Clean up Invoicing use case page #28 (Invoicing cleanup)
• Marketing page: https://request.network/payment-detection
• Current page: /use-cases/payment-detection.mdx