IPv4 Purchase Payment Process: Escrow, Transfer Confirmation and Release of Funds

An IPv4 purchase does not normally move directly from invoice to seller payment. Before a company buys IPv4 addresses, it should understand how funds are secured, what confirms that the transfer has completed, and which event authorizes the escrow provider to release payment.

The IPv4 purchase payment process is a sequence of controlled payment and transfer steps used to protect both buyer and seller during an IPv4 acquisition. It connects invoice payment, escrow funding, RIR approval, registry confirmation, and final fund release so that payment is not completed before the agreed transfer conditions have been met.

What are the main purchase payment stages?

The exact workflow depends on the broker, escrow provider, RIR, and transaction agreement. However, the main purchase payment stages normally follow the same logic:

1. the buyer accepts the purchase terms;
2. an invoice or payment instruction is issued;
3. the buyer sends the agreed amount to escrow;
4. escrow confirms receipt of the funds;
5. the seller begins or continues the RIR transfer;
6. the RIR reviews and completes the transfer;
7. the agreed completion evidence is checked;
8. escrow releases the funds to the seller.

A common escrow workflow follows this structure: the buyer deposits the purchase price into escrow, the seller submits the RIR transfer after the funds are confirmed, and payment is released after the registry update confirms that the addresses have moved to the buyer.

How does the escrow payment process work?

The escrow payment process separates the buyer’s payment from the seller’s access to those funds. The money is held by an agreed intermediary until the release conditions in the transaction are satisfied.

The purchase escrow stages should define:

• the amount to be deposited;
• the payment method and currency;
• the deadline for funding;
• who pays escrow and banking fees;
• what evidence confirms receipt of funds;
• what event authorizes release;
• what happens if the RIR rejects or delays the transfer.

Payment deadlines depend on the marketplace, broker, seller, and transaction agreement. A five-business-day invoice window may apply in some transaction models, but it should not be treated as a universal IPv4 market rule.

What should happen before the seller receives payment?

A secure transfer payment release process should distinguish between three events: submission, approval, and completion.

A transfer request being submitted is not the same as the resources being transferred. This distinction is important when defining escrow release conditions.

ARIN, for example, requires both source and recipient organizations to submit transfer requests for an 8.3 transfer. ARIN links the requests, processes them separately, collects applicable fees, and completes the transfer only after its requirements have been met.

What counts as transfer confirmation for payment?

The agreement should define the exact transfer confirmation payment trigger. A practical confirmation point is the RIR registry update showing that the resources have been transferred to the recipient.

After a RIPE NCC transfer is registered, the resource information is updated in the RIPE Database and both parties receive confirmation. Complete intra-region transfers can often be processed within one or two business days when all required information is available.

For an ARIN transfer, completion occurs after the applicable fees and documentation, including an RSA where required, have been received and the registry has completed the transfer.

This type of transfer confirmation escrow arrangement reduces ambiguity because the release event can be checked against registry records rather than relying only on an email from one party.

When should escrow funds be released?

The escrow funds release should occur only after the conditions written into the transaction agreement have been satisfied.

Those conditions may require:

• confirmed RIR completion;
• registry records showing the buyer as the recipient;
• completion of required contracts or fees;
• confirmation that the exact agreed prefix was transferred;
• resolution of any transaction-specific exceptions.

A common workflow therefore uses payment after transfer, meaning that the buyer funds escrow before the transfer starts but the seller receives those funds only after the agreed transfer milestone has been confirmed.

This does not mean every IPv4 transaction must use identical release conditions. The buyer, seller, broker, and escrow provider should establish them before money is sent.

What happens if the RIR transfer is delayed?

Escrow terms should explain what happens when the transfer remains open longer than expected. The parties should know whether funds stay in escrow, whether either party can cancel, and what evidence is needed to terminate the transaction.

RIR processing time can vary significantly. ARIN transfers may take several weeks depending on documentation and policy review, while complete intra-region RIPE NCC transfers can often be processed within one or two business days.

The payment agreement should therefore avoid assuming that every registry follows the same timeline.

What should buyers verify before funding escrow?

Before sending money, the buyer should confirm:

• the exact IPv4 prefix;
• the registered source organization;
• the purchase amount and transaction fees;
• the escrow account and beneficiary instructions;
• the relevant RIR transfer path;
• the release trigger;
• refund or cancellation conditions.

The buyer should also verify that the block is eligible for transfer and that the transaction documents match the commercial quote. These checks form part of the broader acquisition process, not merely the payment step.

How can you make the payment process easier to verify?

Ask IPv4 Online to align the invoice, escrow instructions, transfer milestone, and release condition before funds are sent. A buyer should be able to point to one specific event that authorizes payment release.

Keep the payment sequence separate from the registry sequence. Escrow can protect funds, but the agreement still needs to define what happens if verification fails, the transfer is rejected, or closing takes longer than expected.