Usage and billing
The first 100 engaged customer units across your company are free every UTC calendar month. Customer 101 starts at €0.05 per Live Space, before tax, and later volume bands cost less. There is no base fee, minimum spend, annual commitment, seat charge or paid feature tier. See the pricing calculator.
| Monthly qualifying customer units | Rate for customers in this band |
|---|---|
| 1 to 100 | Included |
| 101 to 1,000 | €0.0500 |
| 1,001 to 5,000 | €0.0475 |
| 5,001 to 10,000 | €0.0450 |
| 10,001 to 25,000 | €0.0425 |
| 25,001 to 50,000 | €0.0400 |
| 50,001 to 100,000 | €0.0375 |
| 100,001 and above | €0.0350 |
These are graduated bands across the company's qualifying Live customer units, not volume thresholds that reprice earlier customers. Test Space customers do not count. For example, 10,000 qualifying customers cost €460: the first 100 are included, customers 101 to 1,000 cost €45, the next 4,000 cost €190 and the next 5,000 cost €225. The total therefore never falls when usage crosses a threshold. Fractional-cent rates are accumulated across the monthly total and rounded to euro cents.
What counts
A customer counts once when the program successfully:
- awards positive wallet points;
- advances or completes a Goal;
- unlocks a new Perk; or
- completes a Reward redemption.
Further activity by that customer in the same Space and month is included. The same person in two independent Live Spaces counts separately, while both units contribute to the same company volume bands. The month follows when Perkamo processes the result, not a backdated event timestamp.
This measures delivered program functionality. It does not assert additional revenue or guarantee external fulfillment of a benefit. Your application remains responsible for fulfilling Reward effects.
What stays free
Test Spaces, setup, simulations, identify/import, customer-state reads, duplicate retries, failed operations, ineffective events and webhook retries create no charge. A matching rule with no change is insufficient. Negative-only wallet changes and manual support adjustments also do not count. Goal progress can still qualify when a separate Earning rule is capped or on cooldown.
A Test Space is an integration sandbox, not a free production environment. After PAYG activation, all company Test Spaces share 100 monthly active test customers and 1,000 monthly events. The Console warns at 80 percent and returns 429 test_space_limit_exceeded when a limit is reached. The response includes the meter, limit and UTC reset time. Use a Live Space for real customers. Contact support before a high-volume load test.
There are no event or webhook overage fees in Live Spaces after PAYG activation. Security rate limits still protect the service. Accounts awaiting activation can retain temporary account-specific operational limits and a history window until support completes their transition. Customer erasure always overrides normal history availability.
Start and control paid usage
The company owner reviews the rate and sets a company-wide monthly alert budget in Company → Usage and billing, then completes payment setup. Live usage counts from the first qualifying result, even while payment setup is pending. The first 100 qualifying units across the company each UTC month are included; the 101st adds to current spend. Test Space activity does not count. If payment setup is unavailable, the console still shows accrued spend and its alert. Payment details are needed to collect charges after the month closes. Previously accepted rate agreements retain their terms.
The budget covers platform charges before tax across every Live Space in the company. It is an alert threshold, not a service limit. Reaching or exceeding it shows a warning and the amount above budget, while approaching it is visible in the budget progress indicator. Events, points, progress, Benefits and billing continue without interruption. Lowering the budget does not erase charges already accrued. Failed collection is shown in billing and handled through the payment recovery process; it does not automatically stop customer events. If an account must be suspended after that recovery window, Perkamo support uses the separate account status control.
Invoices and corrections
The console shows the amount spent, remaining budget or overage, a daily spending chart and the latest qualifying activity. Today's chart value updates with new qualifying customers. Closed UTC days are recalculated once daily from the usage ledger. Closed months are invoiced for actual paid units; zero paid usage creates no platform invoice. Invoices have a direct Stripe-hosted view and payment action in the Console. Payment methods, billing details and prior invoices are also available through the Stripe billing portal. Existing PAYG agreements keep their accepted rate version. If self-service activation is unavailable for an account, contact support to coordinate its effective date and any agreed credit.
External refunds do not automatically reverse platform service already delivered. For an incorrect platform charge, contact support with the invoice and relevant transaction. Corrections use an explicit invoice credit. Customer erasure removes customer-linked evidence while preserving company billing totals.