Key takeaways
- Count calls per flow, not per user.
- Include retries, re-verification and testing.
- Add 20–30% headroom for growth and spikes.
- Check per-minute limits as well as monthly totals.
Count calls per flow
A typical onboarding might call liveness once and verify once — two requests. If 15% of users retry capture, that's about 2.3 requests per onboarding. Step-up checks at withdrawal add one verify each time.
A worked example
| Activity | Monthly volume | Calls each | Requests |
|---|---|---|---|
| New sign-ups | 3,000 | 2.3 | 6,900 |
| Withdrawal re-checks | 9,000 | 1 | 9,000 |
| QA and testing | — | — | 600 |
| Total | 16,500 |
With 25% headroom that's about 20,600 requests a month — beyond Basic's 5,000, so Pro (100,000) fits with plenty of room.
Don't forget throughput
Monthly allowance is half the story. If a marketing campaign sends 200 sign-ups a minute, you need a plan whose transactions-per-minute limit covers it. Compare limits on the pricing page.
Taxes and currency
SIMSIM bills in USD. VAT, GST or sales tax is added based on your billing location.
