Articles
Long-form explanations that live inside the docs but aren’t part of the integration path. Collapsed in the sidebar by design — an integrator never has to scroll past them.
Product documentation answers “how do I build this?”. Articles answer the questions that come before and around it — how crypto settlement finality actually works, who pays a network fee and why, what transaction screening does. They live under /docs/articles/ so their weight consolidates with the documentation, and they stay collapsed in the sidebar so they never sit between an integrator and an endpoint.
The rules an article follows
- It answers one question, and it is the page that owns that question.
- Every fact in it is checkable against a Concepts page, the API, or the specification — no article introduces a claim the product doesn’t back.
- It ends with the next step: the concept page that goes deeper, or the commercial page that owns the intent.
- It never restates a guide. If an article needs a procedure, it links to the guide that owns it.
Meanwhile, the pages that answer most questions
When you can ship, when you can withdraw, and what happens during a reorganization.
The two components, the four payer configurations, and how to quote exact numbers.
What runs on every transaction regardless, and what your level actually changes.
Two status axes, the full transition set, and the amount edge cases.
Something unclear? payments@suward.com — we treat every integration question as a documentation defect.