Article

Stripe Payment Links for workshop payments

For solo US tutors, set up a shared workshop checkout, calculate card fees and keep payment records separate from your attendee list.

Editorial illustration for Stripe Payment Links for workshop payments: a document represents the research briefing. Not documentary evidence.

Keep your existing payment-and-attendance routine if it works reliably. For a solo US tutor who needs a shared checkout, Stripe Payment Links can collect workshop payments without building a website; as of 21 November 2026, it is included in standard Payments pricing with no monthly Payments fee, but processing charges apply. You still need to match successful payments to the people attending.

Consider one nontechnical adult craft tutor, already using email and Google Sheets, selling 12 places at US$50 each for one fixed-date adult workshop. The budget for additional monthly software subscriptions is US$0. These are illustrative planning assumptions, not a customer case or evidence of demand. Existing tools, materials, premises and labour still cost money.

The proposed setup uses immediate-confirmation payments and a manually maintained attendee list. It needs no AI subscription or custom integration, and it is not a complete booking system.

Choose by the collection problem: whether everyone buys the same offer, whether each purchase represents one place, how you confirm payment, who maintains attendance, and the total fees and setup work. A link is useful when repeatedly arranging payment is the difficulty; it will not resolve an unattended spreadsheet.

Stripe distinguishes reusable Payment Links from customer-specific invoices: anyone holding a Payment Link can use it, while an invoice addresses a particular customer and is not reusable. The alternatives below are three ways to collect payment, not three products to buy together.

Option

Best fit

Charges for this example

Work and limits

Existing email and spreadsheet routine

Collection and attendance checks already work

$0 new software subscription; existing payment-method fees vary

Keep the current process; check payments, attendees and cancellations yourself.

Stripe Payment Links

One fixed-price offer shared with several buyers

$0 monthly standard Payments fee; $21 illustrative card processing

Configure one checkout; reconcile payments and attendees manually. The use cap is not an attendee list.

Stripe Invoicing Starter

Named customers need individual bills

0.4% per paid invoice plus processing; $23.40 illustrative total

Prepare customer-specific invoices; attendance still needs a separate record.

The invoicing row uses US Invoicing Starter pricing checked on 21 November 2026: $600 × 0.4% = $2.40, added to the $21 card-processing example below. For individual bills and unpaid-balance follow-up, see the Zoho Invoice and Stripe payment-reminder guide.

What would twelve $50 payments cost?

On 21 November 2026, Stripe’s standard US domestic online-card rate is 2.9% plus US$0.30 per successful transaction. Assuming twelve separate successful $50 payments:

  • Gross receipts: 12 × $50 = $600.

  • Processing per payment: ($50 × 2.9%) + $0.30 = $1.75.

  • Total processing: 12 × $1.75 = $21.

  • Amount after processing: $600 − $21 = $579, before every other cost.

This is a calculation, not profit or a guaranteed bill. It excludes international cards, currency conversion, taxes, refunds, disputes, optional services and custom rates. Taxes applicable to your workshop or fees are not established by this example.

Two optional Payment Links additions have separate prices: a custom domain costs US$10 monthly, and post-payment invoices cost 0.4% of the transaction, capped at US$2 per invoice. Neither is needed for this baseline. Enabling those invoices for all twelve $50 purchases would add $2.40. They are different from ordinary payment receipts; their cap does not apply to standalone Invoicing Starter.

Nor is $579 necessarily available to spend on materials immediately. Stripe separates successful payments from bank payouts; its initial payout typically completes within 7–14 days, depending on the business and account circumstances. Check your account’s expected deposit date before committing that cash.

What should buyers know before paying?

First confirm that your business can accept live payments. Stripe requires business verification and service activation; access to a sandbox is not live approval. Review your customer-facing business name, support details and statement descriptor—the text identifying the charge on a card statement—because customers can see business information on statements or receipts.

Prepare one clear workshop description covering:

  • The exact date, start and finish times, time zone and location.

  • What the session includes, any materials the attendee must bring, and the USD price.

  • That one purchase buys one place, plus how to contact you if the payer will not be the attendee.

  • Your contact route, cancellation and refund arrangements, and what happens if you cancel the workshop.

Stripe’s business-presentation checklist calls for clear descriptions, currency, contact details and applicable policies. Put this information where buyers can read it before paying. That does not mean this workflow requires a separate paid storefront.

If people need to ask questions before buying, keep that intake separate. The Tally, Typeform and Google Forms enquiry guide covers that task; a submitted enquiry is neither payment evidence nor a reserved place.

How do you create a one-place checkout?

Start in a sandbox for the rehearsal below. Stripe’s Dashboard creation instructions use Payment Links, then +New, followed by selecting or adding a product. For this example:

  1. Add one workshop product with a one-time US$50 price. Do not choose recurring billing or a buyer-selected amount.

  2. Set the item quantity to one and leave Let customers adjust quantity off. Keep extra items and discounts out of this simple setup.

  3. Use one link. Select Limit the number of payments and enter 12. Review the message shown when sales have closed.

  4. Enable native customer-name collection for individuals. Leave it required; do not create a custom name field. Stripe warns against putting personal or sensitive information in custom fields.

  5. Review the remaining payment and message settings, then create the link.

The important unit is a completed Checkout Session: Stripe’s restriction counts completed sessions, not attendees, item quantities or money deposited in your bank. Stripe says the link automatically deactivates when its configured limit is reached.

Using quantity one makes one purchase represent one place in this proposed design. It does not establish one purchase per person: someone could buy twice, or pay for another attendee. Treat the cap as a checkout control, not a promise of twelve unique attendees or a tested guarantee against overselling during simultaneous checkouts.

Do not assume several links share an inventory count, or that refunding a purchase restores an available use. Those behaviours are not established here. Keep the same link across your sales channels.

Which payment methods and messages fit a dated event?

Use methods that confirm success immediately for this manual workflow. Stripe says some bank debits and vouchers can take 2–14 days to confirm. Its fulfillment guidance allows manual handling for low-volume ventures but requires automated payment-event handling, called webhooks, for methods with delayed success notifications. Those methods therefore fall outside this no-integration setup.

Review the methods actually offered in your Dashboard. Stripe’s payment-method settings can affect more than this workshop; do not assume a per-link, card-only switch exists in your no-code interface or alter unrelated checkouts inadvertently. Payment Links can also display local currencies, so the domestic-USD cost example is not an international quote.

Enable owner notifications for successful payments in your personal notification preferences. Customer receipts are a separate setting: under Settings → Business → Customer emails → Payments, turn on Successful payments and check that a recipient email and required public contact details are available. Stripe does not automatically email every receipt it creates. Leave optional invoice creation off unless you need and have budgeted for it.

Use the post-checkout message to explain the next step. For example: “We will check your payment and email your workshop confirmation. Contact us if someone else will attend.” Only promise a response time you can meet. A checkout message should not claim that a ticket has been issued or money has reached your bank.

Use dummy customer details and Stripe’s official sandbox test values, not real card details. Sandbox transactions simulate payments without moving money. The following are checks for you to perform:

  • Confirm the workshop, USD amount, quantity one, required name and contact information, and cancellation wording.

  • Simulate a successful payment and a declined one; make sure only the successful payment reaches a confirmed dummy attendance record.

  • Walk through a repeated purchase and a payer who differs from the attendee. Decide how you would investigate each before confirming another place.

  • Inspect the completion message, manually send a test receipt if needed, and check deactivation and the closed-sales message.

Stripe says test payments do not trigger automatic receipt emails. A sandbox rehearsal also cannot establish live payout timing, actual fees, guaranteed email delivery or capacity under load.

Before public sharing, review the separate live configuration and approve it yourself: live account, product, price, quantity, cap, methods and customer information. Then share the same live link through your existing email or other channels. This is an owner review step, not a built-in Stripe approval feature.

How do you keep the attendee list accurate?

Treat checkout, payment review and attendee list as three separate steps. Check the individual payment in the Stripe Dashboard before confirming attendance. Do not use aggregate link analytics as a live list: Stripe says those metrics can lag by up to 18 hours and are unavailable in sandbox.

A useful operating convention is one restricted spreadsheet row per proposed attendee, with only the information needed to run the workshop:

  • Attendee name and necessary contact details; note a different payer only when needed to match the purchase.

  • Payment reference, amount and reviewed payment status.

  • A separate attendance decision, such as awaiting review, confirmed or cancelled.

  • Any cancellation or refund decision, whether the refund is requested or completed, and when you checked it.

For each proposed attendee, match the payment reference and successful status, resolve duplicate purchases or identity differences, then send the attendance confirmation. A pending payment must not become confirmed attendance merely because someone reached the checkout-completion page. A successful charge can also be refunded or disputed later.

These status labels are your record-keeping convention, not an enforced Stripe approval process. Keep card numbers and security codes out of the sheet. In Google Drive, use Restricted sharing and appropriate access roles, and check the parent folder: files inherit its permissions. Do not share the roster with all buyers.

Stripe documents payment CSV exports with selectable columns. Keep necessary payment records alongside the roster, inspect the columns before relying on a match, and set a retention period appropriate to your obligations. A payment export is not a complete attendance backup or a verified migration to another system. Automatic spreadsheet updates and tickets would require a separately assessed integration.

How do you close sales and handle cancellations?

Close sales when your cutoff arrives, even if fewer than twelve purchases were made. Open the link’s overflow menu and choose Deactivate. This prevents further purchases; it does not delete the link, cancel attendance records or refund customers.

For a cancellation, review your stated arrangement, identify the exact payment and approve the refund amount. Stripe says original processing fees are not returned. Refunds draw on available balance; insufficient funds can leave a card refund pending. Record the request and completed refund separately rather than telling the customer reimbursement has finished when it has not.

Decide separately whether the place can be offered again. Do not automatically raise the cap or create another link after a refund: first reconcile the remaining attendees and payment records. If the workshop needs group purchases, automatic waitlists or coordinated capacity across several channels, choose a workflow with those capabilities verified before taking payments.

For a small, single-date session, the practical choice is narrower: retain a dependable existing routine, or add a shared checkout while keeping payment checks and the attendee list firmly assigned to the owner.