Address Allocation
Pronunciation: AD-dress al-uh-KAY-shun
Also known as: Payment Address Allocation, Deposit Address Allocation
Definition
Address allocation is the controlled selection of an available blockchain address or derivation index for a payment, customer, account, or operational purpose. It occurs before the address is assigned or displayed and must prevent duplicate use, chain confusion, and derivation gaps. Allocation can come from an address pool, deterministic wallet branch, provider API, or custody system.
Overview
Meaning and scope
Address allocation is the controlled selection of an available blockchain address or derivation index for a payment, customer, account, or operational purpose. It occurs before the address is assigned or displayed and must prevent duplicate use, chain confusion, and derivation gaps. Allocation can come from an address pool, deterministic wallet branch, provider API, or custody system.
Mechanism and operation
Address Allocation chooses which destination resource will be used next. In a deterministic wallet, a service can derive public receiving addresses from an extended public key without exposing the private keys needed to spend funds. Allocation reserves or selects an address from the available inventory, while assignment binds that address to a specific customer, invoice, or business record. Network, asset, account branch, address type, and derivation path must be stored with the allocation. Unused allocations need an expiry or release rule, but previously exposed addresses should not be recycled casually. A payer can retain old instructions and send later.
Practical payment example
A merchant allocates a unique deposit address for each customer and records the customer-to-address mapping before accepting incoming transfers.
Operational checks
Systems should balance inventory efficiency against late-payment and attribution risk. Allocation should also preserve the selected Address Format so monitoring software knows how to decode the resulting destination. Allocation services should operate independently from spending keys wherever possible. An extended public key or provider API can generate receiving destinations while private keys remain in a more protected system.
Distinctions and limits
Two simultaneous checkout requests should not receive the same address unintentionally unless deliberate reuse is part of the product. An address cannot be safely interpreted without the context that determines how it is monitored and which wallet controls it.
Related reading
Related definitions: Address Assignment, Address Format.
Example
A merchant allocates a unique deposit address for each customer and records the customer-to-address mapping before accepting incoming transfers.
Comparison
Two simultaneous checkout requests should not receive the same address unintentionally unless deliberate reuse is part of the product. An address cannot be safely interpreted without the context that determines how it is monitored and which wallet controls it.
Key Takeaway
Address allocation selects a unique receiving destination under controlled wallet and network context before it is assigned to a payment or customer.
Sources
- BIP 32: Hierarchical Deterministic Wallets — Bitcoin Improvement Proposals (2026-08-02)
- OxaPay API Reference: Generate Static Address — OxaPay (2026-08-02)
- OxaPay API Reference: Static Address List — OxaPay (2026-08-02)