The neutral layer for ticket inventory

Sell every seat once. Through every seller.

Bandariva lets venues and organisers hand tickets to many marketplaces and sellers without losing track of a single seat. One shared record, live reservations, signed ticket delivery. Your money and your tickets stay exactly where they belong.

Request access See how it works

Never holds ticket money
Never issues tickets
Any payment method, any currency

Jazz Night · Main HallILLUSTRATION

Made-up sellers and seats, to show the idea. A seat is only ever held by one seller.

Why this exists

Selling a seat twice is a systems problem, not a people problem.

The moment more than one seller has a share of the same event, each keeps its own picture of what is left. The pictures drift. Someone finds out at the gate.

Without a shared record

Three sellers, three versions of the truth

Sales are copied between spreadsheets, chat groups and exports, hours or days late.
Two buyers arrive with a ticket for the same seat.
Nobody can say, before the event, how many tickets are really out there.
After the event, each seller’s numbers are argued over before anyone is paid.

With Bandariva

One ledger. Every seller reads and writes to it.

A seller reserves a seat before taking payment. Two checkouts cannot hold the same seat.
Every movement is written once, never edited, and visible to the owner.
Disagreements are flagged the moment they appear, not found at the gate.
Both sides read the same statement when it is time to settle.

How it works

Four steps from “open the event” to “everyone is paid”.

Bandariva sits in the middle as the shared record. It does not take the booking, the payment or the ticket. It makes sure everyone who does agrees on what is left.

Open the event

The owner publishes the event with its seat map or ticket types, then decides who may sell: invite sellers one by one, or open it to verified sellers on terms set up front (commission, days to settle, price range).
Hand out inventory

Allocate seats or quantities to each seller, or let trusted sellers reserve live from what you have not allocated. Unsold seats come back to you by themselves at a cut-off you choose.
Reserve, pay, confirm

A seller holds the seats while its buyer pays in its own checkout: mobile money, card, bank transfer, anything. Paid, it confirms. Not paid, the hold lapses and the seats are free again.
Deliver, then settle

Bandariva signs a short-lived proof of the sale. The ticketing system that owns the event checks it, issues the ticket itself and redeems it. After the event both sides see the same statement.

What goes where

Three things travel in three separate lanes. Bandariva carries only one of them: the shared record.

Swipe sideways to see the whole picture.

Who it’s for

One layer, four ways to use it.

Every organisation gets the same API and the same terms. What you are on an event (owner, venue, seller or issuer) is decided event by event, not by a label on your account.

Venues and owners Marketplaces and sellers Ticketing systems Developers

Venues and event owners

See every seat, every seller, every shilling owed.

You sell through your own box office and two promoters, and their numbers arrive in three formats, a week late.

Draw the hall once: sections, rows, numbered seats, price tiers, a stage, wheelchair and companion spaces. Reuse it for every event.
Give each seller seats or quantities, with a cut-off that returns the unsold ones.
One ledger shows sold, held and left, per seller. Oversold seats and seat conflicts are flagged straight away, and door counts are checked against sales.
Commission, fees on top and days-to-settle are agreed before the first sale and locked once it happens.
Approve who may use your venue, and show fans a public page of the sellers you have authorised.

Talk to us about your venue

Settlement statement · Jazz Night

Seller	Tickets	Gross	Keeps	Owes you
Marketplace A	412	1,236,000	123,600	1,112,400
Box-office app	268	804,000	64,320	739,680
Promoter’s site	96	288,000	28,800	259,200

Due from sellers · KES2,111,280

Example figures. Both you and each seller read the same statement. Bandariva works it out; it does not move the money.

Marketplaces and sellers

Sell events you don’t run, without the risk of a double sale.

You could sell far more events if you could trust the stock. Today every new venue is a new spreadsheet and a new phone call.

Join events through an invitation, or find open events from verified owners, each with its terms in plain view.
Reserve seats while your buyer pays, then confirm. Best-available seating puts a party together, nearest the stage, and keeps wheelchair spaces for those who need them.
Keep your own checkout, your own brand and your own payment methods. Keep the fee you agreed.
Report from the dashboard on a phone, upload a CSV, or connect your system through the API.
See your own position at any time: allocated, held, sold, returned.

Become a seller

Reservation · Stalls, row C

Stalls C-7Stalls C-8Stalls C-9

4:12

Held for your buyer while they pay with mobile money. If the payment fails or they walk away, the seats go back by themselves.

Confirm sale · KES 9,000Release seats

Ticketing systems

Stay the system of record. Let others sell.

You issue the tickets and hold the scanners. You would like to open your inventory to more sellers without losing control of who is admitted.

Bandariva never holds a ticket or a barcode. A seller presents a signed token; you verify it, issue the ticket in your own system and redeem it once.
Tokens are signed with Ed25519 and checked offline against published keys. They expire in minutes.
If you cannot issue (the seat is gone, the event changed), say so: the sale is reversed and the seller refunds its buyer.
Resale is available only where you have said, in your own name, that you can void a ticket and issue a new one.

Read the issuer guide

Reservation token · what you verify

// signed with EdDSA, valid for minutes
{
  "iss": "bandariva",
  "aud": "your-organisation-id",
  "sub": "the-seller",
  "evt": "jazz-night",
  "catName": "Stalls",
  "seats": ["Stalls C-7", "Stalls C-8"],
  "amt": 600000, "cur": "KES",
  "exp": 1793700900
}

Developers

A small, predictable API you can build on in an afternoon.

Most ticketing integrations are a pile of exceptions. This one has a few verbs, and they behave the same every time.

REST and JSON. Amounts are whole minor units with an ISO currency, never floats.
An idempotency key on every write: retry as often as the network makes you.
Signed, retried webhooks, de-duplicated by delivery id, plus plain reads that are always right.
Keys with the least power needed: a role, a list of events, your server’s addresses, an expiry.
Prefer files? A CSV import with a dry-run preview.

Open the developer guide

Reserve, pay, confirmcURL

# 1. hold two seats while the buyer pays
curl -X POST https://api.bandariva.com/v1/events/$EVENT/seat-reservations \
  -H "Authorization: Bearer $KEY" \
  -H "Idempotency-Key: checkout-8841" \
  -d '{"bestAvailable":{"quantity":2},"ttlSeconds":300}'

# 2. once paid, confirm: you get the signed token back
curl -X POST .../seat-reservations/$ID/confirm \
  -d '{"amountCents":600000,"reference":"order-8841"}'

Why Africa, why now

Built for how events actually sell here.

Elsewhere, big ticketing groups and distribution platforms already connect inventory to many marketplaces. Here, most platforms still sell from their own stock, and a venue that uses more than one channel keeps the books by hand. There is room for a neutral layer, and it should be built around how Africa pays and travels.

Every platform sells from its own stock.

A venue that adds a second seller usually adds a second list to reconcile. Bandariva gives the venue one record that every seller, local or global, reads and writes to, so you can say yes to more channels without more risk.

Box officeMarketplacesPromotersResellersPartner apps

Money moves on mobile wallets and cards, and that’s none of our business.

M-Pesa, MTN, Airtel, cards, bank transfers: each seller keeps its own payment rails. Because Bandariva never touches the payment, there is nothing to integrate, no float to hold and no licence you need from us to start.

M-PesaMTN MoMoAirtel MoneyCardsBank transfer

Mobile money services processed over $2 trillion worldwide in 2025, and sub-Saharan Africa leads the world in mobile money (GSMA, 2026).

Events cross borders and currencies.

Tours, festivals and tournaments sell in shillings, naira, rand, cedis and dollars. Every amount carries its currency, statements are kept per currency and never added across them, and an event can be sold from any country.

KESNGNZARGHSUGXTZSRWFXOFEGPUSD

Global ticketing is arriving. Local venues should keep their options.

In 2026 a global ticketing group launched a platform in Kenya and Uganda. As more arrive, venues and promoters will want to sell through many channels without handing their inventory to any one of them. Bandariva is not a ticketing company and never will be: it neither issues tickets nor holds money, so it can sit between all of them.

Source: Live Nation newsroom, 20 August 2026.

When demand beats supply, fakes follow.

Big matches and tours attract look-alike websites and tickets sold outside official channels. Every event can have a public page that lists the sellers its owner has authorised and the web domains each has proved it controls, so a fan can check before paying.

Made light, for phones and thin connections.

The dashboard works on a phone. This site loads no third-party scripts and no tracking, and every figure in the product is an exact whole number in the smallest unit of the currency.

What’s in it

Everything a shared inventory needs. Nothing it shouldn’t have.

Seat maps and reserved seating

Sections, rows, numbered seats, price tiers, a stage and walkways. Wheelchair, companion and restricted-view marks. Best-available for a party, a fire limit, and a full history for every seat.

Live reservations

Hold, extend, confirm or release while the buyer pays. A lapsed hold frees itself. Two checkouts cannot take the same last seat.

One ledger, never edited

Every allocation, sale and reversal is written once. Discrepancies, oversold seats and door-count gaps show up the moment they appear.

Commission your way

Commission inside the price, a fee on top the seller keeps, a fee shared with the owner, a cap on it, or a referral where the owner collects. Agreed up front, shown on one statement.

Door counts

Gate staff record admissions with credentials limited to one event, so tickets sold can be checked against people through the door.

Webhooks and imports

Signed, retried webhooks for every change that matters. A CSV import with a dry-run preview for sellers who start with a file.

Verified organisations

New organisations start capped until they are verified. Look-alike names are refused, and a venue’s name cannot be claimed twice.

Roles and keys

Seven roles for people, with authenticator codes for anything sensitive. Keys limited to a role, named events, your server’s addresses and an expiry.

Resale, where it is safe

Listed and tracked only on events whose issuer can void a ticket and issue a new one, with a price ceiling the owner sets.

Trust

Neutral by construction, not by promise.

Venues will only hand their inventory to a layer that cannot be turned against them. So we left out the things that would let it.

Bandariva will never~~Hold~~ your ticket moneyBuyers pay the seller; sellers settle with owners. Money never passes through Bandariva, so a failure here cannot freeze it.

Bandariva will never~~Issue~~ or store ticketsThe issuer’s system makes the ticket. A breach of Bandariva cannot produce a forged one.

Bandariva will never~~Decide~~ who is rightWe work out the statement. We do not referee a dispute between an owner and a seller, or hold anything back because of one.

Bandariva will never~~Read~~ your salesOperators can create and suspend organisations. There is no operator route to anyone’s events, sales or statements.

The same for everyone

Every organisation gets the same API and the same terms.
No organisation is treated differently in code, and the build fails if one is.
Any exception to the standard terms is recorded with a reason in an append-only log.

Against impersonation

A venue is owned by one organisation; others need its approval to book it, and dates lock once approved.
Public authorised-sellers page per event, with domains proved by a DNS record.
Unverified organisations are capped on events, tickets and sellers.

Ordinary good security

Authenticator codes for sensitive actions; keys stored hashed and shown once.
Signed webhooks and tokens; every operator action is logged.
Encrypted nightly backups, and a "download my data" export so your data is yours to take.

Pricing

Owners and venues pay nothing. Sellers pay a sliver, after a free first year.

We are not a payment company, so we don’t take a share of ticket money. We charge for the software, and only for tickets sold on someone else’s event.

Owners and venues

Free

For your own tickets and for every seller you invite or accept. Nothing is held back for a paid tier.

Seat maps, layouts and best-available
Allocation and live reservations
The ledger, discrepancies and door counts
Settlement statements and webhooks
The dashboard, the API and your data export

Sellers

0.5% of the value you sell, after the free allowance

Months 1 to 12Free, counted from the day you are verified.
After thatThe first 1,000 tickets you sell each calendar year are free.
Beyond that0.5% of the value of the tickets you sell.

Fulfilled resales are charged the same rate. Billed monthly, in arrears, per currency.

Launch pricing for the pilot. Ticketing systems that only issue tickets: ask us. Read the plain-language terms at api.bandariva.com/public/commercial-terms.

Questions

The things people ask first.

Does Bandariva handle payments?

No. Buyers pay the seller in the seller’s own checkout, and sellers settle with owners after the event on the terms they agreed. Bandariva calculates the statement both sides see; it does not collect or pay out. That is deliberate: it keeps a failure here from ever freezing anyone’s money.

Do I need a developer to use it?

No. Owners set up events and invite sellers from the dashboard, and sellers can record sales by hand or upload a spreadsheet. Everything the dashboard does, the API does too, so you can start by hand and automate later.

What stops a seller overselling?

Sellers who hold an allocation reserve seats before they take payment, and a reservation can only be made from what is left. Sellers who report from their own system are never refused (the sale already happened), but any disagreement is flagged to the owner at once as an oversold ticket or a seat conflict.

Who issues the ticket?

The ticketing system the owner names as the issuer, or the owner. A seller presents a signed token; the issuer verifies it, issues the ticket in its own system and redeems the token once. Bandariva never holds the ticket, the barcode or the code on the door.

Which countries and currencies does it work in?

Any. Every amount carries an ISO currency code and is a whole number in the smallest unit; statements are kept per currency and never added across them. It is built for African events first, and nothing in it is limited to Africa.

Can tickets be resold?

Only on events whose issuer has said that it can void a ticket and issue a new one. Bandariva lists, reserves and tracks the resale; the issuer replaces the ticket, so the old one stops working. The owner sets a price ceiling.

Can I test before I connect real events?

Yes. Ask us and we will set up a separate environment for testing, kept apart from real events.

What happens to our data if we leave?

It is yours. Owners and admins can download everything their organisation has in Bandariva at any time.

Now onboarding pilot venues and sellers

Running a venue, an event or a marketplace?

Tell us what you sell and who you sell it through. We will set you up with a verified account and walk you through your first event.

Email hello@bandariva.com I already have an account