> ## 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.

# Checkout Configuration

> Assign a gateway, add buyer support, set up packages, and turn on checkout.

> [!WARNING]
>
> 9Pic Checkout is a **Business plan** feature (in test mode on Trial), and the event needs **Store Original Photos** enabled. See the [Checkout overview](https://docs.9pic.ai/products/checkout/overview.md).

## Overview

The **Configuration** tab is one **Checkout Configuration** card. A menu on the left opens one section at a time:

| Section | What it holds | How it saves |
| - | - | - |
| **Payments** | Payment gateways, tax (**Stripe purchases** with Stripe, otherwise **Receipts and tax**) and the buyer support contact | Gateways and support contact on their own, in each dialog; the tax row with **Save changes** |
| **Packages** | Your pre-event and post-event prices | On its own, in the package builder and buttons |
| **Buyer options** (optional) | Full-library picking, a curated photo pool and search refresh | **Save changes** |
| **Video clips** (optional) | Clip sales status, Motion readiness and preview quality | **Save changes** |
| **Purchase webhook** (optional) | Sends completed purchases to your organisation's webhook URL | **Save changes** |

Each menu item shows a short status: **Set up** while something is needed, **Check** when a payment gateway needs attention, a count such as **2 / 3** for options that are on, or whether clips are on sale.

The card header shows the same status as the Overview status bar and offers the next step, then **Turn on checkout**, and **Turn off checkout** while checkout is on.

## Payments

The **Payments** section holds the **Payment gateways** and **Buyer support contact** rows. If a gateway needs attention (its payment account refused the saved key during a payment, or the last key check found the key refused or missing permissions), the section says **1 gateway needs attention: buyers may not be able to pay**, the menu shows **Check**, and that gateway says what to fix: **Key not accepted** or **Key missing permissions**. Fix the key on the [Payment Configuration](https://docs.9pic.ai/account/payment-gateways.md) page.

### Payment gateways

An event can take payment through one gateway, or offer up to five that buyers choose between (for example a card gateway for credit cards and BENEFIT for Bahrain debit cards).

**1. Open the gateway editor**

On the **Payment gateways** row, click **Assign** (or **Edit** once a gateway is assigned). If your organisation has exactly one supported configuration, the row offers **Use this gateway** instead.

**2. Add your gateways**

Pick a saved **Stripe**, **Xendit**, **PayMongo**, **AFS Gateway**, **BENEFIT** or **No gateway** configuration. To offer another, choose it under **Add another way to pay**. Use the arrows to change the order buyers see, and the bin to remove one. The first gateway is the event's main one.

**3. Set what buyers see (optional)**

With two or more gateways, each one has **Label buyers see** and **Note**, for example "Pay by credit card" and "Visa and Mastercard". Leave them empty to use the text saved on the gateway in [Payment Configuration](https://docs.9pic.ai/account/payment-gateways.md), or "Pay with" and the gateway's name.

**4. Save**

Click **Assign gateway** or **Save gateways**. The other sections stay locked until a gateway is assigned; they show **Go to Payments** until then.

When an event has two or more gateways, buyers who click Pay see a **Choose how to pay** window with your labels and notes, in your order. With one gateway, or when a coupon makes the order free, they go straight to payment.

> [!NOTE]
>
> Gateway credentials are created on the [Payment Configuration](https://docs.9pic.ai/account/payment-gateways.md) page. If the list is empty, create a configuration there first.

| Rule | Why |
| - | - |
| **No gateway** and the 9Pic test payment account can't be combined with other gateways | They only work as the event's single way to pay |
| Every gateway must accept the package currency | Package currencies are limited to the ones all your gateways accept; BENEFIT is BHD only |
| A gateway that can't take a published package's currency can't be added | The dialog disables it and names the currency and package. Change that package's currency or pause it first |
| **Receipts and tax** is replaced by **Stripe purchases** while the event has a Stripe gateway | Stripe purchases use the Stripe gateway's tax instead, so a purchase never has both; buyers who pay another way get the 9Pic receipt without tax |
| PayMongo **Pass on fees** | Applies only to buyers who pay through PayMongo |

> [!WARNING]
>
> If checkout is already **live** and you remove a gateway, checkout is **paused** first (**Pause checkout & save**). Select **Turn on checkout** when you're ready for buyers to purchase again. Adding or reordering gateways doesn't pause checkout.

### Stripe purchases

When the event has a Stripe gateway, a **Stripe purchases** row appears between the payment gateways and the buyer support contact. It holds two settings, both saved with **Save changes**, not with the gateway dialog:

* **Include Stripe invoice**: off by default. When it's on, Stripe creates an invoice after each successful Stripe payment and participants can download it from their purchase. Stripe charges a fee for each invoice it creates, even if it's never downloaded (**Stripe invoice pricing** opens Stripe's page). When it's off, participants get the standard 9Pic receipt.
* **Tax**: names the tax the Stripe gateway charges (set in [Payment Configuration](https://docs.9pic.ai/account/payment-gateways/stripe-invoices.md#stripe-tax)) with **Change in Payment Configuration**, and asks for **Package prices**: **Prices include tax** (the default) or **Tax added at checkout**. A worked example shows what a buyer pays for your first published package. When the gateway adds no tax, the row says **Stripe adds no tax to these purchases** with **Set up Stripe gateway tax in Payment Configuration**.

See [Stripe invoices and Stripe tax](#stripe-invoices-and-stripe-tax).

![Checkout Configuration Payments section: a Stripe gateway, the Stripe purchases row with Include Stripe invoice switched on, Tax showing Stripe charges GST 10% Australia with Change in Payment Configuration, Package prices set to Prices include tax and the example A\$30.00 = A\$27.27 plus A\$2.73 GST, then Buyer support contact](https://assets.9pic.ai/docs/dashboard-guide/checkout/stripe-purchases.webp?v=20261105b)

The Stripe purchases row in Payments, with Stripe invoices on and the gateway's GST 10% included in the package price.

### Buyer support contact

Buyers see this contact on the checkout page and in their purchase details when they need help with an order. The row shows the saved email and phone. Select **Add** (or **Edit**) on the **Buyer support contact** row to open the dialog:

| Field | What to enter |
| - | - |
| **Support email (recommended)** | An address buyers can write to. It must be a valid email, like [support@your-race.com](mailto:support@your-race.com). |
| **Phone or WhatsApp** | A number buyers can call or message, in any format. Add the country code if buyers may call from abroad. |
| **Support instructions (optional)** | A short note shown under "Need help?", such as your support hours. |

Add an email, a phone number, or both. Support instructions on their own are not enough. A live preview in the dialog shows how the support card looks to buyers. Select **Save support contact** to save. Support contact editing is locked until a gateway is assigned, but it does not block creating packages.

To remove the contact, empty all three fields. The dialog warns that saving removes it, and the button becomes **Remove support contact**. Checkout then can't be turned on until you add an email or phone number again; if checkout is already on, it stays on and the status says a requirement is incomplete.

## Turn on checkout

Checkout is turned on from the card header (or the Overview status bar), not from a switch in a section. **Turn on checkout** appears once all of these are in place:

| Prerequisite | Needed before turning on |
| - | - |
| Supported gateway assigned | Stripe, Xendit, PayMongo, AFS Gateway, BENEFIT or No gateway |
| Buyer support contact | An email address or phone number |
| Published package | At least one |

A confirmation reminds you that buyers see every published package for the event and that payments go through your assigned gateways. With **No gateway**, it explains instead that no online payment is collected and buyers complete orders only with a 100% off coupon you create on the **Coupons** tab. Confirming turns checkout on straight away; there is nothing else to save.

While checkout is on, **Turn off checkout** asks you to confirm, then hides packages from buyers and stops new payments. Orders, packages and settings are kept, so you can turn it back on later.

## Packages

Packages define what buyers can purchase. Each event has one package per sale phase, so the **Packages** section lists two rows, **Pre-event** and **Post-event**. Only **published** packages appear on the event checkout page.

**1. Set up a package**

An empty row offers **Set up pre-event package** or **Set up post-event package**. Select it to open the package builder on the prices, with that sale phase already chosen. See [Packages](https://docs.9pic.ai/products/checkout/packages.md) for the full builder walkthrough.

**2. Publish it**

New packages start as **Published**, so buyers can see them once checkout is on. You can save one as **Draft** instead in the builder's **Details** step.

**3. Manage packages**

A package row shows its state, sale phase, prices and sale dates. Use **Pause** or **Enable** to hide or show it to buyers, and the **⋯** menu for **Edit details** or **Archive package**. **View archived** lists archived packages, which you can **Restore** as drafts. Pausing or archiving a package with clip prices (a post-event package or a pre-event clip pass) also stops clip sales; the confirmation says so.

Once you have a package, a **Sale schedule** above the rows shows what sells now and what changes next.

> [!TIP]
>
> Package currency options depend on your assigned gateways: the builder only offers currencies that every one of them accepts.

## Buyer options

Optional features that let buyers add more photos beyond their purchased package, and re-search later as new photos arrive:

| Feature | What it does |
| - | - |
| **Pick from the full library** | Buyers hand-pick photos from the full event library, up to **Max photos per buyer** (1 to 200) |
| **Curated generic photo pool** | You choose a set of generic photos (start line, group shots, etc.) buyers can add **Free for buyers** or **Priced like normal photos** |
| **Refresh search results** | Main option for multi-day events: eligible buyers can search again every 12 hours as later-day photos are uploaded |

These options are locked until a payment gateway is assigned, and they save with **Save changes**. See [Buyer photo options](https://docs.9pic.ai/products/checkout/buyer-photo-selection.md) for setup details, including when to turn on search refresh.

## Video clips

This optional section is for events with 9Pic Motion. Clips are sold through packages: there is no on-off switch here. Add a **Video clips** price to the **post-event** package, or a clip pass (the **All items** price) to the **pre-event** package; publishing either turns on clip selling for the event, and pausing, drafting or archiving the last package that prices clips turns it off again.

**Clip sales** at the top shows where clip sales stand:

| Status | Meaning |
| - | - |
| **On sale · 480p preview** | Checkout is on and a live package sells clips (a post-event package, or a pre-event clip pass buyers pre-book). |
| **Coming soon · Motion setup: 2 steps left** | A live package prices clips, but Motion setup isn't finished. Buyers' clips are locked and shown as "coming soon". |
| **Ready · Start selling clips** | Motion is ready and a live package prices clips that buyers still see as "coming soon". |
| **Not on sale · Checkout is off** | A package prices clips, but checkout is off, so buyers download their clips for free. |
| **Not on sale · Package isn’t live** | The package that prices clips is paused, a draft or its sale has ended, so buyers download their clips for free. |
| **Not on sale · Add clip prices to a package** | No package prices clips. |

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. In every other case buyers download clips for free (watermarked once a watermark is set up), never the original.

| Part | What it does |
| - | - |
| **Before you can sell clips** | A checklist of the steps still needed before clips go on sale: **Turn on 9Pic Motion for this event** (links to Event Config) and **Add a watermark**. No video needs to be processed first. Clip prices can be added before then. Select **Recheck** after finishing them. |
| **Start selling clips** | Shown when Motion is ready and the live post-event package already prices clips that buyers still see as "coming soon", while checkout is on. It puts those clips on sale straight away. |
| **Preview quality** | 360p, 480p (recommended) or 720p for the free watermarked preview buyers stream. It saves with **Save changes**. |

On the package row, a paused or draft clip package says its clips aren't on sale. If 9Pic Motion is off for the event, the row asks you to turn it on or remove the clip prices, and **Enable** stays unavailable until you do.

Buyers download the original clip after buying a package with clip prices. See [Selling Motion Clips](https://docs.9pic.ai/products/checkout/overview.md#selling-motion-clips).

## Receipts and tax

Tax is set in **Payments** for every event, between the payment gateways and the buyer support contact. An event with a Stripe gateway shows [Stripe purchases](#stripe-purchases); any other event shows **Receipts and tax**:

| Setting | What it does | Needs first |
| - | - | - |
| **Show tax on receipts** | Shows your tax name, ID and rate on the 9Pic receipt buyers get after paying | An active tax profile in Payment Configuration → **Tax Configuration → Regular tax**. Without one, the row says **Set up a tax profile in Payment Configuration first** and links there |
| **Package prices** | **Prices include tax** (the receipt breaks tax out of the package price) or **Tax added at checkout** (tax is added on top). A worked example shows what a buyer pays for your first published package | **Show tax on receipts** on |

Both save with **Save changes**.

![Checkout Configuration Payments section with an AFS gateway and the Receipts and tax row: Show tax on receipts switched on showing VAT 10%, and Package prices set to Tax added at checkout](https://assets.9pic.ai/docs/dashboard-guide/checkout/receipts-and-tax.webp?v=20261105c)

Receipts and tax in Payments for an event without Stripe, with tax added at checkout.

## Purchase webhook

| Setting | What it does | Needs first |
| - | - | - |
| **Purchase webhook** | Sends this event's completed purchases to your organisation's webhook URL | A webhook URL in Payment Configuration → **Purchase webhook** |

Without the URL, the switch is unavailable and links to the page where you set it. The switch saves with **Save changes**. Older links to **Tax and webhooks** open this section.

## Stripe invoices and Stripe tax

These settings apply only to purchases paid through your own Stripe gateway. 9Pic's test payment account (used on Trial) never issues invoices or adds tax; your own Stripe test key does, as Stripe test invoices.

**Include Stripe invoice** (in **Payments**):

| What happens | Details |
| - | - |
| On the Stripe payment page | Stripe asks for a billing address and lets the participant add a tax ID |
| After payment | Stripe issues a paid invoice. The purchase shows **Download invoice**, or **Your invoice is being prepared** with **Check again** until it's ready. Downloads are never blocked |
| When it's off | Participants get the standard 9Pic **Receipt**. Older Stripe purchases without a Stripe invoice also get the receipt; invoices issued earlier stay downloadable |
| Several ways to pay | Applies only to purchases paid through Stripe |
| Stripe removed from the event | The setting is kept and shows **Inactive** until you add a Stripe gateway again |

> [!WARNING]
>
> Stripe charges a fee for every invoice it creates, even if the participant never downloads it. At the time of writing Stripe lists 0.4% of the total, up to USD 2 (or the local equivalent) per invoice; check [Stripe's current pricing](https://support.stripe.com/questions/pricing-for-post-payment-invoices-for-one-time-purchases-via-checkout-and-payment-links).

**Tax** (in **Payments → Stripe purchases**): Stripe tax is set once per Stripe gateway in **Payment Configuration → Tax Configuration → Stripe gateway tax** (**No tax**, **A tax rate from your Stripe account** or **Stripe Tax (automatic)**), and used by every event on that gateway. The event chooses **Package prices**:

| Package prices | What the buyer pays |
| - | - |
| **Prices include tax** | The package price, with the tax taken out of it, for example **A\$30.00 = A\$27.27 + A\$2.73 GST** at 10%. The checkout summary says **GST 10% included** under the total |
| **Tax added at checkout** | The package price plus tax, added on Stripe's payment page before the participant pays. The checkout summary says **GST 10% is added at payment** under the total |

* With a tax rate, the Stripe account needs a rate of the matching kind (inclusive or exclusive). If it has none, the row says so and links to the tax rates in Stripe. Create the rate, then select **Save changes** again; 9Pic re-reads your Stripe account when saving.
* With **Stripe Tax (automatic)**, either choice works. With no Stripe tax registration where the buyer is, Stripe charges no tax. The checkout summary names no rate here, because Stripe picks it from the buyer's address: it says **Price includes tax** or **Tax is added at payment**.
* With several Stripe gateways, each charges its own tax and the event's **Package prices** applies to all of them.
* If 9Pic can't check your Stripe account while saving, your changes stay on the bar and the message offers **Try again**.
* Invoice and tax settings are frozen on each purchase when the participant opens the payment page. Changing them never alters existing purchases.

For the Stripe account preparation, the AUD worked example and how these options replace the manual Stripe steps, see [Stripe Invoice Setup](https://docs.9pic.ai/account/payment-gateways/stripe-invoices.md).

## Saving your changes

Changes in **Buyer options**, **Video clips**, **Purchase webhook** and the tax row in **Payments** (**Stripe purchases** or **Receipts and tax**) wait until you save them. A bar appears at the bottom of the page saying **You have unsaved changes**, with **Discard** and **Save changes**. One **Save changes** saves every waiting change across those sections.

* Moving between sections keeps your unsaved changes.
* Leaving the tab or the page asks you to stay or discard them first.
* If part of a save fails, the parts that saved stay saved and the rest stay on the bar, so you can try again.
* An invalid **Max photos per buyer** blocks saving until you fix it.
* If saving **Package prices** fails because your Stripe account has no matching tax rate, an error summary at the top links to the setting. If 9Pic can't check your Stripe account, your changes stay on the bar and the message offers **Try again**.

Gateways, the support contact and packages are not on the bar: they save in their own dialogs and buttons.

## Common Questions

> [accordion] Why are the package buttons locked?
>
> Assign and save a payment gateway first in **Payments**. Packages cannot be set up until a gateway is attached.

> [accordion] Why doesn't my support contact count?
>
> Checkout needs an email address or a phone number. Support instructions alone can't be saved. To remove the contact entirely, empty all three fields and select **Remove support contact**.

> [accordion] Why does Payments say a gateway needs attention?
>
> The payment account refused that gateway's saved key while a buyer was paying, or the last key check found the key refused or missing permissions, so buyers may not be able to pay. Fix the key on the [Payment Configuration](https://docs.9pic.ai/account/payment-gateways.md) page. You can still turn checkout on, but fix the key first.

> [accordion] Why is there no Show tax on receipts on my Stripe event?
>
> 9Pic's own receipt tax can't be combined with Stripe. Stripe purchases use the tax set on the Stripe gateway in **Payment Configuration → Tax Configuration → Stripe gateway tax**; choose whether prices include it in **Payments → Stripe purchases**. Buyers who pay another way on that event get the 9Pic receipt without tax.

> [accordion] What happens to orders when I archive a package?
>
> Archiving hides the package from buyers but keeps its historical orders and pricing snapshots. You can restore it later as a draft.

> [accordion] Do I have to configure buyer photo selection?
>
> No. It's optional. Checkout works with published packages alone. Library selection, curated pool, and search refresh add extra ways for buyers to pick or update photos.

> [accordion] What is the best multi-day event setting here?
>
> Turn on **Refresh search results** in **Buyer options**. Buyers who already purchased can return later and find photos uploaded on later days, within remaining package capacity. You can also grant refresh for one order from [Order detail](https://docs.9pic.ai/products/checkout/transaction-detail.md#buyer-refresh-access).

## Next Steps

> [card] [Packages](https://docs.9pic.ai/products/checkout/packages.md)
>
> Sale phases, pricing modes, and package states.

> [card] [Coupons](https://docs.9pic.ai/products/checkout/coupons.md)
>
> Discount codes for checkout.

> [card] [Transactions](https://docs.9pic.ai/products/checkout/transactions.md)
>
> Track revenue and inspect orders.

> [card] [Payment Configuration](https://docs.9pic.ai/account/payment-gateways.md)
>
> Create the gateway configs you assign here.


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