Skip to main content
The Taberna API lets your server charge a customer in crypto, priced in fiat. You create a charge, redirect the buyer to a hosted checkout page, and a signed webhook tells you when the money landed on-chain. You do not build coin selection, exchange-rate display, deposit addresses, QR codes or confirmation progress. Those live on Taberna’s hosted pages.

​
How it works

  1. Your server creates an order or an invoice and gets back a hosted checkout link.
  2. You redirect the buyer to that link. They pick a token, pay a locked quote, and watch it confirm.
  3. Taberna POSTs a signed order.completed or invoice.paid webhook to your endpoint. You fulfil there.

​
Orders or invoices

Best when you sell a fixed set of things at fixed prices — plans, tiers, licences, downloads.Create the products once (in the dashboard), then reference them by id:
Taberna computes the total, reserves any finite delivery stock for the order’s lifetime, and attaches the delivery to the completed order.

​
Dashboard versus API

The split is deliberate: anything that configures the store is a human action in the dashboard; anything that transacts is available to your server.
There is no API-key route to create products, stores, invoice templates or API keys, and a merchant can run an entire shop without ever writing code — see Sell without code. If you are integrating against a store someone else set up, read What Taberna does not do before you design around a capability.

​
Where keys come from

API keys are minted in the dashboard by a store owner, admin or developer, are bound to one store, and carry an explicit scope set. There is no implicit full-access key and no test key prefix. See Authentication.

​
Start here

Quickstart

Mint a key, create an order, redirect, fulfil on the webhook.

Webhooks

The ten events, payload shapes, and signature verification.

API Reference

Every endpoint and every field, generated from the running service.