Written by Table of contents
- Before you create a request
- Create and send a Payment Request
- What the customer does
- After payment
- If something goes wrong
- Working as a team
- Next steps
Payment Requests let a service provider ask a customer to pay for delivered work. They work for services outside a GitHub repository as well as work supported by an issue, Pull Request, or other delivery record.
Before you create a request
Agree with the customer on the deliverable, price, currency, and who can approve it. Keep the acceptance record and a link to the result. Gitpay handles the payment request; it does not replace the agreement about what was delivered.
For example, after a developer delivers a reviewed feature, they can create a request describing that milestone and share its payment link with the client.
Create and send a Payment Request
- Sign in and open Payment Requests.
- Create a request with a clear title, description, and amount. Describe the completed work in plain language.
- Check the request before sharing its link with the customer.
- Send the link to the person responsible for paying and include the delivery or approval reference in your message.
Avoid sensitive customer data in a description or public link. If the price or scope is disputed, resolve it with the customer before asking them to pay.
What the customer does
The customer opens the link, reviews the request, and completes the available checkout. They do not need to participate in a GitHub issue or Pull Request. See the client guide for the questions to settle before payment.
After payment
Track the request and resulting transfer in your account. A paid request and a completed payout are different stages: processing and your configured payout method affect when funds arrive. See Payments, Claims, and Payouts.
If something goes wrong
If the customer cannot recognize the charge, share the delivery record and request details. For a refund or card dispute, read Disputes and refunds before making assumptions about your balance. Gitpay’s documented interface supports full refunds; agree any other adjustment with support.
Working as a team
A team can use the same delivery discipline: identify who approves the work, who creates the request, and which account receives payment. Confirm account ownership and payout setup before sharing a request.
