If you run texting for your own customers, the billing model decides who carries the risk when a customer's usage spikes: you or them. Twilio-style usage billing charges the account for what it sends, which means you front the cost and collect later. Prepaid credits flip that, because the money is in before the text goes out. Neither is wrong. They suit different businesses.
How the two models behave
With usage billing on a CPaaS account, messages go out as long as the account is in good standing. You see the charges after the fact, then recharge your own customer through your own billing. With prepaid credits, a balance is drawn down per segment and sending stops, or is topped up, when it runs out.
| Question | Usage billing | Prepaid credits |
|---|---|---|
| Who fronts the cost of a spike? | You | The sender, up to the balance |
| Surprise invoice risk | Yes | Low |
| Needs a collections process | Yes | Mostly no |
| Can a customer run up charges overnight? | Yes, unless you cap it | Only up to the balance |
| Easier for tiny accounts | Sometimes | Usually |
Where platforms get hurt
The risk with usage billing is a runaway send. A customer uploads a big list, a script loops, or a retry bug repeats a message, and by the morning you owe the vendor for texts your customer hasn't paid you for. You can build caps and alerts, but you build and maintain them.
The risk with prepaid is a gap in service. If a balance hits zero during a campaign, the rest of the texts don't go. That's why balance alerts matter. We cover that in prepaid balance monitoring for platforms.
How Ready bills
Ready's billing is prepaid credits. The wallet holds dollars, each segment is charged at the account's rate, and the carrier fee shows as its own line on the bill so you can read it. The Standard rate is $0.0075 per segment plus a $0.0045 carrier fee, $0.012 all-in, which doesn't include screening if you switch the scrub or number validation on. There's no volume discount. Enterprise is custom, so talk to us if you need terms a prepaid wallet doesn't fit.
Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.
Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.
For comparison, Twilio's list rate for a US segment is about $0.0083 before carrier fees and number costs, and registration and numbers are priced differently on each side, so a straight per-text comparison misleads. Compare what's included, not a single number. Our honest cost comparison with Twilio lays out the pieces.
Picking one
Choose usage billing if you have a collections process, a finance team that wants one invoice and customers who'd rather not manage a balance. Choose prepaid if you resell texting to small accounts, can't absorb a bad month and want the cap built into the model.
A hybrid is also common: prepaid at the sub-account level, so each customer is bounded, with your own invoice on top.
Frequently asked questions
Does prepaid mean a customer can't send once the balance is empty?
Right. Sending needs balance, so set alerts and top-ups before a campaign.
Can I bill my own customers a different price?
Yes. Your price to your customer is yours to set, and Ready's rate is what you pay. We explain the model in per-message billing vs a flat rebill.
Is there a free allowance?
No. Every text is charged from the first one.
The practical takeaway
Model the worst day, not the average one. If a runaway send would hurt you, put a prepaid boundary around each customer. You can see the full price list on the pricing page.