v6.8.0 - 2026-08-20

release notes for voltage payments api release v6 8 0 , published 2026 08 20 added configurable processing fees for supported sends and receives, with separate send basis points and receive basis points rates wallet policies can override the wallet's current line of credit rates, including an explicit zero rate rates are fixed when a payment starts fixed amount receive requests now include the configured receive processing fee in the amount presented to the payer submit only the intended principal the api calculates the fee and includes it in the generated payment request, while requested amount remains the principal on sends, the processing fee is charged to the sending wallet in addition to the principal and network fee payment responses and webhooks now expose optional top level processing fee terms, including the snapshotted rate and server calculated amount use the returned amount when displaying the fee these terms are omitted for fee free payments and historical payments whose original terms cannot be reconstructed added an optional payment breakdown separating principal, network fees, and processing fees payment level breakdowns aggregate partial receives; payment scoped wallet ledger entries provide settlement details for cross currency payments, use the returned breakdown rather than recalculating fees from the displayed principal provisional breakdowns can change as wallet settlement finalizes conversion and rounding billing line items now expose optional processing fees totals split into send and receive amounts these are informational accounting totals, separate from the bill amount due and voltage's volume fee added payout holdback controls for usd lines of credit retain a percentage of each bill's gross ach payout or enough funds to reach a fixed reserve target in cents held back funds remain in the customer's usd wallets; a holdback is a reserve, not a fee the default none mode preserves full payouts lightning sends now accept an explicit zero max fee to require a zero fee route this limit applies to network/provider fees; configured processing fees are additional added structured context to supported policy and line of credit errors, and recorded payment policy validation failures for subsequent reads fixed browser cross origin access to authenticated checkout settings for configured management origins integration notes use processing fee for fee configuration omitting it leaves the configuration unchanged, an object sets exact rates, and null clears it clearing a wallet override restores line of credit inheritance configuration patch requests return 202 accepted ; wait for reads to reflect the change before creating payments that depend on it processing fee changes through the public line of credit patch route are limited to non mainnet lines of credit mainnet line of credit fee changes require administrator access wallet processing fee overrides support all networks usd payout holdbacks can be updated through the public line of credit route, including on mainnet fee configuration patch bodies reject unknown keys the public field name is processing fee ; earlier development names such as customer fee are not supported aliases