v6.9.0 - 2026-08-31

release notes for voltage payments api release v6 9 0 , published 2026 08 31 treasury movements are available through post /organizations/{organization id}/environments/{environment id}/treasury movements the endpoint uses the existing payment request contract for sends and receives, requires write authorization, and is disabled by default until voltage enables it for the organization treasury movements do not incur processing fees payment responses, payment webhooks, and payment history filtering now expose a payment category existing and standard payments use standard ; treasury movements use treasury payment history csv output advances to schema version 2 and includes payment category every webhook delivery now includes the additive x voltage webhook id header use it to identify the originating webhook registration when routing callbacks or selecting a shared secret; existing hmac verification and callback bodies are unchanged any amount bolt11 and bip21 receive requests with a nonzero receive processing fee are now rejected before invoice or payment uri generation fixed amount receives, zero fee receives, previously generated receives, and treasury movements are unaffected