Usage and billing

Perkamo uses one rate: €0.05 per engaged customer per Live Space per UTC calendar month, before tax. There is no base fee, minimum spend, annual commitment, seat charge or paid feature tier. See the pricing calculator.

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. 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.

There are no event or webhook overage fees after PAYG activation. Security rate limits still protect the service. Accounts still on a legacy plan retain that plan's operational limits and history window until support completes their company-by-company migration. Customer erasure always overrides normal history availability.

Start and control paid usage

The company owner reviews the rate and sets a company-wide spending limit in Company → Usage and billing, then completes payment setup. Before activation, Live activity is a free preview. Earlier usage is never charged retroactively; customers already counted during preview stay included for that Space/month. If paid activation is unavailable, the console says so and preview remains free.

The budget covers platform charges before tax across every Live Space in the company. It starts as alert-only, so reaching it does not interrupt the integration. Owners can explicitly enable a hard stop. With that option enabled, an operation that would add a new charge returns 402 billing_budget_exceeded. No part of that operation's points, progress, benefits or charge commits. Raise the limit and retry with the same transaction identifier. Already-counted customers and free operations can continue.

A zero hard limit pauses new charges. 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, the remaining monthly limit, 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 and payment methods are available through the billing portal.

Existing subscriptions keep their current plan until their account-specific migration date. They must finish that migration before paid usage can start, so subscription and PAYG charges never overlap. Contact support to coordinate the 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.