> ## 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.
# Analytics
> What the dashboard home page reports, and how each number is worked out.
The first screen you see after signing in is your store's numbers. Choose a period at the
top: last 24 hours, 7 days (the default), 14 days, month, 3 months, 6 months, or all time.
## The three headline numbers
| Card | How it is worked out |
| ----------------- | --------------------------------------------------------------------- |
| **Total Revenue** | The prices of every order that **completed** in the period, added up. |
| **Orders** | How many orders completed in the period. |
| **New Customers** | How many different email addresses those completed orders came from. |
Everything on this page counts **completed orders only**. Pending, partial and expired
orders are not in any of it, and neither is anything that has not been paid for yet.
Two things to know when reading these figures. Revenue is shown in dollars whatever
currency your orders were priced in, so a mix of USD and EUR sales is added together
without conversion. And **New Customers** counts distinct email addresses within the
period — someone who bought from you last year and came back today is counted.
## Revenue and Orders chart
Both series over the period. How finely it is grouped depends on the range you picked:
by the hour for 24 hours, by the day up to a month, by the week for 3 and 6 months, and
by the month for all time.
## The three cards below
**Customer Rate** splits the period's buyers into first-time and returning. A buyer is
first-time if this period contains their very first completed order with you, ever.
Over the **all time** range everyone is first-time by definition, so returning shows as
zero. That is arithmetic, not a bug.
**Top Products** ranks your five best sellers by revenue, using the product names as they
were at the time of sale — so a renamed or deleted product still shows up under what it
was called when it sold.
**Payment Methods** shows which coins your customers actually used, as a share of all
completed payments. This one counts **invoice payments as well as orders**, so it can add
up to slightly more activity than the Orders card.
## What is not here
There is no export, no custom date range, no per-product page and no way to save a
report. What is on this screen is what there is.