Limits
Last updated 10 October 2026
The limits this store enforces, read from its live settings, and what it can't protect you from.
Limits we enforce
| Action | Limit | Window |
|---|---|---|
| Reseller API calls (REST and Dhru), per key | 120 calls | 1 minute |
| Order status checks over the Dhru API | 60 status checks | 1 minute |
| Failed API key checks, per IP address | 10 failed key checks | 15 minutes |
| IMEIs in one order | 200 IMEIs | per order |
| Active API keys per reseller | 5 keys | at a time |
| Failed sign-ins, per account | 5 failed sign-ins | 15 minutes |
| Wrong email or two-factor codes, per network | 10 wrong codes | 15 minutes |
| Free IMEI checks, per visitor | 10 checks | 1 minute |
| One top-up | $5.00 to $5,000.00 | per top-up |
| Open bank transfer requests | 3 open requests | per customer |
| New support tickets | 5 tickets | 1 hour |
| Voucher attempts | 10 attempts | 1 hour |
Timeouts
| What | Timeout |
|---|---|
| One order call to a supplier | 90 seconds |
| One completion callback to your server | 10 seconds |
| First status check of a processing order | after 1 minute |
| Longest gap between status checks | 30 minutes |
| An order still processing is flagged for staff after | 72 hours |
| An unpaid card or crypto top-up expires after | 7 days |
What we don't protect against
- Supplier reliability. A supplier can be slow, go offline or reject an order. We refund what fails, but we can't make a supplier deliver.
- Irreversible blockchain payments. A crypto payment can't be reversed by anyone once it is sent. Check the amount and address before you pay.
- Wrong-network deposits. Crypto sent on a network or in a coin the payment page didn't ask for may be lost.
- Server compromise. If someone takes over the server itself, these limits don't hold. We keep it patched and backed up, but no store can promise more.