Restructure docs: separate creator and developer guides#14
Restructure docs: separate creator and developer guides#14
Conversation
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughRenames the "Guides" nav group to "For creators", adds a "For developers" group, replaces Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
guides/payments.mdx (1)
84-114:⚠️ Potential issue | 🟠 MajorSpell out what happens to card processing fees on refund.
Line 97 says the creator gets back the bounty amount minus the 5% platform fee, but the page also charges a card processing fee upfront in Lines 43-49. Right now the refund section does not tell the reader whether that processing fee is returned or forfeited, so the expected refund amount is ambiguous.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@guides/payments.mdx` around lines 84 - 114, Update the "To cancel a funded bounty" / "Refund calculation" section to explicitly state what happens to card processing fees on refund: in the Steps/Refund calculation area (the "To cancel a funded bounty" block, the <Warning> and the "Refund calculation" example), add a sentence clarifying whether card processing fees charged at payment time are refundable or non-refundable and show the arithmetic in the $500 example adjusted accordingly (e.g., show original amount, platform fee (5%), card processing fee (amount or percentage) and the final refund amount), so readers can unambiguously see the total withheld and the net refund.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@guides/getting-paid.mdx`:
- Line 8: Update the overview sentence that currently promises "Get paid
instantly ... receive 100% of the bounty amount directly to your bank" to avoid
overpromising; change it to state that funds become available in the user's
Stripe account immediately upon approval and are then transferred to their bank
(transfers typically take 1–2 business days). Locate the sentence in the
getting-paid.mdx overview (the current Line 8 text) and revise the wording to
match the later details on Lines 76–78 so the page consistently describes
"available in Stripe immediately, then transferred to the bank (1–2 business
days)."
- Around line 114-117: The bullet point currently reading "No chargebacks: Once
approved, payment is final" is inaccurate; replace that specific bullet ("No
chargebacks: Once approved, payment is final") with a factual line such as
"Payouts may be quick; card payments can still be disputed or charged back—we
support dispute handling and documentation" or "Quick payouts: funds are
released promptly, but payment disputes/chargebacks can still occur and will be
handled per Stripe's policies" so the text no longer guarantees immunity from
chargebacks and accurately reflects Stripe's behavior.
In `@guides/payments.mdx`:
- Around line 8-24: Update every occurrence of the phrase "developer gets paid
instantly" in guides/payments.mdx (notably inside the Step titled "Approve and
pay" and the Step content lines referenced) to qualify that funds are released
to the solver's Stripe balance immediately but that settlement to the solver's
bank account may take 1–2 business days per guides/getting-paid.mdx; replace the
unqualified "instantly" wording with a two-part phrase like "funds are released
to the solver's Stripe balance immediately (bank settlement to their account may
take 1–2 business days)" and apply the same change to the other specified
occurrences (lines ~70-74 and ~127-130).
- Around line 43-49: The "Card processing" fee example is miscalculated: 2.9% of
$500 is $14.50 plus $0.30 = $14.80 (not $15.20). Update the table row labeled
"Card processing" and any example totals in the document (the Tip and the other
example block referenced) to reflect $14.80 and adjust any summed fee or
net-bounty numbers accordingly, or alternatively clarify the fee base if
processing is applied to a different amount; ensure both occurrences of the
example are changed consistently.
---
Outside diff comments:
In `@guides/payments.mdx`:
- Around line 84-114: Update the "To cancel a funded bounty" / "Refund
calculation" section to explicitly state what happens to card processing fees on
refund: in the Steps/Refund calculation area (the "To cancel a funded bounty"
block, the <Warning> and the "Refund calculation" example), add a sentence
clarifying whether card processing fees charged at payment time are refundable
or non-refundable and show the arithmetic in the $500 example adjusted
accordingly (e.g., show original amount, platform fee (5%), card processing fee
(amount or percentage) and the final refund amount), so readers can
unambiguously see the total withheld and the net refund.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 8cf7c4d8-74f7-4b07-a7a4-83505c783fae
📒 Files selected for processing (5)
docs.jsonguides/creating-bounties.mdxguides/getting-paid.mdxguides/payments.mdxguides/solving-bounties.mdx
|
|
||
| ## Overview | ||
|
|
||
| Get paid instantly when your work is approved. No waiting periods, no hassle. Connect your Stripe account and receive 100% of the bounty amount directly to your bank. |
There was a problem hiding this comment.
Don't promise instant bank delivery in the overview.
Line 8 says solvers receive funds directly to their bank with "no waiting periods", but Lines 76-78 later say bank transfers take 1-2 business days. Please align this to "available in Stripe immediately, then transferred to the bank" so the page does not overpromise payout timing.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@guides/getting-paid.mdx` at line 8, Update the overview sentence that
currently promises "Get paid instantly ... receive 100% of the bounty amount
directly to your bank" to avoid overpromising; change it to state that funds
become available in the user's Stripe account immediately upon approval and are
then transferred to their bank (transfers typically take 1–2 business days).
Locate the sentence in the getting-paid.mdx overview (the current Line 8 text)
and revise the wording to match the later details on Lines 76–78 so the page
consistently describes "available in Stripe immediately, then transferred to the
bank (1–2 business days)."
| - **Escrow system**: Funds are held securely until work is approved | ||
| - **Instant release**: Payment processes immediately upon approval | ||
| - **Stripe powered**: All payments processed through Stripe's secure infrastructure | ||
| - **No chargebacks**: Once approved, payment is final |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Can card-funded Stripe payments still be disputed or charged back after funds have been paid out to a connected account?
💡 Result:
Yes. A card payment can still be disputed/charged back even after the funds have already been paid out to a connected account—payout doesn’t “finalize” card payments. (docs.stripe.com)
What happens financially depends on your Connect charge type:
- Destination charges / Separate charges & transfers: Stripe debits the dispute amount + dispute fee from the platform (and the platform can try to recover the funds by reversing the transfer, but that only works if the connected account has sufficient balance). (docs.stripe.com)
- Direct charges (on the connected account): Stripe debits the connected account for the dispute/chargeback. (docs.stripe.com)
If the account that’s being debited doesn’t have enough Stripe balance at the time, it can go negative, and Stripe may debit the linked bank (“payout”) account to cover what’s owed (per the Connected Account Agreement). (stripe.com)
Citations:
- 1: https://docs.stripe.com/disputes/connect?utm_source=openai
- 2: https://docs.stripe.com/disputes/connect?utm_source=openai
- 3: https://docs.stripe.com/connect/charges?utm_source=openai
- 4: https://stripe.com/en-li/legal/connect-account?utm_source=openai
Rewrite "No chargebacks" claim to accurately reflect Stripe's behavior.
Line 117 states "No chargebacks: Once approved, payment is final." This is inaccurate. Stripe documentation confirms that card payments can still be disputed or charged back even after funds have been paid out to a connected account. Payout does not prevent chargebacks. Rewrite this point to describe the actual platform workflow (e.g., "Quick payouts" or "Streamlined approval process") rather than making a guarantee that contradicts Stripe's actual policy.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@guides/getting-paid.mdx` around lines 114 - 117, The bullet point currently
reading "No chargebacks: Once approved, payment is final" is inaccurate; replace
that specific bullet ("No chargebacks: Once approved, payment is final") with a
factual line such as "Payouts may be quick; card payments can still be disputed
or charged back—we support dispute handling and documentation" or "Quick
payouts: funds are released promptly, but payment disputes/chargebacks can still
occur and will be handled per Stripe's policies" so the text no longer
guarantees immunity from chargebacks and accurately reflects Stripe's behavior.
| Fund your bounties with a credit card and let bounty.new handle the rest. When you approve a submission, the developer gets paid instantly—no manual transfers, no hassle. | ||
|
|
||
| ## How it works | ||
|
|
||
| ### For creators | ||
|
|
||
| <Steps> | ||
| <Step title="Create bounties"> | ||
| Funds are held in our platform account when you publish a bounty. | ||
| <Step title="Create a bounty"> | ||
| Set up your bounty with a clear description and reward amount. | ||
| </Step> | ||
| <Step title="Approve work"> | ||
| When you approve a submission, the payout processes instantly, and the winning submission gets paid immediately. | ||
| <Step title="Fund it"> | ||
| Pay upfront with a credit card. Funds are held in escrow. | ||
| </Step> | ||
| </Steps> | ||
|
|
||
| ### For developers | ||
|
|
||
| <Steps> | ||
| <Step title="Complete work"> | ||
| Submit your solution for a bounty. | ||
| </Step> | ||
| <Step title="Get approved"> | ||
| Creator reviews and approves your submission. | ||
| <Step title="Review submissions"> | ||
| Developers submit solutions. You review and test their work. | ||
| </Step> | ||
| <Step title="Receive payment"> | ||
| Funds hit your account immediately—no waiting period. | ||
| <Step title="Approve and pay"> | ||
| When you approve a submission, the developer gets paid instantly. | ||
| </Step> |
There was a problem hiding this comment.
Keep payout timing consistent with the solver docs.
This page repeatedly says the developer is paid "instantly", while guides/getting-paid.mdx says bank transfers take 1-2 business days. Please qualify this as funds being released to the solver's Stripe balance instantly, otherwise readers may interpret it as same-minute bank settlement.
Also applies to: 70-74, 127-130
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@guides/payments.mdx` around lines 8 - 24, Update every occurrence of the
phrase "developer gets paid instantly" in guides/payments.mdx (notably inside
the Step titled "Approve and pay" and the Step content lines referenced) to
qualify that funds are released to the solver's Stripe balance immediately but
that settlement to the solver's bank account may take 1–2 business days per
guides/getting-paid.mdx; replace the unqualified "instantly" wording with a
two-part phrase like "funds are released to the solver's Stripe balance
immediately (bank settlement to their account may take 1–2 business days)" and
apply the same change to the other specified occurrences (lines ~70-74 and
~127-130).
| | Fee type | Amount | When charged | | ||
| | ----------------- | ----------- | ---------------------- | | ||
| | Platform fee | 5% | When bounty is created | | ||
| | Card processing | 2.9% + $0.30| When bounty is created | | ||
|
|
||
| <Tip> | ||
| Developers keep 100% of the bounty amount. Creators pay a 5% platform fee. | ||
| Developers receive 100% of the bounty amount. You pay the platform fee and processing fees upfront. |
There was a problem hiding this comment.
The fee example doesn't match the pricing formula above.
Lines 46 and 59 conflict: 2.9% + $0.30 on $500.00 is $14.80, not $15.20. Please either recalculate the example or document the actual fee base if processing is applied to something other than the bounty amount.
Also applies to: 54-64
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@guides/payments.mdx` around lines 43 - 49, The "Card processing" fee example
is miscalculated: 2.9% of $500 is $14.50 plus $0.30 = $14.80 (not $15.20).
Update the table row labeled "Card processing" and any example totals in the
document (the Tip and the other example block referenced) to reflect $14.80 and
adjust any summed fee or net-bounty numbers accordingly, or alternatively
clarify the fee base if processing is applied to a different amount; ensure both
occurrences of the example are changed consistently.
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Actionable comments posted: 6
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs.json`:
- Around line 17-21: Docs were updated to rename the creator payment guide but a
hard-coded link in integrations/linear.mdx still points to "/guides/payments";
open integrations/linear.mdx and in the "Payment settings" card (around the
bootstrap/link block that links to the payments guide) replace the href/path
"/guides/payments" with "/guides/funding-bounties" so the next-step link matches
the renamed page.
- Around line 23-27: The "For developers" navigation entry currently lists only
the "pages" array containing "guides/solving-bounties" — add the new guide path
"guides/getting-paid" to that "pages" array (e.g., alongside
"guides/solving-bounties") so the "For developers" group includes the new
getting-paid page in the primary nav.
In `@guides/funding-bounties.mdx`:
- Around line 43-46: The fee table lists a 5% platform fee and a 2.9% + $0.30
card processing fee but the refund example returns $475.00 (dropping processing
fees), creating an inconsistency; update the refund wording and example to be
consistent by either (A) stating explicitly that both the 5% platform fee and
the card-processing fee (2.9% + $0.30) are non-refundable and adjust the refund
example math to subtract both fees, or (B) explicitly state only the 5% is
non-refundable and then update the refund example to refund the card-processing
amount as well; apply the same change to the corresponding section in the
creating-bounties guide so both guides reference the same rule and use the same
example math/formula.
- Around line 54-64: Update the worked example block showing the $500 bounty so
the card processing fee and total charged reflect the stated 2.9% + $0.30 rule:
change the "Card processing:" value from $15.20 to $14.80 and update "Total
charged:" from $540.20 to $539.80 in the code block that lists "Bounty amount:",
"Platform fee (5%):", "Card processing:", and "Total charged:" so the math
matches the fee formula.
In `@guides/solving-bounties.mdx`:
- Around line 22-24: Update the Step titled "Get paid instantly" so it no longer
promises immediate bank settlement; change the copy to state that the payout is
initiated/processed immediately upon approval but that bank availability depends
on the chosen method (e.g., ACH typically 1–2 business days). Edit the content
used in the Step component (Step title="Get paid instantly") to explicitly
mention the payout is initiated instantly and reference the ACH timing
consistency with the later table.
- Around line 58-60: Remove the internal editorial placeholder Note blocks that
contain the "**Screenshot placeholder**" text in the markdown (e.g., the <Note>
blocks with "**Screenshot placeholder**: Shows the bounty card..."); either
replace each with a real caption beneath the final image or delete the Note
entirely until the screenshot is ready—apply this to all occurrences that match
the same placeholder pattern in the file.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: fb558cde-9d59-4caf-aeca-55cf9dcac935
📒 Files selected for processing (4)
docs.jsonguides/creating-bounties.mdxguides/funding-bounties.mdxguides/solving-bounties.mdx
| "group": "For creators", | ||
| "pages": [ | ||
| "guides/creating-bounties", | ||
| "guides/payments" | ||
| "guides/funding-bounties" | ||
| ] |
There was a problem hiding this comment.
Finish the /guides/payments → /guides/funding-bounties migration.
After renaming the creator payment guide here, integrations/linear.mdx:96-105 still links to /guides/payments from its “Payment settings” card. Readers following that next step will hit the old route.
Suggested follow-up in integrations/linear.mdx
- <Card title="Payment settings" icon="credit-card" href="/guides/payments">
- Configure payouts and billing.
+ <Card title="Funding bounties" icon="credit-card" href="/guides/funding-bounties">
+ Learn about payment methods and fees.
</Card>🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs.json` around lines 17 - 21, Docs were updated to rename the creator
payment guide but a hard-coded link in integrations/linear.mdx still points to
"/guides/payments"; open integrations/linear.mdx and in the "Payment settings"
card (around the bootstrap/link block that links to the payments guide) replace
the href/path "/guides/payments" with "/guides/funding-bounties" so the
next-step link matches the renamed page.
| { | ||
| "group": "For developers", | ||
| "pages": [ | ||
| "guides/solving-bounties" | ||
| ] |
There was a problem hiding this comment.
Add the new guides/getting-paid page to the developer nav.
The PR objective adds a dedicated getting-paid guide, but this group exposes only guides/solving-bounties. That leaves the payout guide orphaned from the primary navigation.
Suggested navigation update
{
"group": "For developers",
"pages": [
- "guides/solving-bounties"
+ "guides/solving-bounties",
+ "guides/getting-paid"
]
},📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| { | |
| "group": "For developers", | |
| "pages": [ | |
| "guides/solving-bounties" | |
| ] | |
| { | |
| "group": "For developers", | |
| "pages": [ | |
| "guides/solving-bounties", | |
| "guides/getting-paid" | |
| ] | |
| }, |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs.json` around lines 23 - 27, The "For developers" navigation entry
currently lists only the "pages" array containing "guides/solving-bounties" —
add the new guide path "guides/getting-paid" to that "pages" array (e.g.,
alongside "guides/solving-bounties") so the "For developers" group includes the
new getting-paid page in the primary nav.
| | Fee type | Amount | When charged | | ||
| | ----------------- | ----------- | ---------------------- | | ||
| | Platform fee | 5% | When bounty is created | | ||
| | Card processing | 2.9% + $0.30| When bounty is created | |
There was a problem hiding this comment.
Make the refund policy consistent with the fee section.
The guide says the 5% platform fee is the non-refundable part, but the refund example on Line 113 returns only $475.00 and drops the card-processing fee entirely. Either document that processing fees are also non-refundable or include them in the refund math; right now the stated policy and the example cannot both be true. This same rule should stay aligned with guides/creating-bounties.mdx Lines 153-159.
Also applies to: 76-113
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@guides/funding-bounties.mdx` around lines 43 - 46, The fee table lists a 5%
platform fee and a 2.9% + $0.30 card processing fee but the refund example
returns $475.00 (dropping processing fees), creating an inconsistency; update
the refund wording and example to be consistent by either (A) stating explicitly
that both the 5% platform fee and the card-processing fee (2.9% + $0.30) are
non-refundable and adjust the refund example math to subtract both fees, or (B)
explicitly state only the 5% is non-refundable and then update the refund
example to refund the card-processing amount as well; apply the same change to
the corresponding section in the creating-bounties guide so both guides
reference the same rule and use the same example math/formula.
| For a $500 bounty: | ||
|
|
||
| ``` | ||
| Bounty amount: $500.00 | ||
| Platform fee (5%): $ 25.00 | ||
| Card processing: $ 15.20 | ||
| ───────────────────────────── | ||
| Total charged: $540.20 | ||
|
|
||
| Developer receives: $500.00 | ||
| ``` |
There was a problem hiding this comment.
Fix the worked example math.
Line 46 says card processing is 2.9% + $0.30, so on a $500 bounty that fee is $14.80, not $15.20. The total charged should be $539.80, not $540.20.
Corrected example
For a $500 bounty:
Bounty amount: $500.00
Platform fee (5%): $ 25.00
-Card processing: $ 15.20
+Card processing: $ 14.80
─────────────────────────────
-Total charged: $540.20
+Total charged: $539.80
Developer receives: $500.00
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@guides/funding-bounties.mdx` around lines 54 - 64, Update the worked example
block showing the $500 bounty so the card processing fee and total charged
reflect the stated 2.9% + $0.30 rule: change the "Card processing:" value from
$15.20 to $14.80 and update "Total charged:" from $540.20 to $539.80 in the code
block that lists "Bounty amount:", "Platform fee (5%):", "Card processing:", and
"Total charged:" so the math matches the fee formula.
guides/solving-bounties.mdx
Outdated
| <Step title="Get paid instantly"> | ||
| Once approved, funds hit your account immediately. | ||
| </Step> |
There was a problem hiding this comment.
Clarify the payout timing so it matches the table below.
Line 23 says funds hit the account immediately, but Line 198 says bank availability takes 1-2 business days via ACH. Reword the earlier copy to say the payout is initiated instantly; otherwise this guide promises faster settlement than it documents later.
Suggested copy update
- <Step title="Get paid instantly">
- Once approved, funds hit your account immediately.
+ <Step title="Get paid fast">
+ Once approved, your payout is initiated immediately.
</Step>
...
When the bounty creator approves your submission:
-- Funds transfer to your bank account immediately
+- Payout is initiated immediately
- You receive an email confirmation
- Payment appears in your Stripe dashboard
- Bounty is marked as complete
...
-| Event | Timing |
-| ----- | ------ |
-| Submission approved | Instant |
-| Funds sent to your bank | Instant |
-| Funds available in your account | 1-2 business days (standard ACH) |
+| Event | Timing |
+| ----- | ------ |
+| Submission approved | Instant |
+| Payout initiated | Instant |
+| Funds available in your bank account | 1-2 business days (standard ACH) |Also applies to: 181-199
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@guides/solving-bounties.mdx` around lines 22 - 24, Update the Step titled
"Get paid instantly" so it no longer promises immediate bank settlement; change
the copy to state that the payout is initiated/processed immediately upon
approval but that bank availability depends on the chosen method (e.g., ACH
typically 1–2 business days). Edit the content used in the Step component (Step
title="Get paid instantly") to explicitly mention the payout is initiated
instantly and reference the ACH timing consistency with the later table.
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
guides/solving-bounties.mdx (1)
8-8:⚠️ Potential issue | 🟠 MajorAlign all payout copy with the ACH settlement timing.
The guide still promises immediate bank settlement in several places, but the timeline below says ACH funds become available in
1-2 business days. Please standardize this page on “payout initiated immediately” / “approval is instant” and keep bank availability separate; otherwise the doc overpromises payout speed.Suggested copy update
-Get paid for solving real problems. Find bounties, submit your solution, and receive instant payment when approved—no waiting periods, no hassle. +Get paid for solving real problems. Find bounties, submit your solution, and have your payout initiated as soon as it's approved. <Step title="Set up payouts (one-time)"> - Connect your bank account via Stripe Connect to receive instant payouts. Takes 2 minutes. + Connect your bank account via Stripe Connect so payouts can be initiated as soon as your work is approved. </Step> ... - <Step title="Get paid instantly"> - Once approved, funds hit your account immediately. + <Step title="Get paid fast"> + Once approved, your payout is initiated immediately. Bank availability depends on the payout method; standard ACH typically takes 1-2 business days. </Step> ... <Step title="Start solving"> - Once verified, you can submit solutions and receive instant payouts. + Once verified, you can submit solutions and receive payouts as soon as approved. </Step> ... ### Instant payouts When the bounty creator approves your submission: -- Funds transfer to your bank account immediately +- Payout is initiated immediately - You receive an email confirmation - Payment appears in your Stripe dashboard - Bounty is marked as complete ... -| Submission approved | Instant | -| Funds sent to your bank | Instant | -| Funds available in your account | 1-2 business days (standard ACH) | +| Submission approved | Instant | +| Payout initiated | Instant | +| Funds available in your bank account | 1-2 business days (standard ACH) | ... <Accordion title="How long does it take to get paid?"> - Payment is instant when approved. Funds typically appear in your bank account within 1-2 business days via ACH. + Your payout is initiated immediately when approved. Funds typically appear in your bank account within 1-2 business days via ACH. </Accordion>Also applies to: 16-24, 57-59, 127-146, 209-210
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@guides/solving-bounties.mdx` at line 8, The headline sentence "Get paid for solving real problems..." and all other payout statements (including the sections around the provided line ranges) currently imply immediate bank settlement; update copy to clearly separate approval vs bank availability by saying approval/payout is initiated/approved instantly (e.g., "payout initiated immediately upon approval" or "approval is instant") and then explicitly note that bank settlement via ACH typically posts in 1–2 business days (or similar phrasing). Replace any instances that claim instant bank deposit with this two-part phrasing across the page (search for the headline sentence and the blocks near the noted ranges) so the doc promises instant approval/initiating of payout while accurately describing ACH timing.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@index.mdx`:
- Around line 40-42: The Card component with title "Set up instant payouts"
currently links to the solving-bounties guide; update its href attribute on the
Card (the Card with title "Set up instant payouts") to point to the new guide by
changing href="/guides/solving-bounties#setting-up-payouts" to
href="/guides/getting-paid" so the card surfaces the new getting-paid guide from
the docs landing page.
---
Duplicate comments:
In `@guides/solving-bounties.mdx`:
- Line 8: The headline sentence "Get paid for solving real problems..." and all
other payout statements (including the sections around the provided line ranges)
currently imply immediate bank settlement; update copy to clearly separate
approval vs bank availability by saying approval/payout is initiated/approved
instantly (e.g., "payout initiated immediately upon approval" or "approval is
instant") and then explicitly note that bank settlement via ACH typically posts
in 1–2 business days (or similar phrasing). Replace any instances that claim
instant bank deposit with this two-part phrasing across the page (search for the
headline sentence and the blocks near the noted ranges) so the doc promises
instant approval/initiating of payout while accurately describing ACH timing.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: ba30bcb8-4312-4d3f-b52f-9dd619c71355
📒 Files selected for processing (2)
guides/solving-bounties.mdxindex.mdx
| <Card title="Set up instant payouts" icon="bolt" href="/guides/solving-bounties#setting-up-payouts"> | ||
| Connect your bank account to receive payments immediately. | ||
| </Card> |
There was a problem hiding this comment.
Point this card at the new getting-paid guide.
Line 40 currently sends readers back into solving-bounties, but this PR introduces a separate payout guide. Given docs.json Line 15-28 only surfaces guides/solving-bounties in the developer nav snippet, this leaves guides/getting-paid.mdx hard to discover from the docs landing page.
Suggested tweak
- <Card title="Set up instant payouts" icon="bolt" href="/guides/solving-bounties#setting-up-payouts">
- Connect your bank account to receive payments immediately.
+ <Card title="Getting paid" icon="bolt" href="/guides/getting-paid">
+ Connect your payout details and learn how instant payouts work.
</Card>🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@index.mdx` around lines 40 - 42, The Card component with title "Set up
instant payouts" currently links to the solving-bounties guide; update its href
attribute on the Card (the Card with title "Set up instant payouts") to point to
the new guide by changing href="/guides/solving-bounties#setting-up-payouts" to
href="/guides/getting-paid" so the card surfaces the new getting-paid guide from
the docs landing page.
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
1 participant
Split documentation into clear "For creators" and "For developers" sections for better UX. Added new "Solving bounties" guide with efficiency tips and separated payment documentation by user role.
Files changed:
guides/solving-bounties.mdx- New comprehensive guide for developers on finding and solving bounties efficientlyguides/getting-paid.mdx- New developer-focused payout guideguides/payments.mdx- Refocused as "Funding bounties" for creators onlyguides/creating-bounties.mdx- Fixed cross-references to new guide structuredocs.json- Reorganized navigation into "For creators" and "For developers" sectionsSummary by CodeRabbit