> ## 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.
# Payout wallets
> The addresses your sales are paid into — one per network.
A payout wallet is an address you own, on a network you accept payments on. Taberna
forwards every sale straight to it. Taberna never holds a balance for you and there is
nothing to withdraw.
Everyone on your team can see these addresses. **Only an owner can add or change one** —
it is the one thing no other [role](/guides/team) gets.
## One address per network
You register **one address for each network**, under **Settings → Payments**. There are
five, so five is the most you can have:
| Network | Address looks like |
| ---------------------------------- | ---------------------------------------------- |
| Solana | `7xKXtg2CW87d97TXJSDpbD5jBkheTqA83TZRuJosgAsU` |
| Ethereum, Base, Polygon, BNB Chain | `0x742d35Cc6634C0532925a3b844Bc9e7595f…` |
Ethereum, Base, Polygon and BNB Chain all use the same address format, but you still set
each one separately — you may well want them going to different places.
## Adding one
Press **Add Address**, choose a network, paste the address, and save. Only networks that
do not already have an address appear in the list.
Taberna checks the address before saving it. A Solana address has to decode properly and
be the right length; an address on the other four has to start with `0x` and be 40 hex
characters after that. The all-zero address is refused outright, because money sent there
is gone forever.
Paste the address; never retype it. Taberna can tell you the address is
*well-formed*, but nothing can tell you it is *yours*. Send yourself a small test
payment the first time if you want to be certain.
## Changing one
Open the address and press the pencil icon. You can change the address, but not which
network it belongs to. There is no confirmation step and no delay — the next sale on
that network goes to the new address.
Payments already on their way to the old address still land there. If you are changing
an address because you lost access to the old wallet, check your recent orders first.
Addresses cannot be deleted, only replaced. If you want to stop accepting a network,
switch its coins off under Payment Methods instead.
## Why a coin will not switch on
Each network's coins stay greyed out until that network has a payout address — the panel
is labelled **(no address)** until you add one. Taberna will not let you accept money it
has nowhere to send.
## What to read next
What happens between your customer paying and your wallet filling.
Which coins to accept.