docs(payment-types): simplify overview and add payment type selection guidance#60
Open
docs(payment-types): simplify overview and add payment type selection guidance#60
Conversation
Clean up `api-features/payment-types-overview.mdx` to avoid overlap with request workflow documentation and keep this page focused on payment type navigation and decision-making. - removed AI-generated warning banner - removed duplicated “Payment Workflows” section (invoice-first/payment-first) - removed workflow-related step from “Choosing a Payment Type” - updated intro/description to focus on payment types only - kept and refined payment type cards: - Native & ERC20 - Conversion - Crosschain - Batch - Recurring - removed hidden/deprecated use-case dependency references - kept API reference pointing to canonical OpenAPI docs: https://api.request.network/open-api
This was referenced Mar 2, 2026
Open
Open
Member
Author
This was referenced Mar 2, 2026
Open
aimensahnoun
changed the title
api-features/payment-types-overview.mdx to avoid overlap with request workflow documentation and keep this page focused on payment type navigation and decision-making. - remov
Greptile SummaryThis PR successfully refocuses the Payment Types Overview page from explaining abstract workflow concepts to providing actionable payment type selection guidance. The changes align with the project's migration from AI-generated content to curated documentation. Key improvements:
Minor suggestion:
All internal links verified, Mintlify component usage correct, and content factually accurate against linked pages. Confidence Score: 5/5
Important Files Changed
Last reviewed commit: e6b580a |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Comment on lines
+41
to
+42
| <Step title="Choose your payment type"> | ||
| Use Native/ERC20 for same-currency flows, Conversion for fiat pricing, and Crosschain when payer and request chains differ. |
There was a problem hiding this comment.
consider breaking this into a bulleted list for easier scanning
Suggested change
| <Step title="Choose your payment type"> | |
| Use Native/ERC20 for same-currency flows, Conversion for fiat pricing, and Crosschain when payer and request chains differ. | |
| Choose based on your requirements: | |
| - **Native/ERC20**: same-currency flows | |
| - **Conversion**: fiat pricing with crypto settlement | |
| - **Crosschain**: payer and request on different chains |
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!
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
Simplified the Payment Types Overview page by removing AI-generated content warnings, streamlining the structure, and focusing on helping users choose the right payment type for their integration.
What changed?
How to test?
Why make this change?
The previous version was overly complex with workflow distinctions that may have confused users. This revision creates a clearer, more actionable guide that helps developers quickly identify which payment type suits their needs without unnecessary conceptual overhead.