docs(crosschain-payments): replace AI-generated content with comprehensive implementation guide

[aimen74]

TL;DR

Replaced AI-generated placeholder content with comprehensive documentation for crosschain payments functionality, including detailed implementation steps and supported networks.

What changed?

• Removed AI-generated content warning and placeholder information
• Added detailed overview explaining crosschain payments capability (paying requests with different currencies/networks)
• Documented supported chains (Ethereum, Arbitrum One, Base, OP Mainnet) and stablecoins (USDC, USDT, DAI)
• Included step-by-step implementation guide covering request creation, route fetching, payment calldata generation, signing, and execution
• Added TypeScript code example showing EIP-2612 permit handling and payment intent signing
• Added reference to custom fee configuration via Platform Fees

How to test?

1. Create a request using the POST /v2/request endpoint with supported stablecoins and networks
2. Fetch available payment routes using GET /v2/request/{requestId}/routes
3. Generate payment calldata with GET /v2/request/{requestId}/pay
4. Test the signing flow using the provided TypeScript example
5. Submit signed payment data via POST /v2/request/payment-intents/{paymentIntentId}
6. Verify webhook lifecycle updates are received

Why make this change?

The previous content was AI-generated placeholder material that lacked specific implementation details. This change provides developers with accurate, actionable documentation including supported networks, currencies, step-by-step integration instructions, and working code examples needed to implement crosschain payments functionality.

[aimen74]

• 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
• 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 👈 (View in Graphite)
• 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 replaces AI-generated placeholder content in api-features/crosschain-payments.mdx with a real implementation guide covering supported chains, currencies, and a step-by-step signing flow. The change is a net positive for developer experience but has one gap that would block implementors mid-flow.

• Supported networks and currencies (Ethereum, Arbitrum One, Base, OP Mainnet; USDC/USDT/DAI) are now clearly documented with a mainnet-only warning.
• Five sequential steps walk through request creation, route fetching, calldata retrieval, signing, and submission using a TypeScript example.
• Step 5's POST URL uses {paymentIntentId} but no prior step tells the developer where to find this value in the API response, leaving the integration flow incomplete.

Confidence Score: 4/5

Safe to merge with a small fix: the paymentIntentId handoff between Step 3 and Step 5 needs to be documented before developers can complete the integration end-to-end.

The guide walks developers through five sequential steps, but Step 5 references a paymentIntentId that is never shown as part of the Step 3 API response. A developer following the guide top-to-bottom will hit a dead end at the submission call with no indication of which response field to use.

api-features/crosschain-payments.mdx — specifically the handoff between the "Getting payment calldata" step and the "Sending the signed data" step.

Important Files Changed

Filename	Overview
api-features/crosschain-payments.mdx	Replaces AI-generated placeholder with a full implementation guide; the paymentIntentId's origin is not documented in the signing-to-submission handoff step, which will block developers at Step 5.

Sequence Diagram

sequenceDiagram
participant Dev as Developer
participant API as Request Network API
participant Wallet as Payer Wallet
Dev->>API: "POST /v2/request (paymentCurrency, amount > 1)"
API-->>Dev: requestId
Dev->>API: "GET /v2/request/{requestId}/routes"
API-->>Dev: Ranked routes (gas fees, service fees)
Dev->>API: "GET /v2/request/{requestId}/pay (selected route)"
API-->>Dev: paymentData (paymentIntent, approvalPermitPayload/calldata, paymentIntentId)
alt Token supports EIP-2612
Dev->>Wallet: signTypedData(approvalPermitPayload)
Wallet-->>Dev: approvalSignature
else Token does not support EIP-2612
Dev->>Wallet: sendTransaction(approvalCalldata)
Wallet-->>Dev: tx receipt
end
Dev->>Wallet: signTypedData(paymentIntent)
Wallet-->>Dev: paymentIntentSignature
Dev->>API: "POST /v2/request/payment-intents/{paymentIntentId} (signedData)"
API-->>Dev: Webhook lifecycle updates (completion event)

Loading

_{Reviews (2): Last reviewed commit: "docs(api-features): align crosschain-pay..." | Re-trigger Greptile}

[greptile-apps]

_{1 file reviewed, 4 comments}

_{Edit Code Review Agent Settings | 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, 4:11 PM UTC: Graphite rebased this pull request as part of a merge.
• May 12, 4:12 PM UTC: @rodrigopavezi merged this pull request with Graphite.

[greptile-apps]

Missing paymentIntentId derivation

The POST URL in Step 5 requires a paymentIntentId, but nowhere in the guide is it explained where this value comes from. Step 3 says the GET /v2/request/{requestId}/pay endpoint returns a "payment intent", and the code in Step 4 does JSON.parse(paymentData.paymentIntent), so paymentIntentId presumably lives as a top-level field in the paymentData response. Without explicitly naming it, a developer reaching Step 5 has no idea which field to use to construct the submission URL.