Can each merchant shape its own views?
Views are built from any object table on the platform, covering transactions, orders, contracts, tokens and operations, with the columns, filters and sort order each merchant chooses. Each view carries its own visibility rule, staying private, shared with named colleagues, or opened to a whole team. Saved searches attach to the view they belong to, so a complex filter combination survives the next refresh.
In detail
Yes. Views are built from any object table on the platform, covering transactions, orders, contracts, tokens and operations. Each merchant chooses the columns, the filters and the sort order that match how its teams work.
Sharing and visibility
Each view carries its own visibility rule. It can stay private, be shared with named colleagues, or be opened to a whole team. Saved searches attach to the view they belong to, so a complex combination of filters survives the next refresh and does not need to be rebuilt.
Language and formats
Column names, field labels and view titles can be renamed to match a merchant's internal nomenclature. A merchant that calls its transactions operations or tickets sees those words. Each column type carries its own display options for dates, amounts, currencies and statuses, and numeric columns can carry a footer calculation such as a sum or an average.
What it means for you
You ship the canvas, and your merchants make it theirs. Requests for custom reports to your team drop, because finance, operations and support teams can build the views they need themselves. The underlying data does not change, only the way each team reads it, and exports built from a view follow the same structure.