Pricing
Pay for what you send. Nothing more.
A prepaid balance, billed per segment at a rate set for your workspace. Failed messages are refunded automatically, and you'll know the rate before you top up.
Workspace balance · prepaid
Your rate, your balance
Ledger
- +
Top-up credited
Recorded in the audit log
- −
OTP · 1 segment
Reserved when accepted
- −
Order update · 2 segments
Reserved when accepted
- +
Failed on every route
Refunded automatically
- 0
Dashboard sign-in code
Never billed
How billing works
Four rules, no surprises
The same rules apply to every workspace. Only the rate is yours.
Prepaid workspace balance
Your workspace holds one balance shared by all its API keys. We credit it when you top up, and every top-up is written to the audit log.
Billed per segment, by type
Each message costs your workspace's rate for its type — transactional, OTP or promotional — multiplied by its segments. Rates are agreed per workspace.
Reserved at the moment of send
The cost is reserved from your balance atomically when we accept the message. If the balance is too low, the API returns 402 insufficient_balance and nothing is sent.
Failed means refunded
If no route can take a message, or every route fails, the full cost goes back to your balance automatically. Idempotent replays are never billed twice.
Never billed
- One-time codes that sign you in to the dashboard
- SIM health-check messages our team sends
- Messages that fail on every route — refunded in full
- Replays of a request with the same Idempotency-Key (kept 24 h)
Not refunded
- Undelivered messages — the network accepted them but the handset never confirmed, so the carrier was used
- Messages you send from the dashboard, including tests to your own number
- Extra segments from a long message or Unicode text — check
segmentsin each response
Segments, explained
Why one message can cost two
Mobile networks carry text in fixed-size segments. Which alphabet your text needs decides how many characters fit. A message can be up to 6 segments.
GSM-7
160 / 153English letters, digits and common symbols
- Fits in one segment
- 160chars
- Each part when longer
- 153chars
A 200-character English message
“Your order #1042 has shipped…”
= 2 segments (153 + 47 characters)
Unicode (UCS-2)
70 / 67Nepali, emoji and any character outside GSM-7
- Fits in one segment
- 70chars
- Each part when longer
- 67chars
A 100-character Nepali message
“तपाईंको अर्डर पठाइएको छ…”
= 2 segments (67 + 33 characters)
One emoji or one Nepali letter switches the whole message to Unicode. Characters such as { } [ ] ~ \ | ^ € count as two in GSM-7. We never split a character across segments.
Find your fit
Tell us what you send. We'll quote your rate.
The billing rules are the same for everyone. What changes is the rate for each message type and the support you need around it.
Startup
You're launching an app and need login codes and a handful of alerts working this week.
- OTP and transactional on one key
- Start with a small top-up
- Docs, dashboard and email support
Talk to us for your rate
Talk to salesBusiness
You send steady daily traffic — orders, receipts, reminders — and want predictable rates and a team in the dashboard.
- Rates set for your mix of message types
- Separate API keys per app or environment
- Members, audit log and webhook delivery history
Talk to us for your rate
Talk to salesEnterprise
You're a bank, wallet, telecom-scale app or institution with security reviews, higher throughput and paperwork to match.
- Per-client send rate agreed with you
- Data processing terms and help with security reviews
- A direct line to the engineering team
Talk to us for your rate
Talk to salesPrefer email? Write to sales@lacspace.com with your expected monthly volume and message types.
Getting started
From sign-up to first send
- 1
Create a workspace
Sign in with your phone number or email. No card needed to explore.
- 2
Agree your rate
We activate your workspace and confirm a rate per message type.
- 3
Top up and send
We credit your balance. Create an API key and send your first message.
Billing FAQ
Questions about paying
Why don't you publish prices?
What exactly is a segment?
segments and encoding it used.When is a message refunded?
failed.Why isn't an undelivered message refunded?
undelivered message was accepted by the mobile network — the carrier was used — but the handset never confirmed receipt, for example because the phone was switched off for too long or the number is inactive. The send was made, so it isn't refunded.What is never billed?
How do I top up?
GET /sms/balance, which also returns your rate per message type.What happens when my balance runs out?
402 insufficient_balance until you top up. Messages already accepted keep going — their cost was reserved when they were accepted.Can I try it before paying?
More questions? See the full FAQ or the balance API.
Get your rate today
Create a free workspace now, and tell us what you plan to send. We'll activate you and confirm your rate.