Written by Table of contents
- Do I need to find a bounty first?
- What is the difference between a bounty and a Payment Request?
- Can a client pay without GitHub?
- When does the provider receive money?
- Can teams and organizations use Gitpay?
- What if work or payment is disputed?
- Where should I go next?
Gitpay connects useful work with payment. Start with What is Gitpay? for the two main paths: project contributions and Payment Requests for delivered work.
Do I need to find a bounty first?
No. A funded issue provides an agreed scope and amount, but a contributor can also start through normal project collaboration. Ask the maintainer whether and how the contribution will be paid before assuming an accepted change earns a payment. See Work on an issue.
What is the difference between a bounty and a Payment Request?
A bounty starts with a project funding an issue. A Payment Request starts with someone asking a customer to pay for delivered work. Both can result in a transfer and payout, but they have different approval paths. See Fund an issue and Charge customers.
Can a client pay without GitHub?
Yes. A customer can open the provider’s Payment Request link, review the request, and pay through checkout. The provider and client should agree on scope and amount before the link is sent.
When does the provider receive money?
Payment, transfer credit, and payout are separate stages. Processing and payout setup can affect timing. Read Payments, Claims, and Payouts.
Can teams and organizations use Gitpay?
Yes. A team can fund project issues or pay a professional’s Payment Request. Agree internally who controls funding, who accepts delivery, and which account receives the funds. These are coordination steps; the docs do not assume a dedicated organization billing feature.
What if work or payment is disputed?
Keep the issue, Pull Request, delivery, and approval records. Read Disputes and refunds for the documented payment effects and contact support for a specific transaction.
