> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kler.africa/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Event payment infrastructure for Africa.

Kler provides event-level payment infrastructure and visibility. Built for ticketing platforms and event organisers who need to centralise payments, monitor inflows, and reconcile transactions in real time.

## What Kler does

Events receive payments from multiple channels — bank transfers, POS terminals, USSD, and card. Without a centralised system, organisers are left piecing together reports after the fact.

Kler solves this by giving every event its own dedicated payment layer:

<CardGroup cols={2}>
  <Card title="Collection Accounts" icon="building-columns">
    Generate a dedicated bank account number per event. All inflows land in one place.
  </Card>

  <Card title="POS Terminals" icon="credit-card">
    Assign physical POS terminals to an event and track every tap and swipe.
  </Card>

  <Card title="Real-time Feed" icon="bolt">
    Receive transaction webhooks the moment a payment hits. No polling.
  </Card>

  <Card title="Reconciliation" icon="table">
    Instantly see totals by channel and terminal. Settlement breakdown included.
  </Card>
</CardGroup>

## How it works

```
Ticketing platform → POST /v1/sessions     → Kler creates session
Kler              → Provisions account + POS terminals
Attendee pays     → Providus fires webhook → Kler records transaction
Kler              → Fires webhook          → Ticketing platform
Dashboard / API   → GET /v1/reconciliation → Live summary
```

## Base URL

```
https://api.kler.africa/v1
```

## Authentication

All API requests require an `x-api-key` header. Keys are issued per organisation. See [Authentication](/authentication) for details.