> ## Documentation Index
> Fetch the complete documentation index at: https://docs.taberna.io/llms.txt
> Use this file to discover all available pages before exploring further.
> ## Agent Instructions
> Taberna is a crypto payments API. Amounts are priced in fiat (USD or EUR) and paid in crypto.
> Fiat amounts are ALWAYS decimal strings ("9.99"), never numbers. Crypto amounts are integer strings in the asset's smallest unit.
> Authenticate merchant endpoints with `Authorization: Bearer tbrn_live_...`. Every key is bound to one store and carries an explicit scope set, so never pass a store id to a /v1 endpoint.
> A 401 means the credential is bad; a 403 means the key lacks a scope. Never retry or re-authenticate on a 403 — surface it as a configuration error.
> The /v1/checkouts endpoints are deliberately unauthenticated and run in the buyer's browser. Never send an API key to a browser.
> Verify webhook signatures over the RAW request body before parsing JSON, and treat delivery as at-least-once: handlers must be idempotent.
> Never grant value based on a browser redirect to successUrl. Fulfil on a signature-verified webhook, or on a server-side read of GET /v1/orders/{id} or GET /v1/invoices/{id}.
> There is no test mode: every payment method is a live chain moving real funds.
> A merchant can run an entire shop with no code: the dashboard creates products and invoices, and every store can host a storefront at {slug}.taberna.io with its own theme, sections, branding and optional custom domain. Never assume the reader has an API integration.
> Taberna issues no refunds and performs no KYC. A refund is something the merchant sends from their own payout wallet, off-platform.
# Products
> Creating something to sell, and what each field on the form does.
A product is a fixed-price item in your catalogue. Customers buy products from your
storefront, and orders are always for products.
Products live under **Products** in the sidebar. Press **New Product** to create one.
Everyone on the team can see them; creating and editing needs the owner, admin or manager
[role](/guides/team).
## The form
| Field | What it does |
| ----------------- | ---------------------------------------------------------- |
| **Title** | The name customers see. Required, up to 255 characters. |
| **Description** | Optional. Shown on the product page and in the cart. |
| **Price** | A number like `19.99`. Required, up to two decimal places. |
| **Currency** | USD or EUR. Set per product, not per store. |
| **Listed** | Off by default. See below — this one matters. |
| **Product Image** | JPEG, PNG, WebP or GIF, up to 5 MB. |
## What "Listed" controls
**Listed** does two things at once:
* It decides whether the product appears on your storefront.
* It decides whether the product can be **bought at all**. An unlisted product is
refused at checkout, even by someone holding a direct link.
So unlisting is how you retire something without deleting it — the product's past orders
stay intact and readable, but no new ones can be created.
Leave **Listed** ticked for anything you want to sell today.
## Adding digital delivery
Saving the product creates it. To set up automatic delivery — licence keys, a file, a
redirect — open the product again and use the **Delivery** card, which only appears once
the product exists. That card is also where per-order quantity limits live.
See [Digital delivery](/guides/digital-delivery).
## What products cannot do
Stated plainly, so you are not left looking for a setting that is not there:
* **One kind of product.** A one-off purchase. There are no subscriptions and no
recurring billing.
* **No variants.** No sizes, colours or editions — make each one its own product.
* **No physical goods.** There is no shipping address, no postage and no stock for
anything you post.
* **No discount codes and no sales.** The price is the price.
* **No search or filter** on the products page. It is a plain grid of everything.
## What to read next
Hand over keys, files or a link automatically.
Put your products on a page customers can browse.