Developer Docs v2026.8

📗 Eleven New Guides

Category: Documentation

Every guide was diffed against the docs tree and the API section list. The gaps were not edge cases: a partner could not find out how to get a terminal shipped, how to search a transaction, or how to read the monthly report they are asked about every month.

• Online payment link — the guide the whole online path hangs off, starting where the work starts: an online store with verified domains, then a PaymentPage terminal, then the order
• Customer identification — the token that arrives by webhook on card tap, and the short window it gives you to price an order for a returning customer
• Tokens — the three enforcement flags, expiry, and re-authorisation
• Terminal logistics — ordering and returning terminals
• Transactions and reports — including what net sales, charges, payout, “from last period” and “unsettled from period” each mean
• API conventions — what holds across every endpoint, including the pagination nobody had written down
• POS templates, AI merchandising, B2B invoices, ESC/POS printing, and device registration

🧾 B2B Invoices

Category: Documentation

Invoicing was a row in the payment methods table and nothing else, so the one method a B2B buyer expects had no path to follow.

• Activation, the company and billing blocks a card payload does not carry, and the invoice terms
• What comes back: bankgiro and OCR for a domestic transfer, IBAN and BIC from abroad
• Crediting splits in two: an unpaid invoice is cancelled with one call and the credit is raised for you; only a paid one takes a return order. Asking for the wrong one earns OR_0035
• bankgiro and ocr added to the Initiate Payment reference — they arrive in every invoice response

🖨️ ESC/POS Printing

Category: Documentation

• Documents the UTF-8 opt-in contract: one field on the print request buys up-front validation and consistent output across current and legacy terminals
• Per-size line budgets, the supported command set, QR and image encoding, and the error codes
• A worked receipt whose base64 is generated by the code printed above it, with real Swedish characters
• A preflight validator that catches the three things that break integrations: an out-of-contract command, non-UTF-8 text, and an over-long line

🐛 Fixed — The Order Path

Category: Documentation

Eighteen guides documented POST /merchants/:merchantId/orders, which 404s. The merchant travels in the MERCHANT-ID header and the path is POST /orders.

• Four path shapes were wrong, not one: orders, order status, order tokens, and payments. All four corrected
• Merchant-scoped configuration endpoints — stores, terminals, tips, notifications, payment methods — are genuinely merchant-scoped and are untouched
• API conventions now states that the merchant is a header, not a path segment, and that the 404 says nothing about path shape
• amount.total is the unit price, not the line total. The parameter table said “Total line amount” and the calculation section below it already disagreed. Invisible until a cart has a quantity above one, so the new example carries two lines and a quantity of two
• Terminal registration removed from guides that told developers to register terminals they already have