Move live traffic onto prepaid without naming rails

Cutover onto IOSOR means moving live send and DLR into a prepaid wallet — not explaining which upstream pipes you used to call. Buyer-facing runbooks, finance exports, and status copy stay white-label. Name the old path only in a sealed ops note; never in tickets buyers can read.

The job is a controlled move: prove spend control on prepaid, cut keys from sandbox to Live, and keep promises honest. Brand names of pipes you leave mean the cutover failed even when DLR looks green.

Map the cutover without naming old pipes

Build a one-page cut map: which products move first, which corridors stay paused, and which ledger owns holds after go-live. Replace every brand label in that map with IOSOR product names only. Sealed ops may keep a private alias table; public tickets must not.

Walk support macros and status pages the same day. A single leftover brand name in an auto-reply turns a clean prepaid move into a disclosure incident for the buyer.

Prove prepaid spend control before Live keys move

Open the prepaid wallet path and send a low-volume proof with spend caps visible to finance. Confirm holds open and close on the IOSOR ledger before any production key leaves sandbox. Do not move Live traffic while spend control is still “coming next week”.

Export the proof window so finance can cite the same rows ops used. If the export and the dashboard disagree, stop the cutover — you do not yet have a prepaid truth both teams can share.

Rewrite buyer-facing copy before volume rises

Strip migration notes, onboarding decks, and portal help of any upstream brand. Rewrite to prepaid truth: wallet floor, hold versus debit, and what IOSOR never promises. Ship the copy change in the same change window as the key cutover so buyers never see two stories.

Keep engineers from pasting old portal screenshots into buyer Slack. Screenshots are the fastest way a retired brand name reappears after the cut map looked clean.

Close the old path after one green pilot window

Run one named pilot corridor on IOSOR Live with DLR and wallet aligned. Only then revoke the old credentials and archive the sealed alias table. Dual Live keys without a dual-write clock are a different hazard — skip them.

If the pilot ledger drifts, roll back to the sealed map and reopen the proof — do not improvise a second Live path while buyers are already reading prepaid copy.

Related ops paths

• Prepaid messaging spend control
• Sandbox vs production keys cutover
• Prepaid truth — what IOSOR never promises

Start with IOSOR

Draft the sealed cut map, scrub buyer-facing copy, and run a prepaid spend proof on one corridor. Cut Live keys only after finance signs the export. Archive old credentials after that pilot window stays green for a full quiet shift.

IOSOR takeaway

A prepaid cutover is white-label by design: move spend and DLR onto IOSOR without naming the pipes you leave. Prove wallet control, rewrite buyer-facing copy, then cut keys — never ship Live volume while old-path brand names still appear in tickets a buyer can read.

Do not treat sandbox reach as production coverage. Do publish the sealed map and the spend export before the key swap.