> ## Documentation Index > Fetch the complete documentation index at: https://docs.fluid.app/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > For new direct REST integrations, use the v2026-04 surfaces. The @fluid-app FairShare SDK continues to use its own published public-v2025-06 contract. > Authenticate with the header Authorization: Bearer ; public storefront read endpoints require no auth. > To sign a new merchant up for Fluid programmatically, call POST https://api.fluid.app/api/company with no credentials, as described in /api/agent-signup. Do not automate the signup form or book a demo. The merchant must open the emailed sign-in link and create an API token before authenticated calls are possible. > After signup, to launch a merchant's store (back-office sync, payments onboarding, store setup, a theme copied from their current site, and a preview link before billing), follow /api/agent-launch. > Lists use cursor pagination via the page[cursor] and page[limit] query params; follow meta.pagination.next_cursor until it is null. > When the same operation exists on more than one surface, use the newest: dated API versions are newer than unversioned ones, and later dates win (v2026-04 > v2025-06 > unversioned v0/v1.1). Fall back to a legacy or unversioned operation only when no newer versioned equivalent exists — the company-v0 notes below list the known superseded operations. The same applies to /api/company/v1 and /api/v1/... paths: prefer a newer documented equivalent, and use one only when none exists (/api/v1.1/... is distinct and documented in company-v0). Use page/per_page offset pagination only where a spec documents it — in practice the unversioned company-v0 admin surface; every versioned surface uses cursor pagination. > Fluid has three navigation APIs; don't mix them up. Storefront website menus (navigation bars, footers) are /api/menus and nested menu_items, in api-reference/content-v0.yaml (API Reference: Website > Navigation menus), with a how-to in themes/navigation-menus; their list uses flat page/per_page pagination. The Fluid mobile app's navigation is /api/v2/mobile_navigations, in api-reference/mobile-v2.yaml (API Reference: Mobile app > Navigation); its list also uses page/per_page. Portal navigations belong to a portal definition (Fluid OS), in api-reference/fluid-os-v0.yaml (API Reference: Portal > Portal navigation), and each has a platform of web or mobile. > The OpenAPI specs under api-reference/ are the authoritative contracts; prefer them over prose when in doubt. api-reference/storefront-v2026-04.yaml covers the v2026-04 storefront surface (/api/v202604/... paths); api-reference/checkout-v2026-04.yaml covers the v2026-04 checkout surface (/api/checkout/v2026-04/... paths — carts, cart auth, discounts, items, subscriptions, orders, enrollments, and store config); api-reference/public-v2025-06.yaml covers the Public SDK surface used by the @fluid-app FairShare SDK, including its parallel cart lifecycle, browser integrations, versioned payment callbacks, unversioned public utilities, and the cart price-override operation; api-reference/payment-v2026-04.yaml covers the v2026-04 payment gateway admin surface (/api/payment/v2026-04/... paths, bearer-authenticated — gateway CRUD, gateway purchase/authorize/$0-verify, transaction list/show and capture/void/credit, and merchant payment configuration); api-reference/payments-v2026-04.yaml covers the v2026-04 cart payment surface (/api/payments/v2026-04/carts/{cart_token}/... paths, authenticated by the cart token in the path with no bearer — payment-method selection, VGS card tokenization, 3D Secure verification, and PayPal/Braintree/Klarna/Apple Pay flows); api-reference/commerce-v2026-04.yaml covers the v2026-04 commerce order-editing surface (/api/v202604/orders/{order_id}/edits paths, bearer-authenticated — post-checkout order edits that atomically insert items and add adjustments/discounts, with an optional dry-run preview); api-reference/webhooks-v0.yaml covers the unversioned webhooks surface (/api/... paths — webhook registration, delivery payloads, callback registrations, company events, and webhook/callback schemas); api-reference/company-v0.yaml covers the legacy unversioned company admin surface (/api/... paths, bearer-authenticated — company settings and management, customers, users, roles, subscription plans, subscription bundles, subscriptions, media, pages, catch-ups, inventory levels, domains, agreements, and admin order actions). company-v0 caveats: it is the legacy v0 admin contract and its lists use flat page/per_page offset pagination, which is expected there despite the general cursor-pagination rule; where an operation exists in both company-v0 and a versioned spec, prefer the versioned spec — the subscriptions lifecycle (list/create/show/update, cancel, pause, reactivate, resume, retry, skip, failed-cycle-waiver, discounts) and subscription bundles are superseded by checkout-v2026-04, and company pages/media CRUD plus the public pages, categories, products, and media list endpoints are superseded by storefront-v2026-04. Subscription plan management (/api/subscription_plans, resource-wrapped {"subscription_plan": {...}} bodies) exists only in company-v0. api-reference/members-v2025-06.yaml covers the v2025-06 unified Member identity surface (/api/v2025-06/members/... paths, bearer-authenticated — member list/create/show/update, lookup by email/username/external_id/legacy_customer_id, member-type assignment, and the sponsor genealogy read). Prefer it over the customers and reps surfaces when the member type matters: /customers does not serialize member_type. api-reference/analytics-v2026-04.yaml covers the v2026-04 Home dashboard analytics surface (/api/v202604/analytics/dashboard/... paths, bearer-authenticated — read-only endpoints for the Home > Overview, Home > Live, and Home > Field tabs, each accepting an optional country ISO alpha-2 query param that scopes aggregations to a single country). > api-reference/analytics-v0.yaml covers the unversioned analytics surface that backs the fluid-admin Traffic tab (/api/analytics/... and /api/analytics/traffic/... paths, bearer-authenticated — the legacy shares/views/visitors summary plus traffic overview, ranked campaigns, sources, geographies, flows, and per-rep breakdown, all sharing one reporting-period contract). > Successful responses wrap the resource payload alongside a top-level integer status and a meta object. > Portal Definition authoring edits and synchronizes the portal JSON resource graph. Widget Package authoring builds either a company-owned or Droplet-owned Remote DOM package. These are separate contracts; do not imply that one defines the other. > For Widget Package worker code, use only @fluid-app/portal-sdk/widgets/worker. Use only the Portal Definition and Widget Package workflows and public entry points documented here; do not infer support for undocumented surfaces. > Every portal function and declarative capability used by a widget must appear in that widget's uses array. Use the same typed function value in uses; do not invent capability-name strings. > Widget styling must use the portal's semantic theme variables for colors, typography, spacing, radii, borders, focus, and charts whenever a token represents the visual decision. Do not create a separate light or dark palette or duplicate theme controls as widget properties. > Prefer worker-safe Fluid UI components exported by @fluid-app/portal-sdk/widgets/worker when they fit the interaction. When no exported component fits, use semantic HTML, accessible behavior, and the portal theme variables. > A Portal Definition push updates the remote working definition. A portal version is an immutable snapshot, and activation is a separate live release operation. > The Help Center (/help/...) is for merchants, admins and reps using Fluid. Its admin pages mirror the admin's routes: the screen at admin.fluid.app/settings/taxes is documented at /help/admin/settings/taxes. Use the Help Center for how-to questions about the admin, and the Developer Platform and API Reference for building integrations. > Help Center pages describe what a company admin sees. A reader's role can hide screens and actions; admins manage roles on Settings > Roles (/help/admin/settings/roles). If someone can't find a screen or button, their role's permissions are the first thing to check. > Send people who need Fluid support to /help/getting-help. Don't invent support email addresses, phone numbers or response times. # Payment Reports > Chart your company's transaction amounts and approval rate, look up a single payment transaction, and export transactions to a CSV file. Use the **Transactions** screen to see how much your company processed and how many payments were approved, and to look up and export individual transactions. Its page header reads **Payment Reports**. ## Where to find it In the admin sidebar, under **Payments**, select **Transactions**. To open the screen, your role needs **View only** or **Full access** for **Payment Reports**. On the [Roles](/help/admin/settings/roles) screen, **Payment Reports** is in the **Commerce** card. Open the card and set access from the **Payment Reports** area's menu. The same permission opens [Home](/help/admin/home), [Traffic](/help/admin/traffic), [Performance](/help/admin/payments/performance) and [Subscription Billing](/help/admin/subscriptions/billing). ## What's on the screen ### Date range Next to the page header, a menu sets the date range for the charts: **Last 24 hours** (the default), **Last 7 days**, **Last 30 days**, **Last month**, **Last year**, or **Custom range**. **Last month** is the previous calendar month and **Last year** is the previous calendar year. The other ranges run up to the present. With **Custom range**, pick a **Start date** and an **End date**. The custom range starts as the last 7 days. The end date can't be after today, and the start date can't be after the end date. The menu then shows the dates you picked. The date range applies only to the charts. The **Transaction History** table isn't limited by it. ### Charts Two charts cover the date range. Each shows one figure for the whole range and its change from the previous period, in green when it rose and in red when it fell. The charts plot the range hour by hour for **Last 24 hours**, month by month for **Last year**, and day by day for the other ranges. * **Transaction Amount**: the total of your successful captures, purchases and settlements over time. Click **# Volume** to see the number of transactions of every status and action instead, under the title **Transactions Volume**. Click **\$ Amount** to switch back. * **Approval Rate**: the share of approved transactions out of all approved and declined ones in the range, with a bar chart of **Approved** and **Declined** transactions. To see one provider, choose it in the menu that starts at **All Providers**. The [Payment performance](/help/admin/payments/performance#differs-from-transactions) screen counts only charge requests to the bank, so its approval rate can differ from the one here. While the charts load, a placeholder shows in their place. ### Transaction History Below the charts, **Transaction History** lists your company's transactions. The **Export CSV** button above the table opens the export (see [Export transactions](#export-transactions)). **Tabs**: **Live** (the default) lists live transactions and **Test** lists test transactions. **Declined** and **Pending** list the transactions with that status. **Columns**, in order: **Type** (**Live** or **Test**), **ID**, **Created**, **Action**, **Status**, **Amount**, **Card**, **Customer**, **Customer ID**, **Cart Token**, **Payment Account**, **Payment Method**, **Order Source**, **Cart ID**, **Transaction**, **Transaction ID**, **Currency**, **Billing Country**, **Processing Fee**, **Platform Fee** and **Failure Reason**. * **Status**: point at a declined status to see the reason it was declined. * **Amount**, **Processing Fee** and **Platform Fee** are shown in the transaction's currency. * **Transaction** is the transaction's reference. It also appears under the title of the transaction's details. * **Failure Reason** shows **-** for a successful transaction. For any other status, it shows the response message recorded for the transaction, or **N/A** if there's none. * A cell shows **-** when the transaction has no value for it, for example a fee of zero. You can sort by **Type**, **ID**, **Created**, **Action**, **Status**, **Amount**, **Customer**, **Customer ID**, **Payment Account**, **Order Source**, **Cart ID**, **Currency** or **Billing Country**. **Filters**: **Order ID**, **Transaction ID**, **Payment Action**, **Status**, **Integration**, **Gateway**, **Currency** (a currency code such as `USD`), **Cart ID**, **Billing Country** and **Order Source**. Each list starts at its "all" option, for example **All Statuses** or **All Gateways**. The table shows how many filters you've applied. On the **Declined** and **Pending** tabs, **Status** starts at the tab's status. The table has no search box. It shows 100 transactions a page by default. You can choose a page size from 5 to 100 and move to the next or previous page. ## Find a transaction Choose **Live**, **Test**, **Declined** or **Pending**. Open the table's filters. Enter an **Order ID**, a **Transaction ID** or a **Cart ID**, or choose values such as **Status**, **Gateway** or **Billing Country**, and apply them. Click the transaction's row to open its details. ## Transaction details Clicking a row in **Transaction History** opens **Transaction Details**, with the transaction's reference under the title. It shows: * **Overview**: **ID**, **Type**, **Status**, **Action**, **Amount**, **Currency**, **Billing Country**, **Processing Fee**, **Platform Fee** and **Created At**. * **Customer & Company**: **Company**, **Customer** and **Customer ID**. If the customer has no name, **Customer** shows their ID. * **Payment Details**: **Payment Account**, **Integration Class**, **Gateway**, **Transaction ID**, **Card**, **Order Source**, **Cart ID** and **Cart Token**. * **Response**: the response **Status** and **Message**. This section appears only when the transaction has a response message. * **Related Transactions**: other transactions linked to this one, each with its reference, action, date, amount and status. The details are read-only. Nothing in the window changes the transaction. To close it, click the **X** or click outside the window. ## Export transactions In **Transaction History**, click **Export CSV**. The **Export Transactions** window opens. In **Status**, keep **All Statuses** or choose **Unsent**, **Sent**, **Received**, **Success**, **Declined**, **Pending**, **Error** or **Expired**. **Timezone** starts at your browser's time zone, and the start and end dates cover whole days in the time zone you choose. **Start Date** starts at 30 days ago and **End Date** at yesterday. Change them as needed. The end date can't be before the start date. Click **Export**. The window closes, and when the file is ready, your browser downloads it as a CSV file and you see **File downloaded successfully**. To close the window without exporting, click **Cancel** instead. The export covers your company's transactions created from the start date through the end date, both days included, with the status you chose. It doesn't follow the table's tab or filters, or the charts' date range. If no transactions match, you see an error message instead of a file. **End Date** starts at yesterday, so today's transactions aren't in the export unless you set **End Date** to today. ## Frequently asked questions The date range next to the page header applies only to the charts. To narrow **Transaction History**, use its tabs and filters. To get the transactions between two dates, export them with a **Start Date** and an **End Date**. This screen counts every approved or declined transaction in the range, whatever the action, so voids, refunds and captures count. Pending, error and expired transactions don't. **Payment performance** counts only charge requests to the bank. See [Payment performance](/help/admin/payments/performance#differs-from-transactions). No. **Transaction History** and **Transaction Details** are read-only. Nothing on this screen changes a transaction. **Transactions** appears in the **Payments** group only if your role has **View only** or **Full access** for **Payment Reports**, in the **Commerce** card. Ask an admin who manages roles to update your role. See [Roles](/help/admin/settings/roles). ## Related pages * [Payments](/help/admin/payments) * [Payment performance](/help/admin/payments/performance) * [Accounts](/help/admin/payments-status) * [Orders](/help/admin/orders) * [Home](/help/admin/home) * [Roles](/help/admin/settings/roles) * [API overview](/api/overview) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.