> ## 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.
# Orders and payments
> Reading the orders list, and what an order's page tells you about a payment.
Every sale is an order. The **Orders** page lists them all; clicking one shows you
exactly what happened, down to the transaction on the network.
## The four statuses
| Status | What it means | What to do |
| ------------- | ------------------------------------------------------------------- | --------------------------------------- |
| **Pending** | Created, not paid yet. | Wait. The customer has a window to pay. |
| **Completed** | Paid in full. Delivery has been handed over. | Nothing. This is the good one. |
| **Partial** | Some money arrived, but less than the price, and the window closed. | Decide yourself — see below. |
| **Expired** | Nothing arrived in time. | Nothing. No money moved. |
Completed and expired are final. So is partial, which is why it needs a word.
### When an order goes partial
Your customer sent something, but not enough, and the clock ran out. That money is still
forwarded to your payout wallet — Taberna does not strand it — but the order is not
complete and nothing was delivered.
Nothing happens automatically from here. Your options are to honour the sale anyway, ask
the customer to buy again, or send their money back from your own wallet. Taberna cannot
refund it for you.
## What the buyer sees
They pick a coin from the ones you accept, and Taberna locks a price in that coin for
**up to 30 minutes**. They see the exact amount, an address and a QR code, then a
progress indicator while the network confirms it.
If they change their mind about which coin to use, they can switch — the old address
keeps working anyway, so money already sent is never lost. If the 30 minutes run out with
nothing paid, nothing is lost either: they simply pick a coin again and get a fresh price.
## The orders list
Seven columns: **Product**, **Qty**, **Amount**, **Status**, **Method**, **Customer** and
**Date**, twenty to a page.
You can filter by status. **There is no search box, no date filter and no export** — if
you are hunting for one order, filter by status and page through.
## An order's page
Click any row. You get:
* **Summary** — when it was created, when it expires, when it completed, how many units.
* **Customer** — their email address and the IP address they paid from.
* **Items** — each product, quantity, unit price and the total.
* **Payments** — one block per attempt, newest first. A customer who switched coins or
let a price lapse will have several. Each shows the coin, the attempt's status, the
amount quoted, the amount received and the deposit address.
* **On-chain payment** — the actual transactions, each linking out to a block explorer so
you can see them for yourself.
* **Settlement** — whether the money has reached your wallet yet, in plain English. See
[How you get paid](/guides/how-you-get-paid).
## What you cannot do to an order
Orders are a record, not a control panel. From this page there is **no refund button, no
manual fulfil button, no cancel button and no way to re-send a delivery**. If a customer
lost the keys they were sent, you send them again yourself.
## What to read next
From the deposit address to your wallet.
The full list, stated plainly.