Expereon platform guide

High-level documentation for how Expereon fits together, how to get started, and how day-to-day work flows for travel-industry buyers and sellers. It focuses on concepts and outcomes rather than exhaustive UI or API reference, and what you see in the product can vary by programme, region, and release.

Disclaimer: Product behaviour, availability, and compliance steps can change. Treat this guide as orientation, not a legal or contractual agreement.

Audience: Buyer organisations, seller organisations, and developers (buyer or seller side) who submit booking reports over the API so invoices can be raised automatically. It does not cover how a programme operator administers tenants or runs compliance reviews on your behalf.

Who this is for

• Buyers (for example online travel agencies and similar partners) who fund obligations, connect sellers, approve invoices, and run settlement in line with their commercial terms.
• Sellers (for example hotels, airlines, ground transport) who receive proceeds, confirm or correct auto-generated invoices tied to bookings, and manage payout destinations.
• Developers who send booking reports through the API (from the buyer’s or seller’s stack, depending on your programme) so the platform can create invoices automatically and notify downstream workflows via webhooks.

Documentation map

Document	Purpose
Overview	What Expereon is, who the actors are, and how onboarding fits together
Key concepts	Balances, invoices, approvals, settlement, and trust at a conceptual level
Getting started — buyers	Account, organisation, users, funding, sellers, and trust settings
Getting started — sellers	Account, wallet or payout setup, and buyer relationships
Invoices and payments	Booking-driven invoice automation, buyer review, settlement, disputes, and refunds
Reporting and day-to-day operations	Dashboards, statements, archive, and notifications
Integrations	API keys, booking submission, webhooks, sandbox, and logs
Glossary	Short definitions of recurring terms