Written by The problem: Open Source Maintainers chasing payments
Even after the work is delivered, payment can stall because the next step is unclear (invoice, approvals, finance queue, international transfer, etc.). The result is the same: you spend time following up instead of doing more billable work.
Why traditional invoicing slows you down
- Invoices look like paperwork, not an action
- Clients need internal approvals (and your invoice gets stuck)
- International clients add extra steps and fees
- Small projects shouldn’t require heavy accounting setup
A simpler workflow: payment requests
- Finish the work
- Create a payment request
- Send the link
- Client pays
Example workflow (copy/paste)
Delivered the agreed milestone and shared the handoff notes. You can pay using this payment link: (Gitpay payment request link). Thanks!
Example use cases for Open Source Maintainers
- Sponsorship / recurring support
- Paid support contract
- Security fix / patch bounty
- Priority issue resolution
Using Gitpay
Gitpay helps service providers create payment requests, share payment links, and receive payments online:
- https://gitpay.me
CTA
Finish the work. Send a payment link. Get paid: https://gitpay.me
