Financial operations

Security programs are financial operations. Rewards are paid, engagements are billed, and subscriptions renew — often across several currencies and jurisdictions. This document covers how the platform models that spend.

Wallets and currencies

Funds are held in wallets and settled in multiple currencies, so a program is not forced into a single accounting currency:

USD, EUR, GBP, INR and ETB are supported for wallet and settlement operations.
Conversion uses real-time rates with disclosed fees.
Every movement is written to a transaction audit trail that records who initiated it and why.

Budgets

Budgets make spend a managed line item rather than a surprise:

Per-program budgets — a reward ceiling for crowd-sourced work, with allocation against severity bands.
Per-engagement budgets — a defined scope of effort for expert work.
Period budgets — monthly, quarterly or annual allocations that reset predictably.
Threshold alerts — notification as consumption approaches the allocation, before it is exhausted.

When a reward is approved, it is recorded against the relevant budget, so the remaining allocation is always current.

Usage metering and overage

Metered capabilities — engagement effort, retest hours, scanning volume and similar — are tracked transparently:

Consumed effort is visible to both parties during the engagement, not only on the invoice.
Overage handling follows pre-agreed thresholds and rates, so exceeding a tier does not create a billing dispute after the fact.
Metering data is retained alongside the engagement record for reconciliation.

Subscriptions and entitlements

Plan and entitlement management determines which capabilities are available:

Tiered offerings with entitlement-aware feature gating — a capability that is not licensed is not silently usable.
Subscription state drives what program owners and participants can do, which is why plan changes take effect on the same control plane rather than in a separate billing tool.
Renewals, upgrades and downgrades are recorded against the organisation account.

Invoicing and reconciliation

Invoices are generated, tracked and reconciled in-platform against the underlying metering and reward records.
Reconciliation compares what was consumed with what was invoiced, with the difference explained by the transaction trail.
Ledger-backed storage is used for financial records, so balances are derived from transactions rather than from a single mutable number.

Incentive engine

Programs sometimes need more than a flat reward band:

Promotions — time-limited multipliers or bonuses for a target area.
Referral programs and referral codes — incentives for bringing researchers into a program.
Contract-term pricing — agreed rates for a named researcher or expert over a period.
Stacking rules — explicit precedence when more than one incentive applies, so the calculation is deterministic rather than argued.

Step-up verification

Sensitive financial operations — large payouts, budget changes, payout method changes — require additional verification before they execute. The requirement is part of the workflow, not a policy document.

Availability and limits

Multi-currency wallets, budgets, metering, overage handling and invoicing are available on all tiers, with limits on concurrent wallets and programs that depend on the plan.
Automated payouts are Professional-tier.
The platform provides the calculations and the record. It does not provide accounting, audit or tax advice.

Payouts and KYC — how approved rewards reach researchers
Tax and reporting — withholding and annual reporting
PTaaS engagement lifecycle — metering and billing for expert work