docs(content): refresh Tron coverage, batch-payment EVM scope, webhook 12-event list

[rodrigopavezi]

Bring existing API and resource pages in line with the current product:

• Tron is co-equal with EVM for single payments/payouts; called out explicitly
  on payee-destinations, payouts, secure-payments, wallet-auth, supported
  chains, token-list, and lifecycle pages.
• Batch (incoming and outgoing) is EVM-only; admonition added to
  batch-payments, payouts, secure-payments, and the supported-chains feature
  matrix, with the exact API error string for searchability.
• Webhook event list synced with the auth API's OutgoingWebhookEvent enum
  (12 events) — added .client_id and .checkout variants alongside the core
  4 payment events.
• Secure Payments reference: documented POST /v2/secure-payments/payouts,
  expanded crosschain chain enum (BASE/OPTIMISM/ARBITRUM/ETHEREUM/POLYGON/BNB),
  noted Tron-specific calldata path.
• Client ID schema: added operatorWalletAddress, defaultPreApprovalExpiry,
  defaultAuthorizationExpiry; called out Dashboard as the recommended path.
• Release notes rewritten to reflect actual recent shipments (Tron support,
  secure payouts, gas transparency, calldata endpoint); dropped v1 fiction.
• Stripped remaining EasyInvoice references from batch-payments and
  crypto-to-fiat-payments.

[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
• 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 👈 (View in Graphite)
• 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 refreshes 15 documentation pages to reflect the current state of the Request Network v2 API: Tron is elevated to a first-class network alongside EVM for single payments and payouts, batch operations are clearly marked EVM-only with the exact API error string, the webhook event list is expanded to 12 events (adding .client_id and .checkout variants), and the AI-generated release notes are replaced with accurate 2026 Q1/Q2 shipment descriptions.

• Tron parity: Payee destinations, payouts, secure payments, wallet auth, supported chains, token list, and lifecycle pages now all call out EVM and Tron symmetry for single-recipient flows, with EVM-only warnings for batch operations.
• Webhook expansion: api-reference/webhooks.mdx and api-features/webhooks-events.mdx add four new scoped event types (payment.confirmed/partial.client_id and .checkout); the table count of 12 is accurate.
• Secure payments reference: Documents the new POST /v2/secure-payments/payouts endpoint fully with request fields, cURL examples, and response schema; expands the crosschain chain enum to six EVM chains (+ POLYGON, BNB).
• Release notes rewrite: Removes placeholder AI-generated content; adds real 2026 Q1/Q2 entries for Tron support, secure payouts, accounting fields, and a calldata endpoint.

Confidence Score: 4/5

Safe to merge after resolving two documentation inconsistencies that would cause developer integration failures.

Two concrete mismatches exist in the changed files. First, expanding the /pay crosschain chain enum to include POLYGON and BNB while leaving the /intent endpoint's chain list at four values means a developer who follows the updated /pay docs for a Polygon crosschain payment would then hit undocumented (and potentially rejected) input on /intent. Second, the release notes describe POST /v2/secure-payments/{token}/calldata as a new endpoint that replaces the payment-intent flow, but no such endpoint appears in the API reference, which still shows /intent as active. Both issues are in changed files and point developers toward the wrong API surface.

api-reference/secure-payments.mdx (intent chain enum) and release-notes/request-api.mdx (calldata endpoint name) need attention before merge.

Important Files Changed

Filename	Overview
api-reference/secure-payments.mdx	Documents new POST /v2/secure-payments/payouts endpoint and expands crosschain chain enum (+ POLYGON, BNB), but the /intent endpoint's chain enum was not updated to match, leaving it inconsistent with /pay.
release-notes/request-api.mdx	Replaces AI-generated placeholder content with real 2026 shipments; references POST /v2/secure-payments/{token}/calldata as a new endpoint that replaces the /intent flow, but this endpoint name does not appear in the API reference.
api-reference/webhooks.mdx	Adds four new event type sections (payment.confirmed/partial .client_id and .checkout variants) with accurate descriptions; payload examples section lacks samples for the new event types.
api-features/webhooks-events.mdx	Replaces card group with a clean 12-event table; event count is accurate (4 core + 2 client_id + 2 checkout + 1 processing + 1 request + 2 compliance = 12).
resources/supported-chains-and-currencies.mdx	Comprehensive restructure with network table, feature matrix, and Tron specifics card; the feature matrix row marking Tron for cross-chain swap-to-pay (Li.Fi) contradicts the EVM-source-only note in the API reference (flagged in a prior review round).
api-features/payouts.mdx	Adds Tron payout tab with correct USDT-tron currency ID and T-prefix address; EVM-only batch payout Warning added with exact error string.
api-features/client-id-management.mdx	Adds operatorWalletAddress, defaultPreApprovalExpiry, defaultAuthorizationExpiry fields and a Dashboard vs Auth API comparison table; changes look accurate and complete.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    subgraph SinglePayment["Single Payment / Payout (EVM + Tron)"]
        SP1["POST /v2/payouts (single)"] --> SP2["Returns calldata + requestId"]
        SP3["POST /v2/secure-payments (single)"] --> SP4["Returns securePaymentUrl + token"]
        SP5["POST /v2/secure-payments/payouts (new)"] --> SP4
    end
    subgraph BatchPayment["Batch Payment / Payout (EVM only)"]
        BP1["POST /v2/payouts/batch"] --> BP2["Returns batch calldata"]
        BP3["POST /v2/secure-payments (requests[] > 1)"] --> BP4["Returns batch URL"]
    end
    subgraph CrossChain["Crosschain Flow (EVM source only)"]
        CC1["GET /v2/secure-payments/:token/pay\n?chain=BASE|OPTIMISM|ARBITRUM|ETHEREUM|POLYGON|BNB"] --> CC2["Returns LiFi calldata"]
        CC2 --> CC3["POST /v2/secure-payments/:token/intent\n?chain=BASE|OPTIMISM|ARBITRUM|ETHEREUM only\n(POLYGON/BNB missing from enum)"]
    end
    subgraph Webhooks["Webhooks (12 events)"]
        W1["payment.confirmed/partial/failed/refunded (core - 4)"]
        W2["payment.confirmed/partial.client_id (new - 2)"]
        W3["payment.confirmed/partial.checkout (new - 2)"]
        W4["payment.processing / compliance.updated / payment_detail.updated / request.recurring (other - 4)"]
    end

Loading

Comments Outside Diff (1)

1. api-reference/secure-payments.mdx, line 457-459 (link)

   /intent chain enum not updated alongside /pay

   The GET /v2/secure-payments/:token/pay endpoint was expanded in this PR to accept POLYGON and BNB as crosschain source chains, but the POST /v2/secure-payments/:token/intent endpoint's chain field still lists only four values: BASE, OPTIMISM, ARBITRUM, ETHEREUM. Because /intent is called after /pay to record the on-chain LiFi broadcast, a developer who uses POLYGON or BNB as their source chain would follow the now-documented /pay path, then call /intent with "chain": "POLYGON" — at which point the documented enum (and likely API validation) would reject it with a 400. Either the /intent chain enum should be expanded to match /pay (BASE, OPTIMISM, ARBITRUM, ETHEREUM, POLYGON, BNB), or a note should clarify that /intent only covers a subset.

_{Reviews (2): Last reviewed commit: "docs(content): refresh Tron coverage, ba..." | 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:08 PM UTC: Graphite rebased this pull request as part of a merge.
• May 12, 5:08 PM UTC: @rodrigopavezi merged this pull request with Graphite.

[greptile-apps]

POST /calldata referenced in release notes but absent from the API reference

The "Calldata endpoint" entry describes POST /v2/secure-payments/{token}/calldata and states it "Replaces previous payment-intent flow for the calldata path." However, api-reference/secure-payments.mdx (also changed in this PR) lists GET /v2/secure-payments/:token/pay as the calldata endpoint and still shows POST /v2/secure-payments/:token/intent as an active, documented endpoint — neither of which matches the name given here. A developer reading the release notes who tries to call POST /v2/secure-payments/{token}/calldata will find no documentation for it. Please reconcile the endpoint name in the release notes with what is actually documented in the reference (or add POST …/calldata to the reference if it is a distinct endpoint).