Static Address Revocation

Overview

Static Address Revocation changes the provider or merchant processing state of a Static Address. OxaPay provides an authenticated revoke endpoint that accepts the address and disables further automatic crediting for that static wallet.

Revocation differs from Address Expiration. Temporary payment addresses usually expire according to a session lifetime, while static addresses remain reusable until an explicit or inactivity-based lifecycle action occurs.

The application should stop displaying the destination, mark its assignment inactive, and prevent new invoices or customer instructions from referencing it. Historical payments and audit records must remain available.

Blockchain networks do not understand the provider’s revoked status. A payer can still send to the address, and the transaction can confirm. Monitoring should detect such transfers and route them to manual investigation rather than ignoring them.

Revocation should be idempotent and require authorization, reason, timestamp, and affected customer or order records. Replacing the address should include secure reassignment and customer communication to reduce repeated late payments.

Revocation should also update callbacks, customer profile, address inventory, and support documentation. If only the provider state changes, the merchant application can continue presenting a destination that no longer credits automatically. Periodic comparison with the provider’s static-address list helps detect local and remote lifecycle states that have drifted apart.

A revocation confirmation should be stored from the provider, and repeated revoke requests should return a stable result. If local and provider records disagree, the address should remain blocked from customer use until reconciliation completes.

A customer-facing replacement process should verify that saved payment templates and recurring instructions are updated, not merely the current checkout page.