Skip to content

docs: fix implementation discrepancies across API docs#85

Open
rodrigopavezi wants to merge 1 commit into03-04-docs_nav_remove_beta_banner_and_hide_sdk_legacy_tab_from_navigation_clean_up_global_docs_navigation_by_removing_the_temporary_beta_status_messaging_and_taking_the_sdk_legacy_tab_out_of_the_top-level_tabs_for_now._-_removed_bannefrom
docs/fix-implementation-discrepancies
Open

docs: fix implementation discrepancies across API docs#85
rodrigopavezi wants to merge 1 commit into03-04-docs_nav_remove_beta_banner_and_hide_sdk_legacy_tab_from_navigation_clean_up_global_docs_navigation_by_removing_the_temporary_beta_status_messaging_and_taking_the_sdk_legacy_tab_out_of_the_top-level_tabs_for_now._-_removed_bannefrom
docs/fix-implementation-discrepancies

Conversation

@rodrigopavezi
Copy link
Copy Markdown
Member

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

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
Copy link
Copy Markdown
Member Author

rodrigopavezi commented Mar 30, 2026

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

This stack of pull requests is managed by Graphite. Learn more about stacking.

@rodrigopavezi rodrigopavezi changed the base branch from 03-04-docs_nav_remove_beta_banner_and_hide_sdk_legacy_tab_from_navigation_clean_up_global_docs_navigation_by_removing_the_temporary_beta_status_messaging_and_taking_the_sdk_legacy_tab_out_of_the_top-level_tabs_for_now._-_removed_banne to graphite-base/85 March 30, 2026 18:15
@rodrigopavezi rodrigopavezi changed the base branch from graphite-base/85 to 03-04-docs_nav_remove_beta_banner_and_hide_sdk_legacy_tab_from_navigation_clean_up_global_docs_navigation_by_removing_the_temporary_beta_status_messaging_and_taking_the_sdk_legacy_tab_out_of_the_top-level_tabs_for_now._-_removed_banne March 30, 2026 18:21
This was referenced Mar 30, 2026
@greptile-apps
Copy link
Copy Markdown

greptile-apps bot commented Mar 30, 2026

Greptile Summary

This PR aligns several documentation pages with the actual implementation across request-api, request-auth-api, request-dashboard, and request-secure-payment.

Key changes include:

  • Secure payment URL fix — corrects the example response URL from secure.request.network to pay.request.network, matching the live hosted payment app.
  • LiFi attribution — adds an explicit callout that crosschain routing is powered by LiFi, giving readers context on the underlying bridge/DEX aggregator.
  • Chain count updates — updates "9 EVM chains, 150+ currencies" to "10+ EVM chains and Tron, 500+ currencies" across checkout.mdx and invoicing.mdx, both of which now link to the canonical supported-chains page.
  • New chain additions — adds Gnosis and Mantle to the mainnet list in supported-chains-and-currencies.mdx, bringing the count to 11 mainnet EVM chains (consistent with "10+").
  • Mainnet/Testnet separation — both recurring-payments.mdx and supported-chains-and-currencies.mdx now clearly distinguish mainnet from testnet networks.

One minor terminology inconsistency was found: recurring-payments.mdx still uses "Arbitrum" and "Binance Smart Chain" where the canonical reference page (also updated in this PR) uses "Arbitrum One" and "BSC".

Confidence Score: 5/5

  • Safe to merge — all changes are documentation-only factual corrections with no logic or code impact.
  • All six changed files are .mdx documentation. The fixes (URL correction, LiFi attribution, chain count updates, Gnosis/Mantle additions, mainnet/testnet separation) are accurate and sourced directly from the actual implementations. The one remaining finding is a P2 style issue (inconsistent chain names in recurring-payments.mdx), which does not affect correctness or user safety and does not block merging.
  • api-features/recurring-payments.mdx — minor chain naming inconsistency ("Arbitrum" / "Binance Smart Chain") vs the canonical reference page.

Important Files Changed

Filename Overview
api-features/crosschain-payments.mdx Added LiFi attribution as the crosschain routing provider in the Overview section — factual addition with no issues.
api-features/recurring-payments.mdx Added Mainnet/Testnet headings to separate network lists; chain name "Arbitrum" and "Binance Smart Chain" are inconsistent with the canonical names used in supported-chains-and-currencies.mdx ("Arbitrum One", "BSC").
api-reference/secure-payments.mdx Corrected securePaymentUrl domain from secure.request.network to pay.request.network to match the actual hosted payment app URL.
resources/supported-chains-and-currencies.mdx Added Gnosis and Mantle to the mainnet chain list, separated mainnet/testnet sections, now accurately reflects 11 mainnet EVM chains.
use-cases/checkout.mdx Updated chain/currency counts from "9 EVM chains, 150+ currencies" to "10+ EVM chains and Tron, 500+ currencies" with a link to the supported chains page.
use-cases/invoicing.mdx Updated chain/currency counts from "9 EVM chains, 150+ currencies" to "10+ EVM chains and Tron, 500+ currencies" in two places, both now linking to the supported chains page.

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'"]
Loading

Reviews (1): Last reviewed commit: "docs: fix implementation discrepancies a..." | Re-trigger Greptile

Comment on lines 74 to 77
- Arbitrum
- Gnosis
- Base
- Binance Smart Chain
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 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.

Suggested change
- Arbitrum
- Gnosis
- Base
- Binance Smart Chain
- Arbitrum One
- Gnosis
- Base
- BSC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant