Skip to main content
Prices define how much you charge for each billable metric within a plan. Paygentic supports multiple pricing models to match your business needs.

Pricing Models

Standard Pricing

Fixed cost per unit. Simple and predictable. Every unit costs the same amount regardless of volume. If you charge $0.001 per token, the 1st token costs the same as the 1,000,000th token. Use cases:
  • Flat rate per token
  • Fixed cost per GB
  • Standard hourly rates
  • Per-seat licensing

Dynamic Pricing

Price varies based on real-time conditions. Instead of setting a fixed price upfront, you specify min/max bounds. The actual price is determined when usage occurs - you pass the current rate with each usage event. Example: GPU compute that follows spot market prices. When demand is low, charge 2/hour.Duringpeaktimes,charge2/hour. During peak times, charge 5/hour. Use cases:
  • Spot instance pricing
  • Market-based rates
  • Time-of-day pricing
  • Supply/demand adjustments

Percentage Pricing

Take a cut of transaction value. Charge based on the monetary value flowing through your platform. Set a percentage (like 2.9%) plus optional minimum and maximum caps per transaction. Example: Payment processing that charges 2.9% of each transaction, with a 0.30minimumand0.30 minimum and 100 maximum. A 10purchasecosts10 purchase costs 0.30 (minimum applies), a 1000purchasecosts1000 purchase costs 29 (2.9%), and a 10,000purchasecosts10,000 purchase costs 100 (maximum applies). Use cases:
  • Revenue sharing
  • Transaction fees
  • Commission models
  • Marketplace takes

Payment Terms

Control when and how customers are charged for usage.

In Advance

Charge at the start of each billing period before usage occurs. The customer is billed upfront for the upcoming period. Perfect for:
  • Recurring subscription fees
  • Platform access charges
  • Per-seat licensing
  • Any fixed fee on Standard Billing plans

In Arrears

Accumulate charges throughout a billing period and bill at period end. Customers pay after usage has occurred. Perfect for:
  • Metered usage (tokens, API calls, storage)
  • Enterprise contracts with NET payment terms
  • Large transaction volumes
  • Traditional invoicing workflows

Instant (Legacy Billing only)

Charge in real-time as each usage event occurs. Money moves immediately from customer accounts. Perfect for:
  • Pay-as-you-go services
  • Prepaid wallet consumption
  • Small, frequent transactions
  • Real-time risk management
Standard Billing plans cannot include prices with paymentTerm: instant. Attempting to add one returns a 422 error. See Billing Versions for payment term constraints by billing model.

Linking a Feature

A price can automatically provision an entitlement when a customer subscribes by linking it to an entitlementTemplate. This is how you grant access to features — quota limits, reset periods, and rollover behavior — directly through the plan’s pricing. To grant a feature without charging for it, set unitPrice: "0" on the price and attach the entitlementTemplate. When a customer subscribes to the plan, the entitlement is provisioned automatically. Key points:
  • The entitlementTemplate on the price defines the grant: quota amount, reset cadence, and rollover behavior
  • Requires Standard Billing (billingVersion: 1)
  • A single price can carry at most one entitlement template
See Features and Entitlements for the full configuration reference.

Combining Models

Mix different approaches within one plan to optimize for your business. Example: AI Platform
  • Base platform access: $499/month (standard, in advance)
  • Token usage: Market rate (dynamic, in arrears)
  • Enterprise support: $5000/month (standard, in advance)
Example: Data Warehouse
  • Storage: $0.02/GB-month (standard, in arrears)
  • Queries: Spot pricing 0.500.50-2.00 (dynamic, instant)
  • Data export: 1% of monthly bill (percentage, in arrears)

Design Principles

Start simple. Standard pricing covers 90% of use cases. Add complexity only when needed. Match customer expectations. B2C favors instant payment, B2B prefers invoicing.

Next Steps