docs(standard-payments): remove AI warning, restructure content with step-by-step flow, and update API references

[aimensahnoun]

TL;DR

Rewrote the standard payments documentation to remove AI-generated content warning and provide clearer, more structured guidance on same-currency crypto payments.

What changed?

• Removed the AI-generated content warning banner
• Clarified that standard payments are same-currency payments where invoiceCurrency and paymentCurrency match
• Restructured native currency and ERC20 token sections to focus on characteristics rather than benefits
• Added a new "How It Works" section with step-by-step implementation guidance
• Updated the "Supported Networks & Tokens" section to reference the supported currencies catalog
• Revised "Used In" section to focus on invoicing and checkout use cases
• Updated API reference section to point to the OpenAPI documentation

How to test?

• Review the documentation page to ensure the content flows logically
• Verify that all referenced links work correctly
• Check that the step-by-step implementation guide is clear and actionable
• Confirm the supported chains and currencies references are accurate

Why make this change?

The previous version contained an AI-generated content warning and lacked clear implementation guidance. This revision provides developers with more precise definitions, clearer implementation steps, and removes uncertainty about content accuracy while maintaining technical accuracy.

[aimensahnoun]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• docs(authentication): simplify auth guide with API key vs Client ID methods and remove AI-generated content #70
• docs(fee-breakdowns): rewrite to focus on API response locations and reconciliation usage #69
• docs(protocol-fees): add protocol fees documentation and navigation #68
• docs(platform-fees): simplify configuration guide and remove AI-generated content warning #67
• docs(query-payments): rewrite with practical implementation focus and remove AI warning #66
• docs(query-requests): simplify and refactor query requests documentation for practical implementation #65
• docs(payment-detection): simplify content and remove AI warning #64
• docs(partial-payments): rewrite with step-by-step implementation guide and clarify API usage #63
• docs(standard-payments): remove AI warning, restructure content with step-by-step flow, and update API references #62 👈 (View in Graphite)
• docs(conversion-payments): rewrite with step-by-step implementation guide and remove AI-generated warning #61
• docs(payment-types): simplify overview and add payment type selection guidance #60
• docs(crypto-to-fiat): expand comprehensive guide with sandbox access, compliance flows, and implementation details #59
• docs(recurring-payments): rewrite with comprehensive workflow, security details, and practical implementation guide #58
• docs(batch-payments): add comprehensive implementation guide with examples, workflow diagrams, and demo videos #57
• docs(crosschain-payments): replace AI-generated content with comprehensive implementation guide #56
• docs(create-requests): rewrite with workflows, examples, and remove AI warning #55
• feat: add complete integration tutorial with Node.js backend and React frontend #54
• docs(getting-started): remove AI warning and refactor to focus on practical payment integration #53
• docs(api-portal): remove AI warning, add local screenshot, and update .gitignore #52
• docs: remove release notes section and streamline use cases to core features #51
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Greptile Summary

Successfully refactors standard payments documentation by removing AI-generated content warning and providing clearer, endpoint-driven guidance.

Major improvements:

• Replaced vague "crypto-to-crypto" description with precise "same-currency payments where invoiceCurrency and paymentCurrency match" definition
• Restructured Native and ERC20 sections from "Benefits" to "Characteristics" with accurate technical details (approval flows, transaction counts)
• Added comprehensive "How It Works" section with step-by-step implementation using actual API endpoints (POST /v2/request, POST /v2/payouts, GET /v2/request/{requestId}/pay)
• Updated network/token section to reference authoritative supported currencies catalog instead of making unsupported claims
• Removed hidden use-case references (payouts, payroll) and kept only active links (invoicing, checkout)
• Standardized API reference to canonical OpenAPI documentation URL

The changes align with the ongoing effort to migrate from AI-generated placeholders to verified content, following the same pattern as recent conversion-payments, batch-payments, and recurring-payments updates.

Confidence Score: 5/5

• This PR is safe to merge with no risk
• Documentation-only change that improves content clarity and accuracy. All internal links verified, API references updated to canonical URLs, and content follows established technical writing guidelines. Part of systematic effort to replace AI-generated content with verified documentation.
• No files require special attention

Important Files Changed

Filename	Overview
api-features/standard-payments.mdx	Removed AI warning, restructured with clear same-currency payment definition, added step-by-step flow, updated API references to OpenAPI docs

_{Last reviewed commit: ad72ad5}

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}