Andorpay
Back to the blog

Published on · Updated on

Usage-based billing: from measurement to payment

Define units, periods and limits for your digital service. Connect reliable usage records, calculation and a clear payment journey.

Usage meter beside a container of tokens and a receipt.

Usage-based billing calculates an amount from a unit of consumption: completed sessions, generated documents, resources used or work delivered. Customers need to understand what counts, and your system needs to explain each unit. Payment comes afterwards, once the amount and the relevant period have been established.

If your digital service operates from Andorra, prepare both parts before offering the model: how you measure usage and how you collect the resulting payment. At AndorPay, we review the payment connection to your business; measurement and calculation need their own scope. A checkout that accepts an amount is not a complete usage-based billing system.

Choose a unit customers can recognise

A useful unit relates to what the customer receives. “Document delivered” describes an outcome; “internal event” describes your technology. If buyers need to understand the application architecture to follow their usage, the commercial explanation needs more work.

Decide when a unit is complete. For a document service, does requesting, completing or downloading a document count? If generation fails and the user tries again, have they used one unit or two? Settle that question before building the counter.

Use the same definition in the offer, the application and the usage summary. Switching from “task” to “credit” without explaining the relationship makes the charge harder to check. A proprietary unit can work, but its meaning needs to remain stable and understandable.

Separate usage, calculation and payment

The product observes what happens. A usage record retains the units. A rule converts those units into an amount. The appropriate document describes the sale, and the payment system attempts collection. Even when one tool covers several tasks, identify them separately.

Layer Question it answers Information required
Service What did the customer receive? Outcome and delivery time
Measurement How many units count? Customer, unit and identifier
Calculation Which terms apply? Current rule and period
Document Which transaction is recorded? Relevant items and details
Payment Has the amount been collected? Operation and confirmed status

The distinction helps when a customer questions a total. Repeating payment does not fix a counter showing too many units. If calculation is correct but collection is pending, investigate the financial operation. A dashboard may show both, but they are not the same state.

Decide when usage is paid for

Before the service is used

A prepaid model provides a quantity of use or a balance under the offer's terms. Explain how it is consumed, what happens when it runs out and whether any time condition applies. Customers need to know when they can continue and when another purchase is required.

This model requires a consistent balance record. A failed action should not consume units if your commercial definition only counts completed outcomes. If two requests arrive together, the system needs to apply the rule without allowing use that conflicts with the available balance.

At the end of a period

A postpaid model totals usage over an interval and calculates the amount at closing. Define the start, end and time zone. Activity near the month boundary must be allocated consistently and remain traceable afterwards.

Customers need visibility during the period, particularly when usage can vary considerably. Decide whether there will be notifications, limits or approval before further use. These are service decisions; do not assume the payment processor knows or controls your usage counter.

A fixed component plus variable usage

An offer can combine recurring access with additional units. Explain what is included, what can run out and which action creates extra consumption. Customers should recognise that boundary without interpreting internal formulas.

Check that the application can show included and additional usage separately. Otherwise, a simpler initial offer may be easier to operate. Our subscription plan guide helps organise features and limits before adding more billing rules.

Keep a record that explains the usage

Each billable unit should be associated with a customer, a specific action, a time and an outcome. Retain a stable identifier for the action so that it can be recognised if the same message arrives again. Retrying delivery of an event should not turn one service outcome into two billable units.

The Airwallex usage events documentation provides a technical example of identifiers used to prevent duplicates. This is a design reference from that provider, not a statement about its commercial availability in Andorra or a capability attributed to AndorPay.

Define how late events are handled too. A task may finish before closing but be reported later after an interruption. Decide whether it belongs to the original period or requires review. Silently changing a total already shown to the customer makes the charge difficult to explain.

Keep the version of the rule applied. If you change what counts as a unit or what a plan includes, earlier periods should remain explainable under their original terms. A new configuration should not automatically reinterpret the entire usage history.

Example: a service that prepares documents

Imagine an application generating documents from user-provided information. You decide that one unit means a completed, available document. A request ending in an error does not count. Downloading the same document again does not create another unit either.

The user can view documents completed during the period. A summary groups that usage and applies the current terms. Before collection, the business can identify the documents making up the total and the unsuccessful actions excluded from it.

If a task appears twice because the same event was received again, its identifier exposes the duplicate. If a document is withdrawn because of a service error, the adjustment retains the reason and original reference. You can explain the change without deleting the history.

After calculation closes, the compatible payment journey is prepared. Its status remains linked to the period. The document summary must not become “paid” simply because it has been generated; it needs the corresponding financial result.

Make limits and notifications understandable

Usage-based offers can be hard to anticipate if customers cannot see what they have consumed. Display units in recognisable language and explain when the figure updates. If reporting is delayed, the counter should not look like a definitive real-time total.

Define what happens at a limit: stop new actions, request an extension or continue under previously agreed terms. Explain that behaviour before the user reaches a blocked action. Hidden limits create commercial questions and support work.

Notifications also need context. “You have used the sessions included in this period” is more helpful than an error code. If more use can be purchased, explain the next step and when it becomes available. If the customer must wait, show the applicable renewal date.

A notification should match the control behind it. An advisory message does not establish that a hard limit will stop consumption. If you offer a hard limit, test it with simultaneous activity so that the customer's expectation matches what the application does.

Resolve discrepancies before charging again

When a customer disputes usage, find the period and the units making up its calculation. Look for duplicates, unsuccessful actions counted incorrectly, a different rule or an expectation that was poorly explained. The aim is to reconstruct the amount using understandable records.

If calculation changes before payment, retain the adjustment and prepare the revised total under the agreed process. If payment has already happened, correcting it requires a separate financial process. Changing a consumption counter does not automatically return money.

Where payment status is ambiguous, check the existing operation before creating another. Our failed renewal guide explains the separation between financial outcome and next action. The same reasoning applies to a variable payment associated with a period.

Check the actual responsibilities of each tool

Before offering the model, establish who measures usage, closes the period, calculates the amount and passes it to the payment journey. A feature list containing “billing” does not answer those questions on its own.

Our API documentation describes the available contracts. Its documented amount input is subject to restrictions; it should not be interpreted as an unrestricted usage-pricing engine. We review the specific journey before committing to its fit for your service.

Prepare an example period showing units, the applied rule and expected outcome. Add when payment should happen and how the service is delivered. That gives a much more precise basis for assessing the connection than a general request for “flexible billing”.

Identify the existing owner of the usage record too. If your product already measures consumption, the question may be how to connect its approved total to payment. If it does not, measurement is additional work that must be included rather than assumed.

Test the model before launch

Test a completed unit, a failed action, a repeated event and an event arriving late. Check period closing, rule changes and a period with no consumption. The expected total should match the records you explain to the customer.

Then validate payment and its association with that period. Include successful, declined and pending outcomes. Review what happens to access or balance in each case. The system should explain both use and collection even when they are not completed at the same moment.

To define the scope, tell us which unit you want to charge for and how you record it. At AndorPay, we review the payment journey and its connections. If you are still separating responsibilities, our guide to payment gateways and billing platforms will help prepare the discussion.

Frequently asked questions

Is usage-based billing the same as a subscription?

A subscription defines an ongoing relationship; usage defines how an amount or entitlement is determined. They can be combined, but need clear rules for scheduling, measurement and delivery.

Do I need to record every action?

Keep enough detail to justify billable units, identify duplicates and resolve discrepancies. Which actions matter depends on your usage definition. Every technical event does not have to become a commercial unit.

Can I change the unit after launch?

You can design a new offer, but define its effective date and retain the explanation for earlier periods. Changing a rule should not silently rewrite customers' consumption history.

WhatsApp