docs(feedback): apply Tristan's revisions from RequestNetwork/request-api#806

[rodrigopavezi]

7 amendments across 3 pages:

1. Welcome page subtitle rewritten:
   "Request Network protocol allows you to be paid and pay at scale
   without intermediaries across EVM and Tron. Our protocol offers the
   instant payment reconciliation, click-to-pay payment links, and
   cross-chain routing that Web3 payments need."

2. Welcome page section renamed "Three on-ramps" -> "Three Products"
   with new subtitle pointing at Dashboard, Secure Payment Page, and
   API. Renamed the Secure Payment card to "Secure Payment Page" for
   consistency.

3. Multi-Chain Checkout: "you fix the destination" -> "you decide of
   the destination" in the Why multi-chain matters section.

4. Batch Payouts What you'll build: "gas-amortized" -> "gas-sponsored".

5. Reordered the two batch modes - Hosted Batch Link is now Mode 1
   (Recommended & Safer Approach), Direct Execution is Mode 2
   (Advanced & Self-Secure). Added Tristan's rationale for each.

6. Cross-chain capability differences spelled out per mode:

   • Hosted Batch Link supports cross-chain execution from a single
     wallet connection with automatic routing across EVM chains.
   • Direct Execution is same-chain only; cross-chain requires one
     transaction per chain on each network's deployed contracts.

7. Added a wallet-infrastructure compatibility note: Secure Payment
   Page and Dashboard not compatible with Safe multisigs today;
   recommend Utila, DFNS, or Fireblocks for corporate treasury;
   WalletConnect-based infrastructure is fully compatible.

[rodrigopavezi]

• docs(review): apply Tristan's two must-fix items from the final review #97
• docs(review): address Greptile review feedback across the stack #96
• docs(feedback): apply Tristan's revisions from RequestNetwork/request-api#806 #95 👈 (View in Graphite)
• docs(kyt): document KYT-screened payments as a use case + payee-destination field #94
• docs(secure-payments): document redirectUrl + redirectLabel #93
• docs(verify): fix broken cross-refs surfaced by mintlify broken-links #92
• docs(scripts): add Playwright screenshot capture scaffolding #91
• docs(content): add use-case pages, Dashboard + Secure Payment tools pages #90
• docs(content): refresh Tron coverage, batch-payment EVM scope, webhook 12-event list #89
• docs(nav): restructure navigation, remove legacy pages, retire Portal #88
• docs: fix broken links and clarify edge cases #87
• docs: add missing feature documentation for recent API changes #86
• docs: fix implementation discrepancies across API docs #85
• docs: remove beta banner and legacy SDK tab #78
• Remove AI-generated content warnings and update internal links #77
• docs(lifecycle): replace external image with local asset and remove AI-generated warning #76
• docs: remove AI-generated content warnings and simplify Request Scan page #75
• docs(resources): remove community page from navigation #74
• docs(supported-chains): add Tron network support and enhance currency documentation #73
• docs(supported-chains): streamline supported chains and currencies documentation #72
• docs(api-reference): add v2 endpoints overview and switch docs OpenAPI to v2-only spec Improve API Reference navigation by introducing a dedicated Endpoints Overview page in docs and wiring Mintlify OpenAPI rendering to a local v2-only spec. - add `api-re #71
• 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
• 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

This PR applies editorial revisions across three documentation pages — the Welcome page, Multi-chain Checkout, and Batch Payouts — reflecting feedback from RequestNetwork/request-api#806. The most structural change is in batch-payouts.mdx, where the two payout modes are reordered so Hosted Batch Link becomes the recommended Mode 1 and Direct Execution is demoted to the advanced Mode 2, with new cross-chain capability descriptions and a wallet-infrastructure compatibility note added.

• Welcome page: Subtitle rewritten, section renamed from "Three on-ramps" to "Three Products", and the Secure Payment card renamed to "Secure Payment Page".
• Multi-chain Checkout: "you fix the destination" → "you decide of the destination" (grammar issue being corrected in docs(review): address Greptile review feedback across the stack #96).
• Batch Payouts: Modes reordered and annotated with new cross-chain and safety rationale; gas-amortized changed to gas-sponsored; wallet-infrastructure compatibility note added.

Confidence Score: 3/5

The batch-payouts page now contains directly contradictory statements about cross-chain support — Mode 1 says it works, the Limits section says it doesn't — which needs resolution before merging.

Mode 1 explicitly introduces cross-chain execution capability for Hosted Batch Link, but the Limits section was not updated and still asserts "Same network only — all requests[] must target the same chain." A developer reading the Limits section will conclude cross-chain batching is impossible, directly contradicting the Mode 1 description on the same page.

use-cases/batch-payouts.mdx — specifically the Limits section, which needs to be qualified to clarify that the same-chain constraint applies only to Direct Execution (Mode 2), not to the Hosted Batch Link (Mode 1).

Important Files Changed

Filename	Overview
use-cases/batch-payouts.mdx	Modes reordered (Hosted Batch Link is now Mode 1, Direct Execution Mode 2) and cross-chain/wallet-compatibility notes added; introduces a contradiction between Mode 1's cross-chain capability and the unchanged Limits section that still says "Same network only" for all requests[].
use-cases/multi-chain-checkout.mdx	Single phrase change: "you fix the destination" → "you decide of the destination"; grammatical issue ("decide of") already flagged and being corrected in #96.
use-cases/welcome.mdx	Welcome page subtitle and section title/subtitle updated; the "SDK" framing for no-code products is a previously flagged issue being addressed in #96.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Batch Payout Request] --> B{Choose Mode}
    B --> C["Mode 1 — Hosted Batch Link\nPOST /v2/secure-payments\n✅ Recommended & Safer"]
    B --> D["Mode 2 — Direct Execution\nPOST /v2/payouts/batch\n⚠️ Advanced & Self-Secure"]
    C --> E["Returns pay.request.network URL\nPayer reviews & signs once"]
    E --> F["Cross-chain routing via Li.Fi\nSingle wallet connection\nMultiple EVM chains"]
    D --> G["Returns calldata\nBackend broadcasts tx"]
    G --> H["Same-chain only\nOne tx per chain required"]
    F --> I[Settlement + Webhooks]
    H --> I

Loading

Comments Outside Diff (1)

1. use-cases/batch-payouts.mdx, line 199-204 (link)

   Limits section contradicts Mode 1's cross-chain capability

   The ## Limits section states "Same network only — all requests[] must target the same chain. No mixing Base + Arbitrum in one batch." But Mode 1 introduced by this PR explicitly says the Hosted Batch Link "supports cross-chain execution from a single wallet connection" and that "The Secure Payment Page handles routing and cross-chain execution automatically." These two statements directly conflict. A reader of the Limits section will conclude cross-chain batching is impossible, which contradicts the Mode 1 description above it. The Limits section needs a qualifier specifying that the same-chain constraint applies only to Mode 2 (Direct Execution / POST /v2/payouts/batch).

_{Reviews (2): Last reviewed commit: "docs(feedback): apply Tristan's revision..." | Re-trigger Greptile}

[rodrigopavezi]

Merge activity

• May 12, 4:02 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• May 12, 5:20 PM UTC: Graphite rebased this pull request as part of a merge.
• May 12, 5:21 PM UTC: @rodrigopavezi merged this pull request with Graphite.