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

# 9Pic Checkout

> Sell event photos with integrated payments, packages, coupons, and order tracking.

> [!WARNING]
>
> 9Pic Checkout is a **Business plan** feature. It is locked on Pay As You Go and Pro, where the lock offers **Upgrade to Business**. If it's still locked after upgrading, email [support@9pic.ai](mailto:support@9pic.ai).

> [!NOTE]
>
> **On Trial, Checkout runs in test mode.** You can set it up and run purchases using the 9Pic test payment account, your own Stripe test key (`sk_test_` or `rk_test_`), or **No gateway**. Buyers pay with test cards and are not charged, test orders are left out of revenue, and buyer emails are labelled **\[Test]** and say no payment was taken. Live payment accounts need the Business plan. See [Trial: Photo Sales Run in Test Mode](https://docs.9pic.ai/account/plans/trial.md#photo-sales-run-in-test-mode).

## Overview

9Pic Checkout lets participants buy event photos and eligible Motion clips directly from the event page. Open **9Pic Checkout** in your event's product navigation.

The product has four tabs:

| Tab | What it covers |
| - | - |
| **Overview** | Setup progress, quick status, and links into configuration |
| **Configuration** | One card with a section menu: Payments (gateways, tax, buyer support), Packages, Buyer options, Video clips, and Purchase webhook |
| **Coupons** | Discount codes buyers apply at checkout |
| **Transactions** | Revenue summary, order list, and CSV export |

> [!WARNING]
>
> **Store Original Photos is required.** Buyers need the original files after payment, so the event must have **Store Original Photos** enabled before Checkout will open. Set this when [creating the event](https://docs.9pic.ai/products/events/create.md) (a Business plan option). Until it's on, Checkout shows a notice that original photos must be stored first.

## Checkout Setup

A status bar at the top of **Overview** (and the **Checkout Configuration** card header) says what is left, for example **Checkout is off. 2 steps left before buyers can pay.** Its button is always the next thing to do: **Assign gateway**, **Add support contact** or **Set up a package**, then **Turn on checkout** once everything is ready. While checkout is on, the button is **Turn off checkout**.

If a payment gateway needs attention, the status bar says so instead of claiming buyers can pay, for example **Checkout is on, but a payment gateway needs attention: buyers may not be able to pay.**, and offers **Review gateway**. See [A gateway that needs attention](#a-gateway-that-needs-attention).

The first time you open Overview, a **How selling photos and clips works** card explains the buyer journey in four steps. While a setup step is left, **Get started** opens it. **Got it** (or the close button) hides the card. To see it again, select **How checkout works** in the status bar. The card is hidden once checkout is set up and on, and your choice to hide it is remembered in that browser only.

The **Set up checkout** checklist (called **Checkout requirements** once checkout is on) lists four steps with a count such as **2 of 4 complete**. Each row's button opens that step right where you need it:

**1. Payment gateway**

**Assign gateway** (or **Change gateway**) opens the gateway dialog on the Configuration tab. Choose a **Stripe**, **Xendit**, **PayMongo**, **AFS**, **BENEFIT** or **No gateway** configuration from your organisation's [Payment Configuration](https://docs.9pic.ai/account/payment-gateways.md) and save it. If your organisation has exactly one supported configuration, the Payment gateways card names it and offers **Use this gateway**, which opens the same dialog with it selected; nothing is assigned until you confirm. An assigned gateway that cannot take checkout payments, or that needs attention, does not count as complete.

**2. Buyer support contact**

**Add support contact** opens the support dialog. Add a support email, a phone or WhatsApp number, or both, so buyers can reach you about an order. Support instructions alone do not complete this step. Buyers see these details at checkout and in their purchase details.

**3. Published package**

**Set up a package** opens the package builder. A package sets what buyers can buy and what it costs, for a **pre-event** or **post-event** sale. If you already have packages but none is published, the button is **Go to packages** instead.

**4. Turn on checkout**

When the steps above are done, **Turn on checkout** opens a confirmation. Confirm it and checkout goes live straight away; there is no separate save. Until then, the button takes you to the first unfinished step.

The support and package steps need a gateway first, so without one their buttons open the gateway dialog.

### A gateway that needs attention

A gateway needs attention when its payment account refused its saved key while a buyer was paying, or when the last key check found the key refused or missing permissions. While that lasts:

* The payment gateway step isn't complete and says **1 gateway needs attention: buyers may not be able to pay**. Its button, **Review gateway**, opens the **Payments** section of the Configuration tab, where each gateway explains what to fix.
* The status bar no longer says **Checkout is live for buyers.** and offers **Review gateway**.
* You can still turn checkout on; the warning is there so you fix the key first.

Fix the key on the [Payment Configuration](https://docs.9pic.ai/account/payment-gateways.md) page: save a working key, or fix its permissions in your payment account and select **Check key**.

**More ways to sell** groups the optional **Buyer options** and **Video clips**. Buyer options let buyers pick extra photos from the full event library or a curated pool, and enable **search refresh** as later photos upload. On Configuration they save with **Save changes**, together with video clip, tax and webhook settings. See [Buyer photo options](https://docs.9pic.ai/products/checkout/buyer-photo-selection.md). **Payment Gateway** and **Packages** summaries sit beside the checklist.

### Turning checkout on and off

| Action | What happens |
| - | - |
| **Turn on checkout** | Available once a supported gateway, a buyer support contact and a published package are in place. After you confirm, buyers can pay for your published packages straight away. |
| **Turn off checkout** | Shown while checkout is on. After you confirm, packages are hidden from buyers and new payments stop. Orders, packages and settings are kept, and you can turn it back on later. |

> [!WARNING]
>
> **Turn on checkout** takes effect as soon as you confirm. Buyers see every published package for the event that matches the current sale phase and dates, so check your packages first.

## Selling Motion Clips

Video clips are sold through packages: add a **Video clips** price to the **post-event** package in the package builder, or a **clip pass** (the **All items** price) to the **pre-event** package so buyers can pay before the event videos are published. There is no separate on-off switch. **Video clips** appears once **9Pic Motion** is turned on for the event in Event Config. Events created before Event Config had product switches count as having Motion on. Motion doesn't need to be published and no videos need to exist yet, so you can set clip prices before the event. Clips go on sale once Motion is ready:

1. Turn on 9Pic Motion for the event (the checklist links to Event Config).
2. Add a watermark (a logo, or copyright text) on the Motion watermark page. No preview is needed.

No video needs to be processed first: clips go on sale as each video finishes processing.

### Clip pass before the event

A pre-event package can price clips only as an all-clips pass: one price for every clip the buyer appears in. Buyers pre-book it from the event page, even after the photos are live, until you publish the event videos in Motion. Once the videos are published, the buyer opens **Claim clips** on their purchase, searches with their bib or a selfie, and every clip found is theirs; originals download from the purchase page like a post-event clip purchase. Searching again later adds clips from videos processed since. A clip pass never locks other buyers' clips; only a post-event clip package does.

### When buyers' clips are locked

Clips are locked behind the purchase only while checkout is on and a **published** post-event package prices them and its sale hasn't ended. That includes a package that opens later and clips shown as "coming soon".

Pausing that package, leaving it as a draft, archiving it, removing its clip prices, ending its sale window or turning off checkout unlocks them: buyers download their clips for free (watermarked once a watermark is set up), never the original. Photos and clips are always bought in separate orders, even when one package prices both.

### Pausing stops clip sales

Pausing the package that prices clips, setting it back to draft, archiving it or removing its clip prices turns clip selling off for the event, unless another published package (post-event, or a pre-event clip pass) still prices clips. Enabling it again, or publishing a package with clip prices, turns clip selling back on once Motion is ready. Only changes to a package that prices clips do this: editing a photo-only package never changes clip selling. The **Pause** and **Archive** confirmations remind you that clip sales stop too.

### Coming soon

While a live package prices clips but Motion setup isn't finished, buyers see clips as "coming soon": they stay locked, and the gallery says **Clip purchases open soon** and offers no purchase. Once Motion is ready, publishing the post-event package with clip prices puts clips on sale and turns on watermark embedding for newly generated clips. A package that was already live shows **Start selling clips** on its row and in the **Video clips** section; it appears only for a live post-event package while checkout is on.

The optional **Video clips** section on the Configuration tab shows the same checklist with **Recheck**, where clip sales stand, and **Preview quality** (360p, 480p recommended, or 720p), which saves with **Save changes**. Buyers stream a free watermarked preview and buy a package with clip prices to download the original. On Overview, the **Video clips** card shows **Done** only while clips are on sale.

## Sale Phases and Dates

A published package must also be within its sale window. **Pre-event** packages sell while event photos are unpublished; publishing photos stops those sales. **Post-event** packages sell only once photos are published, even if their start time has passed.

The Configuration **Sale schedule** shows what sells now, upcoming changes, and gaps or overlaps. Dates display in your local time zone. A package's end time closes sales from that instant onward.

## Tax and Fees

**Tax on receipts** uses your active organisation tax profile from Payment Configuration (**Tax Configuration → Regular tax**). Turn on **Show tax on receipts** in the event's **Payments → Receipts and tax** row, then choose **Prices include tax** to keep the configured package total, or **Tax added at checkout** to add tax on top. This row is replaced by **Stripe purchases** while Stripe is on the event. For Stripe purchases, set the tax once on the Stripe gateway (**Payment Configuration → Tax Configuration → Stripe gateway tax**), then choose **Package prices** and, if participants need a Stripe-issued invoice, **Include Stripe invoice** in the event's **Payments → Stripe purchases**. See [Stripe invoices and Stripe tax](https://docs.9pic.ai/products/checkout/configuration.md#stripe-invoices-and-stripe-tax).

PayMongo additionally offers **Pass on fees** in the gateway editor. Save the editor after changing it. Each card saves its own settings; there is no global Save for the entire Configuration tab.

## Order Support

Open a transaction to review its current status and available actions. Team admins can use **Record offline payment** for money received directly or to grant access without a charge. Recording marks the whole order paid, grants buyer access, and sends a confirmation email; it does not collect money or track a remaining balance. Completed and refunded orders cannot be recorded again.

**1. Review the order**

Choose **Record offline payment** and check the buyer, package, items, and original checkout amount.

**2. Enter the recorded amount**

**Amount to record** starts with the original checkout amount. Edit it to the amount received, using the order's currency and allowed decimal places. To grant access without a charge, enter **0** and select **Other** as the **Payment method**. The original payment history is preserved.

**3. Record the payment**

Add the receipt date and optional reference or internal notes. The reference is shown to the buyer; notes stay with your team. If purchase webhooks are enabled, choose whether to send one. Review the amount, then choose **Record payment** to save. The recorded amount appears on the completed payment and confirmation email. An unfinished online payment must be closed first; if it is still in progress, wait and try again.

> [!WARNING]
>
> Verify receipt of the buyer's payment, or deliberately choose zero to grant access without a charge. Review the amount before recording: even a reduced amount settles the entire order.

To fix an amount after confirming an offline payment, open its order and choose **Edit amount** beside **Amount**, then **Save amount**. This is available only for completed offline payments. See [Correct an offline amount](https://docs.9pic.ai/products/checkout/transaction-detail.md#correct-an-offline-amount) for limits, history, and notification behavior.

If people paid you directly, for example on your registration form or at the venue, add them as offline buyers so they get their photos without paying again. See [Offline Buyers](https://docs.9pic.ai/products/checkout/offline-buyers.md).

## Legacy Checkout

If an event still uses the older photo-purchase flow, the tab shows a **legacy** panel instead of the current four-tab UI, with guidance on moving to the new checkout. Email [support@9pic.ai](mailto:support@9pic.ai) if you need help upgrading that event while keeping purchase history.

## Common Questions

> [accordion] If I pause the package that sells clips, what do buyers get?
>
> Clip sales stop and buyers can download their clips for free, watermarked once a watermark is set up. Enable the package again to sell clips. Pausing a photo-only package doesn't change clip selling.

> [accordion] Which payment gateways are supported?
>
> Stripe, Xendit, PayMongo, AFS and BENEFIT (BHD only) support online payments. **No gateway** is coupon-only: buyers need an organiser-issued 100% off coupon and no online payment is collected. Configurations are created on the [Payment Configuration](https://docs.9pic.ai/account/payment-gateways.md) page, then assigned per event on the Configuration tab.

> [accordion] Can I sell for one event only?
>
> Yes. Checkout is turned on per event. Assign a gateway, add a support contact, publish a package, and select **Turn on checkout** on just that event.

> [accordion] Why don't I see Turn on checkout?
>
> It appears once a supported gateway is assigned, a buyer support contact (an email or phone number) is saved, and at least one package is published. Until then the status bar says how many steps are left and its button opens the next one.

> [accordion] What product types can I sell today?
>
> The package builder supports **Photos** and, for events with 9Pic Motion turned on, **Video clips**. You can add clip prices as soon as Motion is on; clips go on sale once a watermark is saved, and no video needs to be processed first.

## Next Steps

> [card] [Checkout Configuration](https://docs.9pic.ai/products/checkout/configuration.md)
>
> Gateway, support contact, packages, and buyer options.

> [card] [Packages](https://docs.9pic.ai/products/checkout/packages.md)
>
> Build pricing for pre-event and post-event sales.

> [card] [Coupons](https://docs.9pic.ai/products/checkout/coupons.md)
>
> Create and manage discount codes.

> [card] [Transactions](https://docs.9pic.ai/products/checkout/transactions.md)
>
> Revenue summary and the order table.

> [card] [Payment Configuration](https://docs.9pic.ai/account/payment-gateways.md)
>
> Create payment configurations and the organisation tax profile.

> [card] [Fair Usage Policy](https://docs.9pic.ai/account/plans/fair-usage.md)
>
> Storage limits relevant to Store Original Photos.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.