Provisioning
DEFINITION
Provisioning is the process of granting a customer access to the product, features, or service level they paid for once a subscription event, like a signup or upgrade, is confirmed.
TABLE OF CONTENTS
RELATED TERMS
Provisioning is the process of granting a customer access to the product, features, or service level they have paid for once a subscription event occurs. When a signup, plan change, or renewal is confirmed, provisioning turns that billing state into the access the customer actually uses, such as activating an account, unlocking plan-specific features, or setting usage limits.
Provisioning sits between the billing system and the product. Billing decides what a customer is entitled to, and provisioning delivers it. The trigger is usually a subscription event: a new signup, an upgrade or downgrade, a renewal, a pause, or a cancellation. Each event carries a change in entitlement, and provisioning is the work of applying that change to the running product so the customer sees the right level of access. Provisioning is not the API that carries a subscription event, the webhook that announces it, or the entitlement that defines the access; it is the step that reads the entitlement and applies the resulting access change to the product.
It runs in both directions. Granting access is provisioning; removing or reducing it when a subscription is downgraded, paused, or canceled is deprovisioning. In most subscription businesses this is automated and event-driven rather than handled by hand, because access needs to change the moment billing does, and a subscription platform such as Recurly links entitlements to the plans and items a customer buys so that access follows the subscription without a separate integration to maintain.
Why provisioning matters for subscription businesses
Provisioning is where a paid subscription becomes a working product. If it lags or fails, a customer who has paid cannot use what they bought, which creates support tickets, refunds, and early churn. If deprovisioning lags or fails, customers keep access they are no longer paying for, which leaks revenue. Reliable provisioning keeps entitlement and access in sync in both directions, so what a customer can use always matches what they are paying for. Teams that connect provisioning directly to billing tend to reduce this manual reconciliation work, though the exact impact varies by business.
For an operator, the value of provisioning inside a subscription platform is that billing state and product access stay connected without a separate integration to maintain. Recurly supports entitlements that link features or content to the plans and items a customer buys, so access is granted automatically when they subscribe and reflected in later API calls. Recurly's guidance is to provision from the API response of the originating action and to treat webhooks as notifications that signal a change, not as the command that grants access on their own, which keeps access reliable even when a notification is delayed. Whether a specific entitlement model, plan-tier availability, or automation fits a given business should be confirmed with the Recurly team for that account.
How to use provisioning
Treat provisioning as a defined path from a confirmed billing event to a change in product access, not as a one-off script. A few practical points:
Provision from the confirmed result of the originating action, such as the signup or purchase response, rather than from a downstream notification alone, so access is granted the moment payment succeeds.
Store the resulting access state in your own system and treat it as the source of truth for what the customer can do, updating it only when a later event says the entitlement changed.
Map every plan and add-on to the specific access it should grant, so an upgrade, downgrade, or cancellation has a defined provisioning outcome.
Build a manual path for support to grant or restore access when an automated event is missed, so a single failure does not strand a paying customer.
How provisioning works
A typical provisioning sequence for a subscription business runs in order:
A subscription event occurs, such as a signup, upgrade, downgrade, renewal, or cancellation.
Billing confirms the outcome of that event, for example a successful payment or a completed plan change.
The system reads the entitlement tied to the plan or add-on involved.
Provisioning applies that entitlement to the product, granting, raising, reducing, or removing access.
The resulting access state is stored so the product and support teams share one view of what the customer can use.
Later subscription events repeat the sequence, keeping access aligned with billing over the life of the subscription.
Provisioning vs deprovisioning
These two are easy to confuse because they are the same process pointed in opposite directions.
Provisioning grants or increases access when a customer starts or upgrades a subscription.
Deprovisioning removes or reduces access when a customer downgrades, pauses, or cancels.
Both are driven by the same subscription events and the same entitlement mapping, so a business that automates one should automate the other to avoid customers keeping access they no longer pay for.
Benefits and examples
When provisioning is automated and tied to billing events, access tracks the subscription without manual steps.
A customer signs up and pays. Provisioning activates the account and unlocks the plan they bought, so they can start using it immediately.
A customer upgrades. Provisioning raises usage limits or unlocks higher-tier features tied to the new plan.
A customer downgrades or cancels. Deprovisioning removes access to the features they no longer pay for, at the point the entitlement ends.
A renewal payment succeeds. Provisioning keeps access in place for the next term with no interruption for the customer.
Frequently asked questions
What is provisioning in a subscription business? Provisioning is the process of giving a customer access to the product or features they paid for after a subscription event, such as a signup, upgrade, or renewal. It turns a billing outcome into working access, like activating an account or unlocking plan-specific features.
What is the difference between provisioning and deprovisioning? Provisioning grants or increases access when a customer starts or upgrades a subscription. Deprovisioning removes or reduces access when they downgrade, pause, or cancel. They are the same process in opposite directions and are usually driven by the same subscription events.
When does provisioning happen? Provisioning happens whenever a subscription event changes what a customer is entitled to. That includes a new signup, a plan upgrade or downgrade, a successful renewal, and a pause or cancellation. Each event can grant, change, or remove access.
Why should provisioning be automated? Automating provisioning keeps product access in sync with billing without manual steps. If access lags, a paying customer cannot use what they bought, which drives support tickets and churn. If access is not removed on cancellation, the business gives away service it is no longer paid for.
