Skip to content
VoltageVoltageVoltage Docs

Developer Guide

v6.5.0 - 2026-07-22

Release notes for Voltage Payments API release v6.5.0, published 2026-07-22.

  • A new Checkout API surface supports idempotent merchant session creation for BTC payments and USD line-of-credit-backed payments, browser-safe session retrieval, hosted checkout handoff, origin enforcement, and API-key or bearer-JWT authentication. Checkout flows cover Bolt11, on-chain, BIP21, and Taproot Asset receives, with environment settings available through a read endpoint.
  • Browser Checkout clients can subscribe to server-sent events for session snapshots and payment updates. The release improves event accuracy by projecting from canonical receive events, and browser-safe payment details now include payment-owned amount and requested_amount values when available. Quote-backed session creation also adds validation for amount, currency, denomination, precision, wallet compatibility, and terminal quote failures.
  • Production Checkout rollout remained gated after these changes merged: the production configuration required a matching Terraform IAM change before syncing the Checkout application, and unified production documentation routes remained disabled pending Checkout and shared-gateway health checks. This release note therefore does not claim production availability for Checkout.
  • Organization line-of-credit list and summary endpoints now return active lines by default. Pass include_disabled=true to include disabled records; omitted or false remains active-only. Environment and combined filters are also composed correctly.
  • Line-of-credit list endpoints support optional limit and offset pagination. When pagination is requested, the response is an object containing items, offset, limit, and total; without those parameters, the legacy array response is preserved.
  • The release adds a unified documentation aggregator with /v1/docs and /v1/openapi/docs.json routes, strong ETags, and If-None-Match/304 Not Modified support. Public Payments visibility fails closed so private or ambiguously tagged routes are excluded. Production availability of the unified routes remained subject to the rollout gate above.