Understanding the Dispute Freeze Window for Prepaid Accounts

Formal payment processor disputes trigger an immediate freeze window on the IOSOR ledger. During this period, your accessible funds drop automatically, and dropping below the USD 20 balance floor will instantly halt your routing capabilities. To keep your system running, you must resolve the claim promptly or add funds to restore active operations.

Defining the Dispute Freeze Window

When a buyer initiates a formal dispute via a payment processor, the IOSOR ledger triggers an immediate freeze window. This is not a background ops pause but a visible ledger state where the disputed funds and associated credits are isolated. During this window, the console reflects a 'Locked' status on the specific transaction IDs. This ensures that the prepaid balance remains static while the arbitration process occurs.

Ledger Locking and the USD 20 Floor

The IOSOR environment operates on a strict prepaid model. To maintain service continuity, a USD 20 prepaid floor is required for active routing. When a dispute enters the freeze window, if the remaining accessible balance falls below this USD 20 floor, all outbound activity ceases. The ledger does not allow 'netting' of disputed funds against new deposits. Buyers see a clear distinction in the dashboard between 'Available Balance' and 'Disputed Hold'.

Impact on JIT Number Assignments and MRC

During a dispute freeze, the ability to trigger JIT (Just-In-Time) number assignments is suspended if the hold impacts the required MRC (Monthly Recurring Charge). Since IOSOR does not maintain a pre-allocated stock of numbers, every E.164 assignment requires an active, unfrozen balance to secure the resource. If a buyer attempts to provision a new 10DLC or toll-free identity while the freeze window is active, the API will return a 402 Payment Required error.

Traffic Constraints and Soft Review Thresholds

The freeze window also intersects with volume scaling. For accounts approaching a soft review near USD 1,000/month, a pending dispute can accelerate the review process. IOSOR monitors the ratio of successful DLRs to disputed transactions. If the freeze window covers a significant percentage of the monthly spend, the system may limit concurrent OTP sessions to protect the integrity of the route.

Documentation and Resolution Paths

To resolve a freeze window, buyers must provide evidence of authorization for the disputed transactions. This includes logs of SMS delivery, STOP command handling, and webhook receipts.

Related: Unfreeze is not bonus balance · Dispute Holds vs OTP Abuse Velocity Limits · Prepaid hold before first debit.

Start with IOSOR

To verify which assets are currently isolated, navigate to the IOSOR billing dashboard and inspect the active dispute ledger state. Here, you can track exactly which JIT number assignments and MRC-dependent routing paths are temporarily locked rather than guessing about background operations. If your outbound traffic is blocked, check the real-time webhook logs to confirm whether a formal freeze window has been triggered.

IOSOR takeaway

This article demonstrated that a dispute freeze window on IOSOR is a transparent, ledger-level event that directly restricts specific operational capabilities, such as JIT number provisioning and MRC-linked routing. Unlike silent administrative pauses, this visible isolation ensures that both buyers and compliance teams have clear visibility into which funds and routing assets are locked during the resolution process.

Do monitor your active ledger states and webhook notifications to immediately identify when a dispute triggers a freeze. Don't assume your outbound routing or JIT assignments are experiencing a generic system error when a formal payment dispute has actively locked your transaction capabilities.