Uncovered prefix: reject honestly, do not silent-burn

An uncovered prefix is a hard fail path. No zone and no capped WORLD attempt means stop, return money cleanly, and say rejected. Silent accept that later looks like sent is prepaid burn finance cannot defend.

IOSOR is white-label prepaid. Fund the wallet, hold before debit, buy JIT numbers only after assign. Floor USD 20; soft review near USD 1,000/month turns silent coverage fails into night reconciliations. Quote: Check coverage before you quote volume. Gate: Zone vs WORLD gate before production. Money: Hold fail auto-refund and status truth.

Uncovered means stop, not hope

Decide coverage before work. Resolve to a named zone, an explicit WORLD fallback rule, or neither. Neither means reject. Do not queue the unit or wait for ops chat to invent coverage. Accepted on a never-underwritten corridor makes later undelivered look like product fraud. WORLD fallback is a capped exception — not “try anyway.” If production forbids WORLD on that corridor, uncovered equals reject. Pair with the zone gate so prod keys never treat missing zones as Live.

Hold, release, and refund on a dead corridor

Every billable intent reserves prepaid before work — Prepaid hold before first debit. Prefer reject at validation: no hold or immediate release with rejected status. If a hold is open and fulfillment cannot proceed, release the full reserve. Settled amounts that must reverse get an explicit refund linked to the intent.

Never leave a reservation open “until someone finds a route.” Open money without a path is silent burn. Fail playbook: Hold fail auto-refund and status truth.

Never paint fake sent on uncovered traffic

Rejected is not undelivered, expired, or queued. Fake sent, fake delivered, or Live on an uncovered prefix destroys ledger trust. Labels: undelivered, rejected, expired — this fail path must feed those honest outcomes. Client errors stay brand-safe (no zone / blocked fallback), never upstream brands. Same idempotency key reuses the original money result — no second burn hoping coverage appeared.

Status truth buyers and finance share

One export row per intent: destination class, coverage decision, hold/release/refund amounts, timestamps, correlation ID. Soft USD 1,000/month makes corridor burn visible; USD 20 funds the reject-path pilot.

Buyer checklist for uncovered-prefix honesty

1. Unmatched prefix rejects at validation when WORLD is forbidden?
2. Open holds on coverage fail release with exportable status?

Start with IOSOR

Audit your routing rules in the console to ensure any destination prefix without an explicit underwritten zone or active fallback is set to reject immediately at the validation gate. Configure your webhook listener to capture explicit rejected status events and instantly release any prepaid hold associated with that correlation ID. Review your ledger export settings to confirm that uncovered traffic exports honest status labels rather than queueing indefinitely or marking items as fake sent.

IOSOR takeaway

Accepting traffic on uncovered destination prefixes burns balance, damages ledger trust, and creates false delivery expectations. Rejection at the API gate protects your balance holds and maintains accurate status reporting across buyer and finance workflows.