The API reference section reads in a narrow column without a page outline. One
page with a wide table needs a wider column. The page changes only the
width and takes everything else from the section.
{ "schema": "docara.page.v1", "title": "The Payment object", "description": "Demo page: the section sets a narrow column, and a page with a table widens it.", "layout": { "container": {"max": 7} }}
page.md
---
noindex: true
---
# The Payment object
A payment stores the amount, currency, status and change history. All fields
come in the response to payment creation and in notifications.
| Field | Type | Example | Description |
|---|---|---|---|
| `id` | string | `pay_2Hk81` | Payment ID |
| `amount` | string | `1500.00` | Amount with two digits after the point |
| `currency` | string | `RUB` | Currency code per ISO 4217 |
| `status` | string | `succeeded` | `pending`, `succeeded` or `canceled` |
| `created_at` | date and time | `2026-11-02T10:15:00Z` | Creation time in UTC |
| `confirmation_url` | string | `https://pay.acme-pay.example/c/2Hk81` | Payment page for the customer |
How it works
section.json sits in the section folder. Every page in this folder and
its subfolders gets its settings.
The section makes the column narrow (container.max: 4) and turns off the page outline and
the “Previous / Next” links.
The page.json file named after the page changes one setting: the width.
The page still has no outline and no previous/next links: the page did not
touch them.
The order is: the site’s docara.json, then the sections’ section.json files from
outer to inner, then the page’s page.json. Each next file changes
only what it contains.
