GitPay

Invoice from shipped GitHub work

Invoice clients from merged pull requests.

Install GitPay on selected repositories. Read-only PR metadata. No source code access. Send a client-ready invoice — card, PayPal, or bank transfer.

GitHub App · Selected repositories · Read-only PR metadata · No code access

See sample invoice

GitHub App · Selected repositories · Read-only PR metadata · No code access

Installing the GitHub App is usually smoother on desktop. On mobile, use See sample invoice first — then continue on a larger screen when you are ready to import PRs.

What clients see

Static preview — open the live demo anytime without installing the GitHub App.

Invoice from Alex Developer

Awaiting payment

Invoice #123

April 2026

Billed to

Jordan Lee · Brightline Labs

finance@brightline.example

Development work

This invoice covers completed work from April 2026, focused on outcomes that move your business forward. Details below summarize what was delivered; expanded technical references are available if needed.

  • Payment system improvements

    $300.00

    Includes 3 completed changes

  • Improved reliability — Bug fixes and stability updates

    $120.00

    Includes 2 completed changes

Total to pay

$420.00

USD

Secure card payments

Processed securely via Stripe or PayPal

Other ways to pay

Pay $420.00 with PayPal

Pay with PayPal

You'll complete payment securely on PayPal

Pay by bank transfer
Expand on the live invoice for wiring details and reference.

Sample only — your clients use the live payment page from their invoice link.

  • Work verified via GitHub PR metadata
  • Secure payment
  • No GitHub account required
Try demo invoice

How it works

  1. 1

    Install on selected repositories

    Choose only the repositories you invoice from.

  2. 2

    Import merged PRs

    Titles, dates, and links — read-only metadata, not your code.

  3. 3

    Send and get paid

    Clients pay from your link — card, PayPal, or bank transfer.

GitHub App trust

Install GitPay on selected repositories. We use read-only pull request metadata to build line items — no cloning, no write access, no training on your code.

  • You choose which repositories — not blanket org access
  • Metadata only (titles, dates, links) — not source code
  • No repository cloning, no write permissions
  • Revoke access anytime from GitHub settings

Pricing

$0 for 30 days
$9/month after trial

$0

30 days

After trial

$9/month

Free for 30 days. Then $9/month.

  • Unlimited invoices
  • Invoice lines from shipped work
  • Flexible client payments — card, PayPal, or bank transfer
  • Payment tracking
  • CSV export for accountant/tax prep
  • All current features included

No credit card required to start.

No per-invoice GitPay fee.

Stripe processing fees may apply.

GitHub App · Selected repositories · Read-only PR metadata · No code access

GitHub App · Selected repositories · Read-only PR metadata · No code access

See sample invoice

Frequently asked questions

What payment methods can my client use?

Your client can pay by card, PayPal, or bank transfer.

Do I need Stripe to use GitPay?

No. Stripe is optional. You can accept payments via PayPal or bank transfer without connecting Stripe.

What does my client see?

A clean, simple invoice with clear descriptions and easy payment options.

Can I edit the invoice?

Yes. You can edit anything before sending.

Do I need GitHub?

GitPay works best when you import merged PRs from repos you choose. You can still build invoices manually without importing.

Is this secure?

Yes. Payments are processed securely; GitPay never stores card details.

Can I use this without technical knowledge?

Yes. Your client sees a simple, non-technical invoice.

Ready to bill what you shipped?

GitHub App · Selected repositories · Read-only PR metadata · No code access

See sample invoice

30 days free · No credit card required

Invoice clients from merged GitHub PRs | GitPay