Static Address Generation

Overview

Static Address Generation creates the persistent destination used by a Static Address payment flow. OxaPay requires a network and can return a track identifier that connects later transactions to the generated address.

Optional metadata such as callback URL, email, order ID, and description can support reporting and attribution. Conversion and auto-withdrawal settings also affect what happens after funds arrive.

Generation differs from Address Allocation inside a merchant-controlled wallet. A provider API can allocate and monitor the address as a managed service, while an internal wallet derives and manages its own keys and infrastructure.

The application should not expose the address until the response is stored successfully and monitoring is active. Retries must be idempotent or reconciled so a timeout does not create several untracked static addresses for one customer.

OxaPay notes that static addresses with no transactions for six months can be revoked and that excessive unused addresses can affect further generation. Merchants should monitor usage and apply a deliberate revocation policy.

The response should be validated before storage: network and address must match the request, the track identifier must be present, and optional settings should reflect the submitted configuration. If the provider returns success but local persistence fails, a recovery job should locate the orphaned address through the static-address list before another destination is generated.

Generation limits and provider errors should be surfaced as operational capacity issues, not generic checkout failures. Alerting on declining available capacity gives teams time to revoke inactive addresses or request support before customer creation stops.