Written by Introduction
Course creation is a mix of product and service.
You might sell a self-serve course, but you also end up doing “service-like” deliverables: onboarding calls, portfolio reviews, community access, 1:1 audits, template packs, and custom feedback.
That hybrid model is where payment gets messy. Some buyers want checkout-style payment. Others ask for invoices. If you’re not careful, you end up maintaining three payment workflows for the same business.
A payment request keeps things simple: you deliver the digital work or service, send a link, and the buyer pays.
The Typical Workflow Problem
Common course creator payment patterns look like:
- Sell access via a platform
- Handle custom requests manually
- Send an invoice for anything outside the platform
- Wait
- Follow up
Where friction happens:
- Buyers want “a link” and you send a PDF.
- International buyers struggle with bank transfers and fees.
- Custom add-ons fall into a slow invoice workflow.
- You lose focus because you’re doing billing admin.
It’s why course creators search “get paid online freelance” even though they’re not “freelancers” in the traditional sense.
The “platform vs custom work” split
Platforms are great for self-serve access, but they often don’t cover:
- Customized feedback
- Private calls
- Corporate team purchases
- One-off add-ons
When those requests come in, you need a payment flow that’s as simple as your course checkout—without rebuilding your entire stack.
Payment Requests (Instead of Invoices)
Payment requests are useful whenever the work is digital and the buyer wants speed.
Instead of invoices, you:
- Create a payment request for the deliverable
- Send a link
- Buyer pays
- You grant access / deliver the output
That link is a freelancer payment link in spirit: one clear action that closes the loop.
Good moments to use a payment request
Payment requests work well for:
- Portfolio reviews
- Resume/CV reviews
- 1:1 coaching sessions
- Custom template packs
- Private community access
- “Done-with-you” onboarding
Each of these can be described in a few words, which makes it easy to request payment from client (or buyer) without complex tooling.
How to position it so it doesn’t feel awkward
Treat the payment request like a normal checkout step, not a negotiation:
If you’d like the portfolio review, here’s the payment link. Once it’s paid, send me your portfolio link and we’ll schedule.
Clear, direct, and respectful.
Scheduling and rescheduling (a common payment leak)
For calls and reviews, payment gets delayed when scheduling drags.
Two simple rules:
- If it’s a one-off session, ask for payment before you book the time.
- If it’s a deliverable after the session (notes, review), send the payment request link with the final notes.
This keeps the payment step tied to a clear moment: booking or delivery.
Gitpay Payment Requests (Natural Fit)
Gitpay helps creators generate payment requests they can share as a simple link.
- Gitpay homepage: https://gitpay.me
- Gitpay payment requests (service payments): https://gitpay.me/#/use-cases/service-payments
Use it as your “manual checkout” when you don’t want to force everything through a single platform.
Example Use Cases
1) Paid portfolio review
Deliverable: “30-minute review + written notes + next steps.”
Workflow:
- Ask for the portfolio link
- Schedule the call
- After delivery, send notes + payment request link
2) Course onboarding package
Deliverable: “Onboarding call + personalized study plan.”
This is a clean way to charge clients online for higher-touch upgrades.
3) Selling a digital template pack
If you sell a pack directly, a payment request can be used to close the sale in DMs.
4) Community access sponsorship
If a company wants to sponsor seats for their team, payment requests can be easier than setting up an invoicing system for one-off purchases.
5) Corporate buyers who need internal approval
If the buyer needs a manager to approve it, make your payment request easy to forward:
- Label it with the deliverable
- Include dates (“April cohort onboarding”) if relevant
- Keep the description short
Why This Workflow Is Simpler
Payment requests reduce tool sprawl for course creators:
- No complex invoicing software for each custom request
- Faster payments because buyers can pay instantly
- Good for international buyers who need a simple online flow
- Works for digital deliverables like feedback, templates, and access
- Keeps your business focused on teaching, not billing admin
One-minute checklist for higher-touch upgrades
Before you send a payment request for coaching/reviews, include:
- What the buyer gets (deliverable)
- Delivery timing (“within 72 hours”)
- What you need from them (portfolio link, questions, etc.)
- The payment request link
This keeps expectations clear and avoids “paid but unclear” situations.
A practical message template
Send something like:
Your review notes are ready. If you want to close out the portfolio review, here’s the payment link: (payment request link).
Simple, direct, professional.
If someone insists on an invoice
Sometimes a company buyer can only pay against an invoice. Even then, payment requests can still help as the “pay now” step once finance is ready.
The key is not to let payment become a separate multi-week process for a one-hour deliverable.
CTA
If you want a simpler way to sell digital deliverables and get paid quickly, try creating a payment request on Gitpay:
- https://gitpay.me
- https://gitpay.me/#/use-cases/service-payments
