Skip to main content
Use a Usage credits benefit when a purchase should fund a customer’s usage balance. Ruba issues the credits as part of the order or subscription lifecycle, without a webhook handler.
Do not emulate credits by sending negative customer-usage events. Those events can change a Sum meter’s aggregate, but they are not recorded as first-class credited units. Use the Usage credits benefit when the balance must distinguish issued credits from consumed usage.

Choose when credits are issued

Configure the flow

1

Create a usage tracker

Open Products → Meters, create the tracker that measures the billable activity, and save it.
2

Create the benefit

Open Products → Benefits, create a Usage credits benefit, select the usage tracker, and set the number of units to issue.
3

Choose rollover behavior

Enable Carry unused credits over only when remaining subscription credits should carry into the next cycle. Changing this setting affects newly issued credits, not credits already granted.
4

Attach it to the product

Add the benefit to the one-time or recurring product that should fund usage, then save the product.
5

Verify in sandbox

Complete a sandbox checkout and read the customer’s meter balance. For subscriptions, repeat the check after a test cycle to confirm the recurring grant.

Read the resulting balance

Use the Customer Meters API when your application needs to inspect the credited, consumed, and remaining units for a customer.
For the benefit’s full configuration rules, see Usage credits.