Start with a sandbox account
Use the sandbox API and sandbox credentials. Funding uses Stripe test checkout, and fulfilled orders return synthetic installation details. No real eSIM is purchased and no customer email is sent by Akariq.
Your own system may still send emails or record transactions. Configure your integration’s test environment accordingly. Never present a synthetic profile as a usable eSIM.
Exercise the important cases
- Browse plans, paginate and quote the current price for your account.
- Complete test wallet funding and verify exactly one credit.
- Place an order, wait for fulfillment and retrieve installation details.
- Repeat the same order and funding requests; verify there is no duplicate purchase or credit.
- Change a request body while keeping its key; verify conflict handling.
- Attempt an order without sufficient funds and verify your customer-facing recovery.
- Test invalid or expired credentials and ensure no keys appear in browser code or logs.
- If using webhooks, verify signatures, reject invalid signatures, acknowledge duplicates and recover from a failed delivery.
- Check that your own customer page and email show the selected plan and its installation instructions.
Coordinate additional test accounts or unusual order states with Akariq. Never try to access another real partner’s data as a test.
Prepare for production
Ask Akariq for production credentials after reviewing the sandbox results. Confirm pricing, commercial terms, webhook configuration, funding arrangements and the support contact for your integration.
Switch both the base URL and credentials. Fund the production account, then complete a controlled real purchase with an agreed budget and an eSIM-compatible device. Verify payment, fulfillment, customer delivery and installation. Sandbox success cannot prove real network connectivity.
Operate after launch
Monitor available and reserved credit, aged orders, failed webhook deliveries, request errors and your own customer-delivery failures. Keep the Akariq order ID linked to your consumer order and payment records.
Alert your team when an order enters pending_review. Investigate rather than purchasing again. Arrange credential rotation before expiry and keep your webhook verification secret current.
Start with a volume your team can monitor. Increase it after the complete purchase and support process is working reliably.