> For the complete documentation index, see [llms.txt](https://kreatorverse-2.gitbook.io/kollect-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kreatorverse-2.gitbook.io/kollect-documentation/introduction.md).

# Introduction

This documentation describes how to integrate **Kollect** from your **backend systems** using the **server-to-server (S2S) API** to create **payment links**, and how to receive **signed webhooks** when payments complete or fail.

***

## Who this documentation is for

The intended audience is **backend engineers**, **technical leads**, and **integration partners** who need to:

* Issue invoice-backed payment sessions **without** driving the flow from a browser-only SDK session.
* Automate order fulfillment when a customer pays on the hosted Kollect payment experience.
* Verify webhook authenticity using a **shared signing secret**.

If you are building a browser or mobile client with user sessions, additional product surfaces (for example DPoP-protected status polling) may apply; this guide focuses on **API key + HMAC** server flows.

***

## What you can build

| Capability             | Description                                                                                                                                                    |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Create payment URL** | `POST /sdk/server/create-payment` returns a `paymentUrl`, `paymentId`, and invoice identifiers.                                                                |
| **Hosted checkout**    | Your customer opens the URL and completes payment in the Kollect UI.                                                                                           |
| **Outbound webhooks**  | Kollect POSTs JSON to your HTTPS endpoint with `x-kollect-signature` when the payment settles (for `kollect-server` integrations, `invoice_settlement` scope). |

***

## Documentation map

| Section                                                                                       | Purpose                                                               |
| --------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| [Architecture & data flow](/kollect-documentation/introduction/architecture-and-data-flow.md) | End-to-end sequence and component boundaries.                         |
| [Getting started](/kollect-documentation/introduction/getting-started.md)                     | Prerequisites, onboarding, and configuration checklist.               |
| [API reference](/kollect-documentation/api-reference.md)                                      | Endpoint contracts, headers, and examples.                            |
| [Security](/kollect-documentation/security.md)                                                | Credentials, signing, and idempotency.                                |
| [Webhooks](/kollect-documentation/webhook-overview.md)                                        | When events fire, how to register URLs, and how to verify signatures. |
| [Reference](/kollect-documentation/api-reference.md)                                          | Statuses, errors, and rate limits.                                    |
| [Guides](/kollect-documentation/guides.md)                                                    | Lifecycle, testing, and operational best practices.                   |

***

## Quick links

* **Primary endpoint:** [Create payment URL](/kollect-documentation/api-reference/create-payment.md)
* **Webhook verification:** [Payload & signature verification](/kollect-documentation/webhook-overview/payload-and-verification.md)
* **Errors:** [Error handling](/kollect-documentation/reference/error-handling.md)

***

## Versioning note

Behavior documented here reflects the **Kollect backend** implementation (routes, middleware, and services). Always confirm **base URLs**, credentials, and environment-specific settings with your **Kollect platform or integration contact** for production deployments.