What are pending loyalty points?

‍Pending loyalty points are rewards that a customer has earned through a specific action (such as a purchase or referral) but are not yet available for redemption.

In Voucherify, pending points support is a built-in feature that allows brands to add control, flexibility, and protection to their loyalty programs. These points remain in a temporary "pending balance" until a predefined activation condition is met, such as a fraud check or the expiration of a return window. Once satisfied, the points convert into an active balance that the customer can spend or use toward tier progression.

Why pending points are important?

For brands, immediate point issuance carries significant financial risk. Using a pending state allows you to:

• Eliminate return & refund abuse: points only become available after the return window closes, preventing customers from "earning and burning" points on items they later return.
• Mitigate fraud & gaming: by delaying availability, you reduce the risk of bots or malicious actors exploiting reward gaps.
• Align with order status: ensures that points accurately reflect "real" revenue (fulfilled and paid) rather than just intent.
• Improve program stability: prevents sudden "liability spikes" on your balance sheet by only activating points once the transaction is finalized.

How pending points work in Voucherify?

When an earning rule triggers (e.g., order paid), Voucherify can be configured to grant pending instead of active points. Each pending entry records the associated customer, order or event, campaign, and timestamp.

In Voucherify, you can define your pending points policy in 4 distinct ways:

• ‍No pending period: points activate immediately after being granted. Useful when you want the structural benefits of a pending flow (audit trail, metadata, cancellation hooks) without actually delaying anything.‍
• Period-based: points activate after a set number of days, up to one year. This is the classic return-window model: grant on purchase, activate after 14 or 30 days.‍
• Fixed date: points activate on a specific calendar date. Think end-of-quarter activations, seasonal program resets, or coordinating with financial close cycles.‍
• Event-based: points activate when a specific custom event fires. Fulfillment confirmed, invoice paid, subscription renewed. You define the trigger, Voucherify listens for it. This is the most flexible option and removes the guesswork of picking an arbitrary waiting period.

Regardless of method, Voucherify provides endpoints to list, adjust, or cancel pending points before activation. Once activated, points move to the customer's active balance and become eligible for redemption, tier progression, or other loyalty mechanics.

Common use cases for pending points

Pending points are especially valuable in scenarios like:

• E-commerce & retail: holding points until the 14-day or 30-day return window expires.
• High-ticket electronics: preventing "reward harvesting" on expensive items that have high return rates.
• Subscription services: granting points only after the second month of a subscription is successfully billed.
• B2B invoicing: activating points only after the "Net-30" invoice is marked as paid in the ERP.
• Seasonal and campaign-aligned programs: using fixed-date activation to batch-release points at the start of a new loyalty season or after a promotional event closes. It keeps the program tidy and gives finance a predictable activation schedule.
• Fulfillment-dependent rewards: using event-based activation tied to a "shipped" or "delivered" event from your OMS. No arbitrary 14-day guess, points activate when the order actually lands.

Best practices for pending points

• Communicate clearly to customers: show in the wallet UI that some points are “pending” and explain why/when they’ll become active. Transparency builds trust.
• Pick the activation method that matches your risk, not your convenience: period-based is simple but arbitrary. If your real concern is returns, an event tied to the return window closing is more precise. If it's payment confirmation, wire it to your billing event.
• Set realistic pending period: too long and customers feel cheated; too short and you expose yourself to return or refund risk.
• Use automation and webhooks: let your system automatically activate points, send notifications, and manage edge cases (returns, cancellations, disputes).
• Account for liability and breakage: track how many pending points never activate (returns, cancellations) vs. how many convert for financial forecasting.
• Ensure concurrency and consistency: if an order is refunded or partially returned, make sure pending (or activated) points are revoked or adjusted appropriately.
• Avoid over-complicating the UX: if customers see a wall of pending points, they may mistrust the program. Use clear labels.