---
title: Payments
description: Send each project or booking its payment link, set a deposit and installments, record payments made another way, and issue refunds.
section: Core workflows
order: 7
---

# Payments

Each project and each mini-session booking has one payment link. It shows the client what they owe, what they have paid, and what is left, and lets them pay online. There is nothing to build: the link follows the project's amount, add-ons, and tax.

## Before you start

Check these settings first:

- Go to **Settings → Account** to check your currency and **Default tax rate (%)**. Your currency is set at signup and cannot be changed. Each new project takes the default tax rate when it is created and keeps it, so changing the default later does not change existing projects.
- Go to **Settings → Payments** to connect Stripe if clients should pay online. You can also continue incomplete Stripe setup, refresh its status, and open the Stripe Dashboard after connection.
- Payment reminders are on by default. Change their timing in **Settings → Reminders**.

Only teammates with billing access can manage Stripe and payment reminders. Manage payouts, disputes, and Stripe account details in the Stripe Dashboard.

You can also record cash, bank transfers, and other payments received outside LYGHTBOX.

## Open Payments

Open a project and select the **Payment** step in **Progress** to open **Payments**. For a mini-session booking, open the booking's details and choose **Payments**.

**Payments** shows the total, how much has been paid, and the amount remaining, along with the payment link and the payments received. Use **Record payment** for money received another way.

If the project has no package or amount yet, choose **Set up** on the **Payment** step. **Record payment** needs a total above zero.

Each project uses one tax rate. Turn off **Charge tax** on the **Package & add-ons** tab for a tax-exempt job. Turning it back on uses your current default rate.

For work that does not need payment, turn off **Payment required**. The project can be booked without a payment, and its payment link shows **No payment required**: the client cannot pay through it, you cannot send or copy it or record a payment, and its reminders stop. You cannot turn off **Payment required** while the project has payments, including one still processing. When you turn it back on, emails and reminders that came due while it was off are skipped.

## What's on the payment link

The link's charges come from the project: its amount (named after the package), each add-on, and tax. For a mini-session booking, they are each session's amount, its add-ons, and tax. Sessions booked back to back count as one booking, with one link.

A booking from a booking page or proposal lists what the client chose: the package or session, each add-on, and any discount, such as **Discount (SAVE10)**. If you change a project's amount, the link shows the new amount on one line, with add-ons sold after booking still on their own.

When you change the amount, add or remove an add-on, or turn tax on or off, the link updates itself. If this happens after the client has the link, they see when it was last updated.

Every payment counts toward the link: card payments made through it, payments made at checkout on a booking page, and payments you record yourself. The link always asks for what is left.

With a deposit, the client pays the deposit, plus tax, when they book. The rest of the package and the add-ons, less any discount, are left on the link. If the total is less than the deposit, they pay the total when they book.

## Send or copy the link

- **Send** emails the client a link to pay what is due now. Check the recipient and subject, and add a message if you like. When nothing is due, copy the link instead.
- **Copy link** copies it so you can share it yourself, for example in a message.

The client can open and pay the link once you have sent or copied it. Opening **Payments** yourself does not share it. You can still share a link that is paid in full, so the client can see their payments.

## Set a payment schedule

Without a schedule, the link asks for the full amount by one due date. To collect it over time, choose **Edit schedule**:

1. Add a **Deposit** if needed. Enter an amount or a percentage of the current total.
2. Add more payments with **Payment**, each with an amount and a due date. They appear as **Payment 1**, **Payment 2**, and so on.
3. Choose when the balance is due: 14 or 30 days before the event date, a custom date, or no due date.
4. Select **Save schedule**.

The **Balance** is whatever is left after the deposit and payments. A percentage becomes a fixed amount when you save, and so does a date counted back from the event. A balance due date set by a booking page moves when the session date changes.

Payments fill the schedule in order, deposit first, however they were made. A bank transfer you record counts the same as a card payment.

- **When the total changes**, the balance changes with it. If the total drops below the deposit and installments, the latest unpaid ones shrink first.
- **Unpaid payments** can be changed at any time. Payments that are already covered stay as they are.
- **Something new after Paid in full**, such as an album added after the wedding, appears as an **Additional amount**, due straight away.

## What the client sees

The payment link shows the client:

- The charges and what is left to pay.
- Payments received, with their method and date. Your notes are never shown.
- The schedule, with what is due now.
- Buttons to pay the amount due now or everything that is left.

Clients can pay with any payment method your Stripe account allows. A bank payment can take a few days to clear. Until it does, the link shows **Payment processing**.

The payment link also appears in the client's [portal](/docs/client-portal) for the project or booking.

## Understand payment link status

- **Not sent** - you have not sent or copied the link yet. The client cannot open it.
- **Sent** - the client has the link and nothing has been paid yet.
- **Partially paid** - some money has been paid, with more still due.
- **Overdue** - a payment has passed its due date.
- **Paid in full** - nothing is left to pay. Reminders stop.
- **Closed** - you closed the link. The client cannot pay it.

If something is owed again after **Paid in full**, the status returns to **Sent**, **Partially paid**, or **Overdue**. The client keeps the same link.

## Close or reopen the link

Close the link when you no longer want to collect through it. The client cannot pay it, and its emails and reminders stop. If the client had already submitted a payment, it can still go through. LYGHTBOX keeps it and the link stays closed.

Choose **Close payment link** from the payment link's menu. To collect again, choose **Reopen payment link** from the same menu, or send or copy the link. The address stays the same.

## Record payments and refunds

In **Payments**, select **Record payment** to add a cash, bank transfer, or other payment. Enter the amount, payment date, method, and an optional note. The payment uses your account currency and counts toward the payment link.

For mini sessions booked back to back, a recorded payment goes to the whole booking. You can edit or delete the payments you recorded.

When the payments cover everything, the link shows **Paid in full** and its reminders stop. There is nothing else to cancel.

To refund a card payment made through the link, choose **Refund card payment** from the payment link's menu. A card payment on a past invoice has its own **Refund** button. For a payment made on a booking page, use **Refund checkout payment** on the **Package & add-ons** tab. Choose **Full refund** or **Partial refund**, select a reason, and optionally add an internal note. The dialog shows how much you can refund.

Refunds return money to the original payment method and reduce what has been paid, so the link asks for that amount again. A closed link stays closed. Online payments cannot be edited like the payments you record yourself.

If the total drops below what has been paid, **Payments** shows the project as overpaid. Only you see this, and nothing is refunded automatically.

## Payment reminders

Payment reminders are on by default. LYGHTBOX emails the client 3 days before each payment is due and 3 and 7 days after, until it is paid. To change the timing or turn them off, go to **Settings → Reminders**, edit **Payment reminders**, and select **Save changes**.

Reminders start once you send or copy the link, and each one asks for the amount due at the time. Changing a payment's amount or date does not send its reminders again. Reminders stop when the link is paid in full or closed, and while the project is archived or marked lost. If you restore the project, the emails and reminders still to come go out; any that came due meanwhile are skipped.

The **Before due** reminders also go to a client whose [request you've accepted](/docs/proposals#reminders-before-book-by), that many days before its **Book by** date, until they book.

Once the client has the link, LYGHTBOX also emails it when each later payment comes due. **Payments** shows the next scheduled email, and you can send it now or cancel it.

When a client pays a deposit on a booking page that collects the remaining balance 1 or 7 days before the session, LYGHTBOX emails them the payment link on that day. If they book after that day, the balance is due the day they book, and the link goes out with their confirmation.

As payments come in, LYGHTBOX updates the payment link, the project's balance, and its **Payment** step.

## Past invoices

Invoices created before payment links stay on their project or booking as a record. You and your client can still open them, but they cannot be edited, sent, or paid. Payments made on them count toward what the client has paid.

## Related guides

- Follow each job in [projects](/docs/projects).
- Require payment on [booking pages](/docs/bookings).
- Set up the packages and add-ons you charge for in [services and pricing](/docs/services).
