Skip to main content

Azotte Terminology

This page explains the main terms used across Azotte, including the portal, APIs, subscription lifecycle, catalog, pricing, campaigns, payments, and integrations.

Use this glossary as a shared reference when reading developer documentation, configuring the management portal, or discussing Azotte concepts with technical and business teams.

Core Tenancy & Identity​

Tenant​

A logically isolated workspace in Azotte.

Each tenant has its own data, users, roles, catalog, integrations, payment settings, and operational configuration. Most platform activity is scoped to a tenant.

Tenant Identifier​

The unique identifier of a tenant.

Azotte uses this identifier to resolve which tenant context an API request, portal session, or integration action belongs to.

x-tn Header​

The HTTP request header used to pass the tenant identifier to Azotte APIs.

In portal-based flows, this value is usually handled automatically. In API and machine-to-machine integrations, external systems must provide the correct tenant context when required.

Tenant Admin​

A user with full administrative authority inside a tenant.

Tenant Admins can manage users, roles, catalog settings, integrations, payment configuration, fiscalization configuration, and other tenant-level settings.

Team Member​

A user account that belongs to a tenant.

A team member can access the Azotte portal according to the permissions assigned through roles.

Role​

A named set of permissions.

Roles define which portal screens, actions, and configuration areas a team member can access.

→ Manage roles and permissions

API Key​

A long-lived credential issued for a tenant.

API keys are used by external systems to authenticate machine-to-machine requests against Azotte APIs.

→ Create and use API keys

Customer Domain​

Customer​

The end user, subscriber, or buyer of a tenant.

A customer can hold subscriptions, payment methods, orders, entitlements, invoices, interactions, and lifecycle history.

Subscription​

A recurring agreement between a customer and a tenant.

A subscription connects a customer to a bundle, billing cycle, renewal policy, lifecycle state, and entitlement set.

Common lifecycle states include:

  • Active
  • Paused
  • Cancelled
  • Expired
  • In grace period
  • Pending renewal

Third-Party Subscription Provider​

An external source of subscriptions.

Examples include Apple App Store, Google Play, telecom partners, OTT platforms, partner marketplaces, or legacy billing systems. Azotte can import, reconcile, and manage these subscription records depending on the integration model.

Membership Level​

A customer tier used for segmentation and business rules.

Examples include Bronze, Silver, Gold, VIP, Student, or Enterprise. Membership levels can influence pricing, campaign eligibility, entitlement access, and customer treatment.

Cancellation Reason​

A predefined reason selected when a subscription is cancelled.

Cancellation reasons support churn analysis, customer support, win-back campaigns, and retention reporting.

Catalog, Bundles & Entitlements​

Bundle​

A sellable product package.

A bundle groups one or more entitlements and defines what the customer receives when they subscribe or purchase.

Examples:

  • Premium Monthly Plan
  • Sports Add-on
  • Family Pack
  • Annual Pro Subscription

Bundle Group​

A logical collection of related bundles.

Bundle groups help organize catalogs, storefront presentation, campaigns, reporting, and portal navigation.

Entitlement​

A grant of access to a feature, service, content package, quota, or capability.

Customers receive entitlements through subscriptions, purchases, campaigns, goodwill grants, or manual operator actions.

Examples:

  • Access to premium video content
  • 4 device slots
  • 100 GB storage
  • Ad-free viewing
  • Advanced reporting

Quota Unit​

A measurable unit connected to an entitlement.

Quota units are used when access is limited, metered, or consumed over time.

Examples:

  • Minutes
  • GB
  • Device slots
  • API calls
  • Seats
  • Downloads

Pricing​

Price​

The monetary amount charged for a bundle.

A single bundle can have different prices depending on region, currency, storefront, customer segment, tax rules, or promotional context.

Price Card​

A price configuration attached to a bundle.

A price card defines how a bundle is priced for a specific market, segment, storefront, or condition. It can include list price, currency, tax behavior, billing period, and applicable price impacts.

Trial Policy​

Rules that define how trials work for a bundle.

A trial policy can control trial duration, eligibility, conversion behavior, repeat usage, and what happens when the trial ends.

Price Impact​

A campaign or pricing rule that changes the amount charged.

Examples include percentage discounts, fixed discounts, free periods, reduced first month pricing, or special renewal pricing.

Storefront & Distribution​

Storefront​

A customer-facing sales channel where bundles are offered.

A tenant can operate multiple storefronts with different branding, catalog scope, pricing, payment routing, tax settings, and localization.

Examples:

  • Web storefront
  • Mobile app
  • Smart TV app
  • Partner portal
  • Regional storefront
  • B2B customer portal

Subscription Channel​

The source channel where a subscription originates.

Examples include Web, iOS, Android, OTT, Partner, Telecom, Sales Team, or Migration.

Subscription channels are important for reconciliation, lifecycle rules, revenue reporting, and customer support.

Region​

A geographic or commercial market.

A region can influence currency, tax rules, PSP routing, fiscalization rules, legal requirements, localization, and available bundles.

Localization​

Locale-specific content and formatting.

Localization includes translations, currency display, date formats, notification content, portal labels, checkout text, and customer-facing descriptions.

Campaigns & Promotions​

Campaign​

A time-bound or rule-based promotion.

Campaigns apply specific impacts to eligible customers, bundles, storefronts, regions, or segments.

Examples:

  • 20% discount for the first 3 months
  • Win-back offer for cancelled users
  • Student discount
  • Free sports add-on for annual plans
  • Black Friday promotion

Campaign Group​

A container for related campaigns.

Campaign groups help organize promotions by purpose, period, market, reporting category, or business initiative.

Dynamic Trigger​

A rule-based mechanism that automatically starts an action when a condition is met.

Examples:

  • Customer becomes high churn risk
  • Payment fails
  • Trial is about to end
  • Customer reaches a usage milestone
  • Subscription is cancelled
  • Renewal date is approaching

Dynamic triggers can start campaigns, send notifications, grant entitlements, or create operational tasks.

Promo Code​

A redeemable code that applies a campaign impact.

Promo codes are usually entered during checkout or applied by support agents.

Coverage​

The scope where a campaign, price card, or rule applies.

Coverage can include:

  • Storefronts
  • Regions
  • Bundles
  • Bundle groups
  • Customer segments
  • Membership levels
  • Subscription channels

Impact​

The result applied by a campaign or rule.

Common impact types include:

  • Price impact: changes the amount charged
  • Timeline impact: changes duration, renewal date, trial length, or billing period
  • Entitlement impact: grants or modifies access
  • Communication impact: triggers a notification or message

Payments, Billing & Fiscalization​

Order​

A record of a purchase attempt.

An order captures the customer, bundle, price, campaign impacts, tax calculation, payment intent, and final purchase outcome.

Payment​

A monetary operation related to an order or subscription.

Payments can include authorization, capture, recurring charge, refund, failed attempt, or retry attempt.

Payment Method​

A stored payment instrument used by a customer.

Examples include cards, wallets, bank accounts, local payment methods, and PSP-specific tokens.

Invoice​

A billing document issued for an order or subscription period.

An invoice usually includes line items, tax details, totals, payment status, customer details, and billing period.

Refund​

A full or partial reversal of a captured payment.

Refunds return money to the customer through the original payment method when supported by the PSP.

Goodwill​

A complimentary benefit granted outside normal billing.

Examples include free subscription days, credits, temporary access, or manual compensation after a service issue.

Transaction​

A low-level financial movement.

Transactions can include charges, captures, refunds, chargebacks, fees, settlements, or PSP-side events.

PSP​

Payment Service Provider.

A PSP processes payments on behalf of the tenant. Examples include Stripe, Adyen, Checkout.com, local acquirers, wallet providers, and regional payment gateways.

Payment Adapter​

Azotte’s connector for a specific PSP.

A payment adapter contains the integration logic, credentials, routing behavior, supported features, and operational configuration required to process payments through that provider.

FSP​

Fiscalization Service Provider.

An FSP issues legally compliant fiscal receipts, invoices, or e-invoices in markets where fiscalization is required.

Tax Scheme​

A configurable tax model used to calculate and present taxes.

Tax schemes can define VAT, GST, sales tax, tax inclusion, exemptions, reverse charge behavior, and region-specific rules.

Subscription Lifecycle Actions​

Renewal​

The scheduled process that extends a subscription into the next billing period.

Renewal usually includes payment attempt, invoice generation, entitlement continuation, and lifecycle state update.

Manual Renew​

An operator-initiated renewal outside the normal schedule.

Manual renewals are useful for support, recovery, migration, testing, or exceptional customer handling.

Reactivate​

Restoring a cancelled or expired subscription to an active state.

Reactivation can keep the previous schedule or start a new billing period depending on the configured business rule.

Defer​

Moving a subscription’s next renewal date or expiry date forward without charging immediately.

Deferral is often used for compensation, service recovery, goodwill, or operational corrections.

Grace Period​

A temporary period after a failed payment or expired billing cycle where the customer may still keep access.

Grace periods help reduce involuntary churn and give customers time to resolve payment issues.

Pause​

Temporarily suspending a subscription without fully cancelling it.

Pause rules can define whether billing, entitlement access, and renewal dates are stopped, shifted, or partially maintained.

Notifications & Communication​

Notification​

A message sent to a customer, operator, or external system.

Notifications can be delivered through email, SMS, push, in-app messages, webhooks, or other channels.

Notification Template​

A reusable message template.

Templates can be localized and can include subject, body, channel, language, and placeholders.

Placeholder​

A dynamic token inside a notification template.

→ Use notification placeholders

Example:

{{customer.firstName}}