docs(protocol-fees): add protocol fees documentation and navigation#68
Open
docs(protocol-fees): add protocol fees documentation and navigation#68
Conversation
…cture nav Introduce a dedicated Protocol Fees page using legacy fee documentation as the source of truth, and register it in API Features navigation. - add `api-features/protocol-fees.mdx` with legacy-aligned protocol fee content - preserve legacy fee structure details (rate, cap, covered payment types) - keep legacy “Who Pays the Fee?” and “Shifting the Fee to the Payee” explanations and examples - include protocol + platform fee coexistence section and metadata response example - update `docs.json` to add `api-features/protocol-fees` under Fee Structure This separates protocol-fee policy from platform-fee implementation and improves Fee Structure discoverability.
This was referenced Mar 2, 2026
Open
Open
Open
Member
Author
This was referenced Mar 2, 2026
aimensahnoun
changed the title
Greptile SummaryAdds comprehensive protocol fees documentation explaining Request Network's 5 basis point fee structure with ~$25/€25 cap on stablecoins. Found two grammar errors and one calculation error in the fee-shifting example that need correction. Key Issues:
What Works Well:
Confidence Score: 3/5
Important Files Changed
Last reviewed commit: c0b0763 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| | ------------ | ---------------------- | ------------------------------------------------- | | ||
| | Protocol Fee | 5 basis points (0.05%) | ~$25/€25 for main USD and EUR backed stablecoins | | ||
|
|
||
| The protocol fees applies to all the payment types |
There was a problem hiding this comment.
grammar: "fees applies" is incorrect - use "fee applies" (singular) or "fees apply" (plural)
Suggested change
| The protocol fees applies to all the payment types | |
| The protocol fee applies to all the payment types |
|
|
||
| ## Shifting the Fee to the Payee | ||
|
|
||
| If you want the payee to bear the protocol fee instead of the payer, simple reduce the invoice amount by 5bps (0.05%) before creating the request. |
There was a problem hiding this comment.
"simple reduce" should be "simply reduce"
Suggested change
| If you want the payee to bear the protocol fee instead of the payer, simple reduce the invoice amount by 5bps (0.05%) before creating the request. | |
| If you want the payee to bear the protocol fee instead of the payer, simply reduce the invoice amount by 5bps (0.05%) before creating the request. |
Comment on lines
+46
to
+51
| - Original intended payment: 1000 USDC | ||
| - Reduce by 0.05%: 1000 - (1000 x 0.05%) = 999.50 USDC | ||
| - Total paid by the payer: 1000 USDC + gas fee | ||
| - Amount received by payee: 999.95 USDC | ||
|
|
||
| This way, the payer pays approximately the original amount while the payee effectively absorbs the fee. |
There was a problem hiding this comment.
incorrect calculation - if invoice is reduced to 999.50 USDC, the payee receives 999.50 USDC, not 999.95 USDC
The math should be:
- Reduced invoice: 999.50 USDC
- Payer pays: 999.50 + (999.50 × 0.05%) ≈ 999.9975 USDC (≈ 1000 USDC)
- Payee receives: 999.50 USDC (not 999.95)
Suggested change
| - Original intended payment: 1000 USDC | |
| - Reduce by 0.05%: 1000 - (1000 x 0.05%) = 999.50 USDC | |
| - Total paid by the payer: 1000 USDC + gas fee | |
| - Amount received by payee: 999.95 USDC | |
| This way, the payer pays approximately the original amount while the payee effectively absorbs the fee. | |
| - Original intended payment: 1000 USDC | |
| - Reduce by 0.05%: 1000 - (1000 x 0.05%) = 999.50 USDC | |
| - Invoice amount: 999.50 USDC | |
| - Protocol fee: 999.50 x 0.05% = 0.4975 USDC | |
| - Total paid by the payer: 999.9975 USDC ≈ 1000 USDC + gas fee | |
| - Amount received by payee: 999.50 USDC |
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
Added comprehensive documentation for protocol fees charged by Request Network API on all payment types.
What changed?
Created a new documentation page
api-features/protocol-fees.mdxthat explains:Added the protocol fees page to the navigation structure under the "Fee Structure" group in
docs.json.How to test?
Review the documentation page to ensure:
Why make this change?
This documentation provides essential transparency about Request Network's fee model, helping developers understand costs associated with API usage and giving them options for fee management in their applications.