> ## Documentation Index > Fetch the complete documentation index at: https://docs.macropay.ai/llms.txt > Use this file to discover all available pages before exploring further. # Orders & Subscriptions > Track every sale, subscription, and checkout — with tax already remitted and disputes handled as your Merchant of Record. Every successful payment becomes an **order**. One-time purchases and recurring subscriptions flow through the same record, because in Macropay both are just **products** with different billing logic. As your Merchant of Record, we're the legal seller on each order — so the sales tax and VAT you see attached has already been calculated and remitted on your behalf, and you keep a clean, auditable trail of every transaction. Because Macropay is the seller of record, the tax line on an order isn't a number you owe — it's tax we collect and remit worldwide. Your liability stays bounded; the compliance work doesn't land on you. ## Sales overview The **Sales** view is your running ledger: a paginated list of every order, newest first. Scan revenue at a glance, then drill into any single sale for the full breakdown. ## Anatomy of an order Open any sale to see the metadata captured at the moment of purchase: | Field | What it tells you | | -------------- | ----------------------------------------------- | | **Amount** | Gross value charged to the customer | | **Tax amount** | Sales tax / VAT we collected and remit for you | | **Invoices** | The MoR invoice issued for this order | | **Customer** | Buyer profile, plus their full purchase history | Selecting the customer expands their basic details alongside every past order they've placed — useful for support, refunds, or spotting repeat buyers. Building agent or usage-based products? Orders surface alongside the metered events and value receipts those products generate, so billed revenue and the underlying activity sit in one place. See [usage-based billing](/features/usage-based-billing/introduction) for how metered charges roll up into orders. ## Checkout sessions Before an order exists, there's a **checkout session**. This view lists them all, and you can filter by customer email, status, or product to find exactly the one you need. A session moves through four states: Created and waiting on the customer to enter payment details. The customer hit **Pay** or **Subscribe** — payment is processing. Payment cleared and an order was created. The session timed out before completion. Spin up a fresh checkout to retry. ## Diagnosing failed payments Click into any checkout to inspect its **payment attempts**. When a charge is declined or fails, this is where you see exactly why — the decline reason, the attempt history, and what the customer experienced. Card data never touches your servers. Every attempt is tokenized in our PCI DSS Level 1 compliant vault, so you get the diagnostic detail without inheriting the PCI scope.