Changelog

Material changes, written for operators.

This record focuses on capabilities and operating behavior that affect customers and integrators. Internal refactors appear only when they change reliability, security, or the user experience.

Reviewed August 20, 2026 Owner: VialAPI Platform team

August 2026

Launch controls and accountable order handling

  • Business payouts now require separate sender evidence and receiving-business confirmation before balances change.
  • Access and support requests receive private references, accountable owners, response targets, escalation, and customer-safe status pages.
  • Public status now reports component health and append-only customer-safe incident updates with an Atom subscription feed.
  • Hosted Store domain, seller-policy, catalog, buyer-access, and recovery controls are code-complete; public launch remains gated on production domains, counsel approval, monitoring, and payment processing.

July 2026

One business workspace

  • Single-account users now enter their workspace directly.
  • Manual ordering and AI-assisted ordering are first-class workspace actions.
  • The owner Businesses directory brings accounts, relationships, people, pricing authority, and channels together.
  • Business-account API documentation now sits alongside the sales-channel API contract.

July 2026

Pricing and commercial controls

  • Versioned price books and customer-safe price sheets keep internal tiers and true cost private.
  • Market research observations remain reviewable and cannot silently change published prices.
  • Commercial agreement versions preserve the exact terms accepted by each party.

July 2026

Integration and operational safety

  • Idempotent order intake, deterministic sandbox outcomes, signed webhooks, and certification paths are documented.
  • Readiness checks now include required jobs, queues, provider configuration, parity, alerting, and active incidents.
  • Error boundaries preserve user work and attach a support reference for correlation.

In development · certification pending

Hosted consumer Store

The non-payment control plane, merchandising, seller-policy, inventory, buyer-access, support, and recovery paths are implemented. Hosted Store remains a not generally available capability: production domains, certificates, counsel, independent monitoring, exact-release evidence, and payment processing remain gated.