docs(crosschain-payments): replace AI-generated content with comprehensive implementation guide#56
Open
docs(crosschain-payments): replace AI-generated content with comprehensive implementation guide#56
Conversation
Update `api-features/crosschain-payments.mdx` to follow legacy content structure and sequencing while keeping Mintlify-compatible formatting. - Replaced mixed/rewritten content with legacy-aligned section flow - Removed non-legacy “get in touch” block - Kept supported chains/currencies explicitly on-page (crosschain-specific) - Converted “How It Works” to step-based structure using Mintlify `Steps` - Kept endpoint links directly inside the relevant steps (legacy-style placement) - Restored signing code example in step 4 - Removed extra “Used In” section - Removed separate endpoint dump section that made the page noisy - Updated custom fee note to reflect current availability and link to `/api-features/platform-fees` (instead of “in development”)
This was referenced Mar 2, 2026
Open
Member
Author
This was referenced Mar 2, 2026
Open
aimensahnoun
changed the title
api-features/crosschain-payments.mdx to follow legacy content structure and sequencing while keeping Mintlify-compatible formatting. - Replaced mixed/rewritten content with 
Greptile SummarySuccessfully replaces AI-generated placeholder content with comprehensive implementation guide for crosschain payments functionality. Key Improvements:
Minor Improvements Suggested:
Confidence Score: 4/5
Important Files Changed
Last reviewed commit: 76e5cbc |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
|
|
||
| ## Crosschain Payments Supported Chains and Currencies | ||
|
|
||
| For crosschain (and samechain) payments, the Request Network API supports 12 stablecoins: USDC, USDT, and DAI on 4 chains (Ethereum, Arbitrum One, Base, OP Mainnet). |
There was a problem hiding this comment.
Wording could be clearer: states "12 stablecoins" but only 3 stablecoin types are listed (USDC, USDT, DAI). Consider: "3 stablecoins (USDC, USDT, and DAI) across 4 chains, totaling 12 currency-chain pairs"
| To enable crosschain payments, the request must be created with: | ||
|
|
||
| - `paymentCurrency` in the supported stablecoins and supported networks | ||
| - `amount` greater than 1 (crosschain execution under 1 stablecoin is not allowed) |
There was a problem hiding this comment.
Ambiguous amount requirement: "greater than 1" typically means > 1, but "under 1 is not allowed" suggests >= 1 is valid. Clarify whether the minimum is 1 or 1.01
Comment on lines
+84
to
+86
| const ethersProvider = new ethers.providers.Web3Provider( | ||
| walletProvider as ethers.providers.ExternalProvider, | ||
| ); |
There was a problem hiding this comment.
Uses deprecated ethers v5 syntax (ethers.providers.Web3Provider). The Integration Tutorial uses wagmi. Consider updating to ethers v6 syntax or wagmi for consistency:
// Ethers v6 syntax
import { BrowserProvider } from "ethers";
const ethersProvider = new BrowserProvider(walletProvider);Or align with the wagmi pattern from /api-setup/integration-tutorial
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Comment on lines
+82
to
+89
| import { ethers } from "ethers"; | ||
|
|
||
| const ethersProvider = new ethers.providers.Web3Provider( | ||
| walletProvider as ethers.providers.ExternalProvider, | ||
| ); | ||
| const signer = await ethersProvider.getSigner(); | ||
|
|
||
| const paymentIntent = JSON.parse(paymentData.paymentIntent); |
There was a problem hiding this comment.
Code example references undefined variables walletProvider and paymentData. Add context showing where these come from (e.g., from the /v2/request/{requestId}/pay API response)
This was referenced Mar 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR
Replaced AI-generated placeholder content with comprehensive documentation for crosschain payments functionality, including detailed implementation steps and supported networks.
What changed?
How to test?
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.