Uh oh!
There was an error while loading. Please reload this page.
docs(standard-payments): remove AI warning, restructure content with step-by-step flow, and update API references - #62
Conversation
This was referenced Mar 2, 2026
Merged
Merged
ContributorAuthor
This was referenced Mar 2, 2026
Merged
api-features/standard-payments.mdx from AI-generated placeholder content into a clearer, endpoint-driven page aligned with current API behavior. - removed AI warning banner anaimen74
marked this pull request as ready for review
March 2, 2026 12:09
Greptile SummaryThis PR rewrites the standard payments documentation page, removing the AI-generated content warning and providing clearer, more structured guidance on same-currency crypto payments with a new step-by-step "How It Works" section and updated API references.
Confidence Score: 5/5Documentation-only change with no runtime impact; all internal links resolve to existing pages. The change is purely additive documentation restructuring. All four internal links resolve to existing files in the repository, the external OpenAPI links follow the same anchor scheme used elsewhere in the docs, and no code is modified. No files require special attention. Important Files Changed
Sequence DiagramsequenceDiagram
participant Dev as Developer
participant API as Request Network API
participant Chain as Blockchain
Note over Dev,Chain: Request-first flow
Dev->>API: "POST /v2/request (invoiceCurrency == paymentCurrency)"
API-->>Dev: requestId
Dev->>API: "GET /v2/request/{requestId}/pay"
API-->>Dev: calldata (+ approval calldata if ERC20)
alt ERC20 payment requiring approval
Dev->>Chain: Execute approval transaction
Chain-->>Dev: approval confirmed
end
Dev->>Chain: Execute payment transaction
Chain-->>Dev: payment confirmed
Note over Dev,Chain: Payment-first flow
Dev->>API: "POST /v2/payouts (invoiceCurrency == paymentCurrency)"
API-->>Dev: payout initiated
Reviews (2): Last reviewed commit: "docs(api-features): rewrite standard-pay..." | Re-trigger Greptile |
This was referenced Mar 2, 2026
Merged
Merged
This was referenced Mar 3, 2026
This was referenced Mar 30, 2026
This was referenced May 8, 2026
Contributor
Merge activity
|
rodrigopavezi
changed the base branch from
03-02-docs_api-features_rewrite_conversion-payments_with_verified_api_behavior_refactor_api-features_conversion-payments.mdx_from_ai-generated_placeholder_content_into_endpoint-driven_documentation_aligned_with_current_api_behavior._-
to
graphite-base/62May 12, 2026 16:21
Refactor `api-features/standard-payments.mdx` from AI-generated placeholder
content into a clearer, endpoint-driven page aligned with current API behavior.
- removed AI warning banner and unsupported assumptions
- clarified standard payments as same-currency flows where
`invoiceCurrency` and `paymentCurrency` match
- split behavior between Native and ERC20 payments with accurate
execution characteristics (approval vs no-approval paths)
- added practical “How It Works” steps with direct endpoint references:
- POST /v2/request
- POST /v2/payouts
- GET /v2/request/{requestId}/pay
- replaced vague token/network claims (e.g. “500+ tokens”) with
references to authoritative supported-currency resources
- removed hidden/unsupported use-case links (`payouts`, `payroll`)
and kept active links (`invoicing`, `checkout`)
- updated technical reference to canonical OpenAPI docs:
https://api.request.network/open-apirodrigopaveziforce-pushed
the
03-02-docs_api-features_rewrite_standard-payments_with_verified_api_flow_refactor_api-features_standard-payments.mdx_from_ai-generated_placeholder_content_into_a_clearer_endpoint-driven_page_aligned_with_current_api_behavior._-_remove
branch
from
May 12, 2026 16:23
ad72ad5 to
4e4d0f8CompareUh oh!
There was an error while loading. Please reload this page.
rodrigopavezi
deleted the
03-02-docs_api-features_rewrite_standard-payments_with_verified_api_flow_refactor_api-features_standard-payments.mdx_from_ai-generated_placeholder_content_into_a_clearer_endpoint-driven_page_aligned_with_current_api_behavior._-_remove
branch
May 12, 2026 16:24
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Rewrote the standard payments documentation to remove AI-generated content warning and provide clearer, more structured guidance on same-currency crypto payments.
What changed?
invoiceCurrencyandpaymentCurrencymatchHow to test?
Why make this change?
The previous version contained an AI-generated content warning and lacked clear implementation guidance. This revision provides developers with more precise definitions, clearer implementation steps, and removes uncertainty about content accuracy while maintaining technical accuracy.