FAQ

Questions we get - answered plainly.

No marketing spin. If a question keeps coming up, we add it here.

What exactly is Azotte?

Azotte is a subscription orchestration platform and transaction trust center. It sits between your sales channels and your product systems, normalizing subscriptions, enforcing entitlements, and emitting trusted lifecycle events.

Is Azotte a payment processor?

No. Azotte orchestrates subscriptions; it does not process payments directly. You keep your existing PSPs - Azotte routes, retries, and reconciles across them.

How is Azotte different from a generic billing tool?

Generic tools treat each channel as a silo and each region as a fork. Azotte treats channels and regions as first-class configuration. One catalog, many execution paths - without rebuilding integrations.

Can I use Azotte without replacing my current stack?

Yes. Azotte is designed for gradual adoption. Most customers start with one storefront or one product line and migrate more over time. Legacy systems and Azotte can operate in parallel indefinitely.

Does Azotte support usage-based pricing?

Yes. Metering, prepaid wallets, overage rules, and enterprise commit-and-draw-down are first-class. See the AI & Usage-Based solution page.

What about app stores and in-app purchases?

Apple App Store and Google Play subscriptions normalize into the same lifecycle model as web and partner subscriptions. Provider-specific differences are handled by adapters.

How do you handle multi-region compliance?

Each storefront has its own tax scheme, consent rules, and payment providers. GDPR, VAT OSS, SCA, LGPD, and similar are handled per-storefront. See Security & Compliance.

What does integration look like?

REST API, typed SDKs, and signed webhooks. Hosted pages are available for checkout and self-service if you want to skip the frontend work. Most customers reach production in 2–6 weeks.

Can we migrate from our current subscription system?

Yes. Migration support is included. Azotte imports existing subscriptions and runs them alongside your legacy system until you're ready to cut over per product, per region, or per brand.

How is data isolated across tenants?

Tenant isolation is built into the data model. Queries and APIs are tenant-scoped by default. Admin actions and data exports respect scoped RBAC.

What are the SLAs?

Webhook delivery SLA is 99.95%. API p99 latency target is under 120 ms. Enterprise plans include custom SLAs and dedicated support. See system status for live metrics.

How do I talk to sales?

Book a demo from any page, or reach out via contact. Typical first-call lasts 30 minutes and covers your current stack, your growth plans, and what a migration would look like.