Static Address

Overview

A Static Address remains associated with a merchant context across multiple transfers. OxaPay generates a static address for a specified network and links it to a track identifier, with optional callback, email, order ID, conversion, and auto-withdrawal settings.

Unlike a temporary invoice address, the static address is not tied to one expected amount or short lifetime. This makes it useful for recurring deposits, account top-ups, or customers who need a stable destination.

Reuse shifts matching responsibility. Payments can arrive without a unique invoice, so the system may rely on address assignment, amount, memo, reference, customer identity, or an internal ledger to determine the business purpose.

Address reuse can reduce privacy because outside observers can link transfers to the same destination. It can also create accounting ambiguity when several deposits arrive close together. Monitoring should retain transaction-level evidence and never infer order status from balance alone.

Static addresses require lifecycle management through Static Address Generation and Static Address Revocation. OxaPay notes that inactive addresses can be revoked and that merchants should revoke unused addresses to avoid generation limits.

A static-address ledger should track every incoming transfer independently and then post credits to the assigned customer account. The address balance is not an account balance because outgoing sweeps, refunds, and unrelated deposits can change it. Reconciliation should compare transaction-level credits with internal ledger entries and provider callbacks rather than treating the current on-chain balance as authoritative.

Customer account closure should not immediately destroy the address relationship. The destination can be disabled for new instructions while historical ownership and late-transfer routing remain available for the required retention period.