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]

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(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 docs pages: a rewritten welcome subtitle, a renamed "Three Products" section, reordered batch-payout modes (Hosted Batch Link promoted to Mode 1/recommended), per-mode cross-chain capability notes, and a new wallet-infrastructure compatibility callout for Safe multisig users.

• use-cases/multi-chain-checkout.mdx: "you fix the destination" is replaced with "you decide of the destination" — the new phrasing contains a grammatical error ("decide of" is not idiomatic English).
• use-cases/batch-payouts.mdx: Mode order and guidance updated correctly, but all three real-world code examples still use the Direct Execution path (now labeled "Advanced"), creating a mixed signal for developers reading the examples first; a minor word-repetition ("hosted…hosted") also slipped in.
• use-cases/welcome.mdx: Section rename and subtitle refresh look good; the new subtitle incorrectly implies the Dashboard and Secure Payment Page are accessed "through the Request Network SDK".

Confidence Score: 3/5

The structural changes are sound, but a grammatical error was introduced into the multi-chain page and the real-world examples contradict the newly recommended mode.

The "you decide of the destination" phrasing in multi-chain-checkout.mdx leaves a grammatically broken sentence in public-facing documentation. Additionally, all three real-world code examples in batch-payouts.mdx demonstrate the path now labeled "Advanced & Self-Secure", sending an implicit message opposite to the page's updated recommendation.

use-cases/multi-chain-checkout.mdx (grammar error) and use-cases/batch-payouts.mdx (example code contradicts newly-promoted recommended path)

Important Files Changed

Filename	Overview
use-cases/batch-payouts.mdx	Modes reordered (Hosted Batch Link is now Mode 1/recommended, Direct Execution is Mode 2/advanced); cross-chain capabilities documented per mode; wallet infrastructure compatibility note added; but "hosted…hosted" redundancy, and all real-world examples still demonstrate the non-recommended Direct Execution path.
use-cases/multi-chain-checkout.mdx	Single line change replacing "you fix" with "you decide of" — introduces a grammatical error ("decide of" is not standard English; should be "decide on").
use-cases/welcome.mdx	Welcome page subtitle rewritten, section renamed "Three Products", card renamed "Secure Payment Page"; the new subtitle inaccurately says users interact with "Request Network SDK" through all three products when Dashboard and Secure Payment Page are no-code tools unrelated to the SDK.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Need to pay multiple recipients?] --> B{Who controls the payer wallet?}
    B -->|Human / Finance team| C[Mode 1: Hosted Batch Link\nRecommended & Safer]
    B -->|Automated backend| D{Need cross-chain payouts?}
    D -->|Yes| C
    D -->|No, same-chain only| E[Mode 2: Direct Execution\nAdvanced & Self-Secure]
    C --> F[POST /v2/secure-payments]
    F --> G[Returns pay.request.network URL]
    G --> H[Payer reviews and signs once]
    E --> J[POST /v2/payouts/batch]
    J --> K[Returns calldata]
    K --> L[Backend broadcasts transactions]

Loading

Comments Outside Diff (1)

1. use-cases/batch-payouts.mdx, line 134-191 (link)

   Real-world examples all use the non-recommended mode

   All three "Real-world examples" (Marketplace seller payouts, Refund campaign, Contractor payroll) call POST /v2/payouts/batch — the Direct Execution path now labeled "Advanced & Self-Secure". This contradicts the recommendation added earlier in the page that Hosted Batch Link should be the default choice for most scenarios. A reader who skims to the examples section will get the opposite signal from what the restructured modes section intends to convey.

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