For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
LoginSandbox
Platform GuidesAPI DocsSDKMCP ServerChangelog
Platform GuidesAPI DocsSDKMCP ServerChangelog
  • Getting started
    • Introduction
    • Concepts
    • Onboarding guide
  • Use cases
    • Monetizing an AI agent
    • Pricing models for AI products
    • Configuring entitlements for AI products
  • Usage metering & events
    • Meters
    • Usage events
    • Unmatched events
    • Event reprocessing
  • Products & plans
    • Product Catalog
    • Pricing Plans
      • Usage-based pricing
        • Flat and fixed pricing
        • Progressive tiered pricing
        • Top-tiered pricing
        • Stairstep pricing
        • Pricing rules
        • Combining usage volumes
      • Recurring pricing
      • One-off pricing
      • Pricing groups
      • Add-ons
      • Seat-based pricing
      • Top up pricing
    • Features & Entitlements
  • Wallets & credits
    • Credit types & wallets
    • Credits in pricing plans
  • Customers & subscriptions
    • Customers
    • Subscriptions
    • Quotes
  • Invoicing
    • Invoices
    • Invoice corrections
    • Payment Collections
    • Tax
    • Currencies & Exchange rates
    • E-invoicing
  • Analytics & reporting
    • Insights
    • Report downloads
    • Revenue Recognition & Deferred Revenue
  • Integrations
    • CRM
    • ERP
    • Email Providers
    • Data Imports: Event File Uploads
    • Data Exports
    • Payment Service Providers
  • Settings & admin
    • Billing entities
    • Payment Options
    • User management
    • Customising invoices
    • Custom fields
    • Default platform settings
    • API key creation
    • Alert Rules
    • Workflows
  • Workflows
    • Workflow Triggers
    • Workflow Actions
    • Monitoring and Audit
    • Common Use Cases
  • For developers
    • Introduction
    • Authentication
    • Local development setup
    • API
    • Errors
    • Troubleshooting
    • Query Parameters
    • Expanding Responses
    • Idempotency
    • Timestamp formatting
    • Webhooks
    • Locale
    • MCP Server
LoginSandbox
On this page
  • Pricing types
  • Percentage-based pricing
  • Minimum (floor) and maximum (caps) values
  • Add-on pricing
  • Combining usage volumes
  • Non-billed products
  • Summary
Products & plansPricing Plans

Usage-based pricing

Was this page helpful?
Previous

Flat and fixed pricing

Next
Built with

The options in usage-based pricing are endless, and we are proud to say we cover the most complex and exotic pricing structures out there.

Within the Solvimon platform there are various ways to price and configure pricing. The main way to configure usage-based pricing is with a pricing type, but pricing can also be diversified with included volume, changing the type to add-on, configuring a block size, or even to combine volume and create volume pooled pricings.


Pricing types

We offer all standard usage-based pricing types. We go into more detail on separate pages for the following pricing structures:

  • Flat
  • Progressive tiered
  • Top-tiered
  • Stairstep

Percentage-based pricing

Percentage-based fees are similar to unit-based pricing, but it differs in the fact that the meter value is a monetary amount value instead of a number. The price is calculated as a percentage of the amount, instead of a unit-based fee.

Percentage based pricing has the same options for pricing such as a flat (percentage) fee, and progressive or top-tiered pricing structures. However, as it’s a calculation on top of the unit measurement, it also allows for minimum and maximum pricing calculations.

Minimum (floor) and maximum (caps) values

When using percentage-based pricing, you might want to price your customers with a minimum and/or a maximum amount. This extra pricing configuration is available for both flat and tiered percentage-based pricing configurations.

Read more about it here.


Add-on pricing

By default, pricings that you create are configured as ‘default’ pricing. It is also possible to change the type to ‘add-on’, which enables your team to not include that specific pricing in a subscription.

Read more about add-ons.


Combining usage volumes

In some cases, usage metrics are combined to combine volumes of multiple products into one pricing configuration.

In the KYB industry, an example would be to combine volumes of ‘Authorized transactions’ and ‘Cleared transactions’ within one tiered pricing schema.

Read more about combining volumes here.


Non-billed products

The Solvimon Platform also supports ‘non-billed’ pricing, which means the product. For example, when your company does not have any pricing for a default usage event but does have an exception (e.g. if the card type is Mastercard), you can configure the default pricing to be ‘non-billed’ and add a price rule for the meter property filter of card type = Mastercard.

Non-billed pricing is also not shown on the invoice of your customer.


Summary

All pricing models are used to charge customers based on their usage, but they differ in the way the pricing tiers are structured. They all can be useful options for businesses that want to offer flexible pricing to their customers. It is important to carefully consider which approach is most appropriate for your business and your customers’ needs.