Prepaid components essentially allow merchants to charge for usage before it is used, as well as handle units recorded past a set limit. There are two main aspects to using this component:
- Prepaid allocations
- Prepaid usage
Prepaid allocations are the purchase of a block of units for a customer to use; using up that block of units is referred to as prepaid usage. Generally, a subscriber will purchase an allocation first, then record usage over time. If the usage recorded exceeds the amount allocated, or an allocation was not purchased to begin with, those units of usage will be billed as overage.
One unique aspect about prepaid components is that proration will be neither calculated nor applied when purchasing allocations or recording usage. The full amount due will be charged when buying the allocation.
Bear in mind that allocations are always additive and cumulative. For example, if a subscriber requests an allocation for 600, and then another for 800, the total allocation will be 1400.
Allocations are used up in a first in, first out fashion. This means that if 50 units are purchased initially, and then another 50 units are bought later, usage will be recorded against the first allocation of 50. This ensures that subscribers will have the maximum amount of time to use their allotted allocation before any expirations (if configured) take place.
While we will typically use the word “purchase” to describe prepaid allocations, it is possible for the allocation to be at no charge, if the component is free, or to be accrued until the next renewal, if the credit card is declined upon allocation.
At this time, allocations may only be reduced or deleted via API request. Any expiration dates per allocation block may also be updated via API.
To prevent overage pricing from taking effect, a customer must first purchase an allocation. Purchasing additional allocations will not wipe out any existing units in overage. These units will be billed for at renewal.
The only way to reduce the units in overage for a given subscription is to record negative usage. When recording negative usage, overage units will be diminished first, followed by recorded usage.
This section will not be any different than the normal component form. Please review that page for more details.
Like other components, the pricing scheme for a given price point can be per unit, volume based, tiered, or stairstep.
With this setting enabled, the same amount of allocated units for a given subscriber will automatically be purchased again at each renewal. By default, any prepaid allocation that is purchased will not be renewed for the next billing period.
Note that this feature will not automatically purchase additional allocations mid-period, even if there are few units left remaining.
If any units are leftover from the subscription’s current allocations, this option allows those units to be rolled over to the next renewal.
For example, if a subscriber has only used 60/100 total units, those remaining 40 units will be available during the next billing period without incurring overages.
This feature is a type of rollover, so it can only be used when the rollover option is true. When a prepaid usage component price point is created with an expiration interval and unit, all allocations will have an expiration date based off the component’s expiration params.
When an allocation has an expiration date, its quantity will always be available beyond renewal dates and only the expiration date will be respected. Once the allocation has expired, any additional usage recorded will be charged at overage pricing.
Each individual allocation block made to a subscription can have its own expiration date. This means that if a prepaid usage component is set to expire in 6 months, an allocation made in month 1 and another made in month 4 will have different expiration dates. The expiration comes into effect at exactly the specified days or months after the allocation is created. For example, if an allocation is created at 9:58AM on July 6th and is set to expire in one month, the effective expiration date is August 6th 9:58AM.
After clicking the toggle button to enable the setting, enter any number and select either “month” or “day” to set the expiration interval.
Another unique facet of prepaid components is the ability to define overage pricing. Let’s say a subscriber has purchased an allocation of 100 units, and has recorded usage for all of them. If 5 more usages are recorded, each of those 5 can be billed at a different cost than the original 100 units had cost.
In the example above, purchasing the first allocation has a volume based pricing scheme, where the price decreases as more units are purchased at once. Once a subscriber has fully depleted those units, they would be billed a flat $0.50 for each additional usage recorded.