Prepaid Sub-Account Provisioning and Spending Limits Playbook

Prepaid Sub-Account Provisioning and Spending Limits Playbook.

Sub-Account Architecture and Isolation

IOSOR sub-accounts function as independent financial and technical silos. When onboarding an enterprise client, navigate to the Sub-Account Manager to generate a unique Account ID. This ID acts as the primary key for all DLR, webhook, and billing events. Ensure that each sub-account is configured with its own dedicated API key set to prevent cross-contamination of traffic. By isolating environments, you ensure that one client's traffic spikes or configuration errors do not impact the broader platform stability.

Configuring Prepaid Balances and Thresholds

Every sub-account requires a minimum USD 20 prepaid floor to initiate service. Navigate to the Financial Ledger tab within the sub-account dashboard to deposit initial credits. Set a soft review trigger at USD 1,000/month to monitor usage velocity. This threshold allows your team to perform a manual audit of traffic patterns before the client scales significantly. Use the automated balance alert system to notify both the client and your internal support team when the balance drops below 15 percent of the total deposit.

Rate Limiting and Traffic Shaping

To maintain platform integrity, apply strict message rate caps at the sub-account level. Navigate to the Traffic Control module and define the maximum requests per second for SMS and OTP delivery. Ensure that E.164 formatting is enforced at the API gateway to prevent malformed requests. By throttling traffic, you protect the sub-account from accidental loops or malicious spikes that could deplete prepaid funds prematurely. Always verify that the STOP keyword logic is active to maintain compliance.

JIT Number Assignment and Provisioning

IOSOR utilizes a Just-In-Time (JIT) provisioning model. When a client requests numbers, do not rely on pre-allocated stock. Instead, use the Number Provisioning API to search and assign available E.164 assets directly to the sub-account. This ensures that the client only pays for what they use. Once assigned, the numbers are immediately linked to the sub-account's balance, ensuring that any MRC or usage costs are deducted in real-time from the prepaid wallet.

Integration and Operational Links

Effective management requires synchronization across multiple operational modules. Refer to these guides for advanced configuration:

• Two-wallet brand split: ops playbook without mixed From
• Low-balance pause before a campaign blast
• Second API Environment: Handover and Cutover

Start with IOSOR

Open the Sub-Account Manager in the IOSOR console and generate dedicated API keys tied strictly to the new enterprise client's unique Account ID. Next, access the Traffic Control module to define explicit requests-per-second limits for SMS and OTP delivery before binding JIT E.164 assets. Finally, verify that webhook endpoints are correctly mapped to the isolated sub-account ID to guarantee accurate DLR tracking.

IOSOR takeaway

Enterprise onboarding demands complete financial and operational separation across every sub-account layer. Enforcing isolated API keys, localized rate caps, and automated spending review triggers guarantees that one client's traffic spikes or balance depletion will never impact adjacent platform operations.

Do set strict RPS caps and dedicated webhook routing during initial account creation. Don't share API credentials between enterprise clients or allow traffic to execute without active balance monitoring triggers.