Billing and Credits Management

Overview#

Organisations that need predictable costs benefit from a credits model. Rather than receiving an invoice at the end of a metered period, teams purchase credits in advance and consume them as they work. The balance is always visible, auto-topup prevents unexpected service interruptions, and the transaction ledger provides the immutable record that finance teams and auditors need.

Key Features#

Credits-Based Billing: Organisations maintain a credit balance consumed as platform features are used. Credits provide a simple, predictable billing model with full transparency into exactly what drove each deduction.
Credit Packages: Pre-defined packages carry bonus credit incentives on larger purchases. Each package displays the effective credit value and cost per credit, making it straightforward to select the most economical option.
AI Token Usage Tracking: Token-based billing for AI operations with per-model cost calculation. Track consumption by model type, operation, and user for complete cost visibility without manual reconciliation.
Infrastructure Usage Metering: Metered tracking for platform resource consumption including compute, storage, bandwidth, and data operations. Costs are calculated and deducted automatically with no manual step required.
Auto-Topup: Configure automatic credit replenishment when the balance falls below a defined threshold, ensuring uninterrupted platform access without requiring administrators to monitor balances manually.
Low-Balance Alerts: Receive notifications when the credit balance approaches the configured minimum, giving your team time to purchase additional credits before operations are affected.
Monthly Usage Summaries: Aggregated reporting by month with breakdowns by usage type, quantities, and costs. Filter by organisation, year, and month to support internal chargebacks and financial reviews.
Transaction History: A complete, immutable ledger of every credit movement, including purchases, usage deductions, refunds, and manual adjustments, with full audit trail and user attribution.

Purchase Workflow#

Browse available credit packages and select the option that fits your needs.
Initiate the purchase, which opens a secure checkout through the integrated payment processor.
Upon successful payment, credits including any package bonus are added to your balance immediately.
All transactions are recorded with timestamps and user attribution for audit purposes.

Use Cases#

Predictable budgeting with pre-purchased credit packages and configurable auto-topup to avoid service interruptions.
Cost allocation using monthly usage summaries broken down by usage type and resource for internal reporting.
Usage monitoring with real-time balance checks and low-balance alerts to maintain operational continuity.
Financial auditing with a complete, immutable transaction history covering every credit movement and its cause.

Open Standards#

GraphQL (June 2018 specification): All subscription-tier queries, usage-status dashboards, tier assignment, and add-on mutations are exposed through a typed GraphQL API, enabling strongly-typed, self-documenting billing operations for client integrations.
OAuth 2.0 Bearer Token (RFC 6750): Calls to the Revolut Merchant API are authenticated using the Bearer token scheme, and all billing GraphQL endpoints enforce the same token-based authentication via the platform's IsAuthenticated permission layer.
HMAC-SHA256 webhook verification: Incoming payment-event webhooks from Revolut are verified using an HMAC-SHA256 signature over a timestamp-prefixed payload, with a mandatory ±5-minute timestamp window enforced to prevent replay attacks.
ISO 4217 currency codes: Currency values throughout the credits model and Revolut order payloads (USD, EUR, GBP) conform to ISO 4217, ensuring interoperability with payment processors and financial reporting systems.
ISO 8601 date and time format: All purchase timestamps, invoice issue/due dates, and usage-period boundaries are serialised in ISO 8601 format, maintaining consistent temporal representation across API responses and audit records.
JSON (RFC 8259): Revolut Merchant API requests and responses, webhook payloads, and internal usage metadata are all carried as JSON, the interchange format defined by RFC 8259.
PSD2 / Strong Customer Authentication (EU 2015/2366, RTS 2018/389): Card payments processed via Revolut Merchant comply with PSD2 Strong Customer Authentication requirements, including 3-D Secure challenge flows for EU-issued cards, ensuring regulatory compliance for online payment transactions.

Availability#

Enterprise Plan: Included
Professional Plan: Included

Last Reviewed: 2026-02-24 Last Updated: 2026-04-14