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

# Overview

Create an account and learn how to build on wallee.

This page gives you the big picture: what {inject-brand-name} is, the core concepts you will meet everywhere in the platform, and how a payment flows through the system. Five minutes here will make everything else in this documentation easier.

### What is {inject-brand-name}?

{inject-brand-name} is a payment platform for **omnichannel payment processing**:

* **E-commerce** — hosted payment page or iframe checkout for your webshop, with ready-made plugins for all major shop systems.
* **In-store** — card terminals fully integrated into the same platform and reporting.
* **Unattended** — payments at vending machines, kiosks and charging stations.

One contract, one portal, one API — every channel feeds into the same transactions, settlements and analytics.

{% hint style="info" %}
**Security built in:** {inject-brand-name} is PCI DSS Level 1 compliant. Payment forms are generated and hosted by {inject-brand-name} (payment page or iframe), which keeps you as a merchant out of most of the PCI scope.
{% endhint %}

### Core concepts

These terms appear throughout the portal, the API and this documentation:

| Concept                   | What it means                                                                                                                                                    |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **User**                  | A person (human user) or system (application user) that logs in. One user can access several accounts.                                                           |
| **Account**               | Your contractual home: plan, billing information, invoices and user management. Created automatically when you sign up.                                          |
| **Space**                 | The operational workspace inside an account: transactions, payment methods, terminals, settlements and settings live here. By default one account has one space. |
| **Space view**            | A lightweight variant of a space — share the same configuration but separate presentation, e.g. country shops of the same webshop.                               |
| **Transaction**           | A single payment. Every transaction follows the same standardized state flow, regardless of payment method or channel.                                           |
| **Processor & connector** | The route a payment takes to the acquiring side. Conditions let you route transactions between multiple connectors.                                              |
| **Manual task**           | A structured request for your decision when something cannot be processed automatically (e.g. suspected fraud).                                                  |

See [Account Structure](/documentation/readme/account-structure.md) for a deeper explanation of users, accounts, spaces and permissions.

### How a payment flows

Every transaction on the platform follows the same standardized process — whatever the payment method:

```
Pending → Confirmed → Processing → Authorized → Completed → Fulfill
                              ↳ Failed        ↳ Voided / Decline
```

The final states (Fulfill, Decline, Voided, Failed) give you a clear signal whether to ship goods or release services. You will find every transaction and its state in your space under **Payment > Transactions**.

### Where to go next

* [**Create an Account**](/documentation/readme/create-an-account.md) — sign up and start your free trial (step-by-step guide).
* [**Account Structure**](/documentation/readme/account-structure.md) — understand users, accounts, spaces and space views.
* [**Users, Roles and Invites**](/documentation/readme/account-structure/permission-concept.md) — give your team and developers the right access.
* [**Manual Tasks**](/documentation/readme/manual-tasks.md) — learn where the platform asks for your decisions.

{% hint style="success" %}
**Tip for developers:** everything you can do in the portal is also available via the [Web Service API](https://{inject-platform-url}/doc/api/web-service) — same concepts, same terminology.
{% endhint %}