Address Expiration

Overview

Meaning and scope

Address expiration is the point after which a payment address issued for a specific session should no longer be used or credited under the original payment terms. It is common in temporary invoice and white-label flows where the address is tied to a rate, amount, or lifetime.

Mechanism and operation

Address Expiration limits the usable lifetime of a session-specific payment destination. In OxaPay white-label payments, the generated address is valid only for the configured lifetime, and the documentation warns that funds sent after expiry can be unrecoverable. The address lifetime is connected to payment-session context such as Expected Amount, pay currency, network, and quote. A price quote controls rate validity, while address expiration controls whether the destination remains recognized for that session. Products can align these timestamps, but systems should store them separately. A static address is designed for reuse and is disabled through a separate lifecycle action.

Practical payment example

An invoice address is no longer offered for new orders after the quote expires, but the monitoring system still handles late incoming funds.

Operational checks

A temporary address normally expires automatically according to the payment configuration. Interfaces must remove or clearly mark expired instructions and prevent copyable stale QR codes. Expiration policy should be enforced consistently across API, web interface, QR code, and support tools. Cached pages and browser history can continue exposing old instructions after the backend has expired them.

Distinctions and limits

After expiration, the same visible destination should not be assumed to retain the original rate or automatic matching behavior. Late transfers should enter an exception workflow with chain evidence, session timestamps, and recovery rules rather than being silently credited or discarded.

Related reading

Related definitions: Expected Amount, Quote Expiration.