How to send an invoice with a payment link
Follow a simple workflow: build the invoice, email the PDF with a Stripe Checkout path, then track what is paid or overdue. EasyPayRequest keeps those steps in one payment request. This page is the step-by-step send workflow—not a first-ask tone guide, reminder cadence, or email template library. Examples are educational product guidance, not legal or tax advice.
Add client details, line items, tax, payment terms, and a calendar due date. Preview the PDF so the record looks professional before you send. Confirm the billing name and email—not only the project contact. If Stripe is not connected yet, connect it before you promise a pay-now path; a beautiful PDF with a broken Checkout link is still a failed send.
Send the invoice PDF with a clear Stripe payment link in the same message. State the amount and due date near the link in the body—do not hide the ask only inside the PDF. Use one invoice number in the subject so AP can search later. For first-ask wording details, use the client payment request email guide; this step is about the send workflow itself.
Use paid, due, and overdue context—and reminders when needed—so you are not digging through old threads to see what is open. When you follow up, reply in the same thread and resend from the same invoice record rather than pasting an old Checkout URL from a prior email. Reminder cadence and overdue tone live on their sibling guides.
Open the PDF and confirm the client name, invoice number, line items, tax, and calendar due date. Click the Stripe pay-now path yourself in a private window so you catch expired Checkout sessions or a disconnected Stripe account before the client does. If the email client strips links, keep the amount due and “Pay now” wording in the body—not only inside the PDF.
Subject: “Invoice INV-1042 for Website redesign — $2,400 due June 30.” Body: “Hi Jordan — attached is invoice INV-1042 for the website redesign milestone ($2,400, due June 30). You can review the PDF and pay by card here: [pay-now link]. Reply if the billing contact or PO needs to change.” Keep one ask, one link, one due date. Expand tone variants on the first-ask and template pages.
Draft line items and due date → preview PDF → verify Stripe pay-now opens the matching amount → send to the billing email → watch status on the invoice record → if unpaid near due, use the reminder guide. Do not skip preview: most “wrong amount” complaints start as an unchecked PDF or a stale link from a previous invoice.
Client wants ACH instead of card: still send the invoice PDF with clear remittance instructions and keep status on the same record if you track externally. Multiple stakeholders: CC AP, keep the project lead informed, but put one primary To: address. Revised invoice after a scope change: update the record and resend a new pay-now path—do not leave two live links for different totals.
Wrong recipient (billing vs project contact), missing due date (“Net 30” with no calendar date), pay-now link that opens a different amount than the PDF, follow-ups that start a new thread without the invoice number, and sending before Stripe is connected. Fix those before you escalate tone. For reminder wording after send, use the invoice reminder and overdue email guides.
Use this page for the ordered send workflow. Use client payment request email for first-ask tone. Use invoice reminder email for before/after-due cadence. Use the Stripe invoice payment link page for how Checkout and invoice context fit together. Use the payment link generator to preview wording before you create a real request.
Preview wording and move from mock link to a real request.
Open resourceSee how invoice context and Checkout fit together.
Open resourceWrite the first email that carries the invoice and link.
Open resourcePlan polite follow-up after the first send.
Open resourceApply the same send workflow to progress billing phases.
Open resourceReview the full payment-request workflow.
Open resourceNo. The workflow is designed around the invoice email plus a Stripe Checkout link, not a custom payment site you maintain.
Yes. EasyPayRequest centers the polished PDF so the payment link is not a bare URL without context.
Resend from the same invoice record after confirming Stripe is connected and the Checkout session matches the current balance. Avoid pasting an old link from a prior email.
Prefer email (or your normal billing channel) with the PDF and invoice number so AP has a searchable record. A bare link in chat is easy to lose and hard to reconcile.
Stripe charges standard card processing fees on paid invoices. Those go to Stripe, not as a markup from EasyPayRequest.
No. The steps cover how to send an invoice with a payment link. Confirm tax, terms, and compliance for your location and client type.
Yes. Create a free account for core invoices and payment requests, then upgrade for fuller reminders and automation.
Start free, create a professional invoice, and include a Stripe payment link so clients know exactly how to pay.
Start for free