Connect GitHub to get started
We use merged pull request metadata to build invoices. Your repositories are not cloned and your source code is not read.
From merged PR to invoice and payment
Fix authentication bug (#142)
Invoice preview
Client: Acme Inc
Amount: $500
Includes: GitHub work references
Sample layout — not a real invoice
GitHub PRs, then invoice, then paid
Secure GitHub OAuth · Read-only access · No code access
- No source code access
- No write permissions
- No repository cloning
Your code stays private
GitPay only reads pull request metadata needed to create invoices: PR titles, links, dates, authors, and status.
We never clone repositories, read source code, modify files, or request write access.
You'll see the exact permissions GitHub requests on the next screen before you authorize.
What does GitPay access?
GitPay uses GitHub OAuth to read the minimum information needed to create invoices from GitHub work. This may include repository names, pull request titles, pull request URLs, timestamps, authors, and PR status.
GitPay does not read, copy, store, or train on your source code.
You stay in control. You can revoke GitPay access anytime from your GitHub settings.
See pricing · We never store your code