Access, then the USD 20 prepaid floor

Apply approval grants account access. The next commercial step is a funded prepaid wallet so holds can cover pilot traffic. That floor starts spend control — not a membership fee and not proof that Live send is allowed.

Teams often misread the first top-up as go-live. Access plus balance only means you can practice hold and debit in a controlled pilot. Production send still needs sandbox-vs-Live keys, catalog honesty, and Launch runway greens.

Say the sequence in every kickoff: access → wallet floor → hold-before-send drills → then runway. Skip the middle and finance will treat messaging like invoice-later SaaS.

Fund the wallet after access, not before identity

Do not ask for prepaid balance while apply or KYC is still open. Money without access creates orphan top-ups and confused ledgers. Close access first, then invite the public minimum top-up so the wallet opens cleanly. Once access lands, the floor starts a pilot wallet — enough to exercise holds without pretending volume review is finished. Soft spend governance near larger monthly reviews stays separate; day-1 is wallet truth, not a sales package.

The floor is a wallet start, not an entry fee

Call the public minimum what it is: a wallet floor so a pilot can try holds and debit. It is not a license fee, not a seat charge, and not a promise of inbox delivery. Framing it as an entry tax trains buyers to expect postpaid courtesy after they pay. IOSOR commercial story is prepaid: balance covers the hold before the send leaves. The floor makes that story operable for a first week.

Wallet ready is not production send

A green wallet balance does not flip catalog Live, rotate production keys, or clear vault gates. Sandbox credentials can still be the only keys in the console. Live tiles may still sit in setup. Run a deliberate pilot week: open hold, send a controlled message, confirm debit and DLR correlation, then stop. Treat that as wallet proof. Keep production corridors behind Launch checks and key cutover. Brief sales that funded ≠ Live.

Keep spend control next to the floor story

Spend control explains how holds, thresholds, and volume review govern growth after the floor. Pair those materials when finance asks what happens after the first top-up. Do not invent unlimited send because the wallet shows a positive balance.

Trust copy also matters: never promise outcomes the ledger cannot prove. The floor starts the ledger; it does not rewrite delivery SLAs.

Related ops paths

• Wallet pilot week: hold and debit truth
• Prepaid messaging spend control
• Prepaid truth: what IOSOR never promises

Start with IOSOR

Once KYC verification clears and console access is granted, submit the USD 20 top-up to initialize your pilot wallet. Verify in the dashboard that the balance is credited as working wallet funds rather than an administrative fee. Run a single sandbox payload test to observe real-time hold authorization and debit reconciliation before requesting production status.

IOSOR takeaway

Treating the USD 20 floor as a working wallet balance ensures clean ledger accounting and aligns internal teams on what access actually grants. The initial balance funds hold and debit cycles during initial testing; it does not purchase an enterprise license or bypass operational setup.

Do complete identity verification before initiating top-ups to prevent orphaned account balances. Don't assume a funded wallet automatically unlocks production traffic or clears catalog gating.