> ## Documentation Index
> Fetch the complete documentation index at: https://docs.shootbin.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Collect client payments before photo delivery

> Require payment before clients can view projects or download delivery files. Track payment status manually.

Client payments let you require that your client has paid before they can view a project or download their delivery. You control whether the requirement applies to viewing, downloading, or both,and you can mark a project as paid yourself for payments made outside the platform, such as bank transfers or cash.

Client payments are available on the **Beta**, **Studio**, and **Agency** plans.

## Payment requirements

Shootbin supports two independent payment requirements you can enable per project:

<CardGroup cols={2}>
  <Card title="View requirement" icon="eye">
    The client must pay before they can open the project and view any photos. Use this when access itself is contingent on payment.
  </Card>

  <Card title="Download requirement" icon="download">
    The client must pay before they can download the delivery package. Use this to release finals only after receiving funds.
  </Card>
</CardGroup>

You can enable either requirement, both, or neither on each project.

## Set up payment requirements

<Steps>
  <Step title="Open the project payments page">
    Inside a project, click **Payments** in the project sidebar.
  </Step>

  <Step title="Enable payment requirements">
    In the requirements panel, check one or both options:

    * **Require payment before viewing**
    * **Require payment before downloading delivery**
  </Step>

  <Step title="Add payment instructions (optional)">
    Use the payment instructions field to tell your client how to pay,for example, your bank account details, PayPal address, or a payment link. These instructions appear on the client's payment status page inside the project.
  </Step>

  <Step title="Save settings">
    Click **Save settings**. The requirement becomes active immediately. Any client who visits the project will now see the payment prompt for whichever restrictions you've enabled.
  </Step>
</Steps>

<Warning>
  Enabling the view requirement will block clients from accessing the project until payment is marked as received. Enable this only when you're ready to ask for payment.
</Warning>

## Mark a project as paid

When a client pays outside the platform,via bank transfer, cash, or any other method,you can manually mark the project as paid.

<Steps>
  <Step title="Open the project payments page">
    Navigate to **Payments** inside the project.
  </Step>

  <Step title="Mark payment as received">
    Click **Mark payment received**. The project immediately shows as paid and any active payment requirements are lifted for the client.
  </Step>
</Steps>

<Tip>
  You can also reset the payment status if needed,for example, if you marked it as paid by mistake. Click **Reset payment** on the same page.
</Tip>

## What the client sees

When a client reaches a payment page, they land on a page that explains payment is required before they can proceed. The page shows:

* Which access is restricted (viewing or downloading)
* Any payment instructions you've added
* Their current payment status

If the client visits their project payment status page directly, they can see whether payment is required, pending, or received,keeping them informed without needing to contact you.

<Tabs>
  <Tab title="Payment required">
    The client sees a prompt explaining that payment is required. Your payment instructions are shown so they know how to pay.
  </Tab>

  <Tab title="Payment pending">
    After the client indicates they've paid (or you're waiting on confirmation), the status shows as pending while you verify and mark it received.
  </Tab>

  <Tab title="Payment received">
    Once you mark the project as paid, the requirement is lifted and the client has full access to what they've paid for.
  </Tab>
</Tabs>

## Payment settings summary

| Setting                            | What it does                                                     |
| ---------------------------------- | ---------------------------------------------------------------- |
| Require payment before viewing     | Blocks project access until payment is received                  |
| Require payment before downloading | Blocks delivery download until payment is received               |
| Payment instructions               | Free-text field shown to the client on their payment status page |
| Mark as received                   | Manually lifts all payment requirements for the project          |
| Reset payment                      | Reverts the project back to unpaid status                        |