docs: fix implementation discrepancies across API docs#85
docs: fix implementation discrepancies across API docs#85
Conversation
Align documentation with actual codebase after cross-referencing request-api, request-auth-api, request-dashboard, and request-secure-payment implementations. - fix secure payment URL from secure.request.network to pay.request.network - add LiFi as the crosschain bridge provider in crosschain-payments - update chain counts from "9 EVM chains, 150+ currencies" to "10+ EVM chains and Tron, 500+ currencies" in checkout and invoicing - add missing chains (Gnosis, Mantle) to supported-chains-and-currencies - separate mainnet and testnet lists in recurring-payments and supported-chains-and-currencies
Greptile SummaryThis PR aligns several documentation pages with the actual implementation across Key changes include:
One minor terminology inconsistency was found: Confidence Score: 5/5
Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["PR #85: Fix Implementation Discrepancies"] --> B["secure-payments.mdx\nURL: secure → pay.request.network"]
A --> C["crosschain-payments.mdx\nAdd LiFi attribution"]
A --> D["supported-chains-and-currencies.mdx\nAdd Gnosis + Mantle\nSplit Mainnet / Testnet"]
A --> E["recurring-payments.mdx\nSplit Mainnet / Testnet"]
A --> F["checkout.mdx + invoicing.mdx\n9 chains / 150+ → 10+ chains & Tron / 500+"]
D --> G["Canonical chain list\n11 EVM Mainnet + Tron + Sepolia testnet"]
F --> G
E --> H["⚠️ Still uses 'Arbitrum' & 'Binance Smart Chain'\nvs canonical 'Arbitrum One' & 'BSC'"]
Reviews (1): Last reviewed commit: "docs: fix implementation discrepancies a..." | Re-trigger Greptile |
| - Arbitrum | ||
| - Gnosis | ||
| - Base | ||
| - Binance Smart Chain |
There was a problem hiding this comment.
Inconsistent chain names vs. canonical reference page
recurring-payments.mdx uses "Arbitrum" (line 74) and "Binance Smart Chain" (line 77), while resources/supported-chains-and-currencies.mdx — the source of truth updated in this same PR — uses "Arbitrum One" and "BSC" respectively. Per the style guide, terminology should be consistent throughout all documentation.
| - Arbitrum | |
| - Gnosis | |
| - Base | |
| - Binance Smart Chain | |
| - Arbitrum One | |
| - Gnosis | |
| - Base | |
| - BSC |

Align documentation with actual codebase after cross-referencing
request-api, request-auth-api, request-dashboard, and
request-secure-payment implementations.
"10+ EVM chains and Tron, 500+ currencies" in checkout and invoicing
supported-chains-and-currencies