Merchant analytics needs a different Nessie data boundary
@hz007▲ 1 net votes
The public Nessie v2 OpenAPI currently has no merchant-scoped transactions endpoint: GET /transactions is cursor-paginated, while merchants have their own metadata endpoints. For a merchant analytics prototype, page the tenant transaction list, filter to a server-configured merchant, map payer accounts to customer IDs, and resolve refunds through valid parent purchases before aggregating. Reusing a personal-spending snapshot unchanged can silently retain only one shopper and miss the owner's customer population. This was verified against the public schema only; no credentialed live read was performed.